Kept in planning or development for years, an initiative keeps renewing its funding and its sponsor's visibility without ever shipping anything that could be judged against the original pitch.
An example
When a new chief financial officer joined a gas distribution company, the first budget review included the fourth annual renewal of the asset analytics center of excellence: forty-two staff, 11 million dollars a year, and a chief analytics officer on the executive committee. The center had produced twenty-six proofs of concept, among them a predictive model for pipe corrosion, and none was in production. Each year's steering deck showed a new roadmap with a two-year horizon. Field crews still scheduled pipe inspections from a spreadsheet. When the operations vice president had suggested a delivery deadline the previous year, the chief analytics officer called it short-term thinking about a long-term transformation, and the suggestion was dropped. The new finance chief ran a zero-based review of every standing workstream and set one date by which the corrosion model would schedule real crews or the center would shrink to five people.
Why it works
Continuing a project that is structurally pre-delivery costs the sponsor nothing in accountability: there is no shipped product to compare with the pitch, no failed launch to explain, no sunk cost to reckon with. Renewal is the easy path. The project also gives the sponsor steady visibility as a steward of the future, through town-hall slots and board updates, so it looks better than its output justifies. Calling for a delivery gate is framed as killing innovation, which makes the alternative costly for whoever proposes it. Sponsor control of the success metrics and the review schedule keeps it going, as do a culture where activity passes for progress and the absence of any outside deadline.
The thinking behind it
George A. Akerlof Akerlof's The Market for "Lemons": Quality Uncertainty and the Market Mechanism (1970) showed what goes wrong when one side knows the quality of what it offers and the other cannot tell. The sponsor of a perma-project knows how close it is to delivering, while the budget committee sees only steering decks. A deliver-or-terminate gate set by someone else forces that information into the open.
Erving Goffman In The Presentation of Self in Everyday Life (1956), Goffman separates the front region, where a performance is given to an audience, from the back region, where contradicting facts are kept. Town-hall slots, board updates, and conference talks are the project's front region, and the absence of anything in production stays in the back. The question of what has shipped brings the back region forward.
Barry M. Staw Staw's Knee-Deep in the Big Muddy: A Study of Escalating Commitment to a Chosen Course of Action (1976) found that people personally responsible for a course of action committed more resources to it after setbacks, which he interpreted as self-justification. A sponsor who controls a project's review schedule is also its most committed defender. That is why the leaders' remedy separates the people who run a program from the people who decide whether it continues.
Warning signs
Several funding cycles have come and gone for a workstream with steering decks, roadmaps, and proofs of concept that has shipped nothing and closed no hypothesis. Replanning is frequent and the horizon stays two years out. The sponsor controls both the success metrics and the review calendar. Requests for a delivery date are answered with talk of long-term transformation.
How to defend yourself
This tactic needs no enemies, so personal arguments do little. The reliable counter is structural: a deliver-or-terminate gate scheduled by someone other than the sponsor.
- Ask the question the project avoids: who would lose face if this shipped, or if it shut down?
- Propose a fixed external milestone, such as a customer commitment, a regulatory filing, or a production date, with a named owner outside the sponsor's team.
- If you are new in a finance or operations role, a zero-based review of all standing workstreams lets you ask without singling anyone out.
- Point to a peer initiative that shipped. The contrast does more than any critique.
Frame the gate as protecting the project's best idea, so it cannot be cast as killing innovation.
How a leader shuts it down
Schedule a delivery-or-terminate decision for every multi-year initiative, owned by someone other than the sponsor. Separate the people who run a program from the people who set its success measures. Run zero-based reviews of standing workstreams on a fixed cycle, so the question of what shipped becomes routine.