Scenario

Flagship Project Is Late and Over Budget: Continue or Kill?

The steering committee keeps approving extensions because every option looks worse than one more quarter. This scenario maps the incentives that keep failing programmes alive and the single question that cuts through them.

By the time a flagship programme is visibly late, the organisation is no longer deciding whether it was a good idea. It is deciding whether anyone is willing to own the write-off. Until someone is, the default decision is another extension, taken one quarter at a time.

Last reviewed 3 July 2026 · Free and ungated

Pressure-test this decision

Selected senior operators who have rescued, rescoped and stopped programmes like this one can tell you which door this situation usually leads to, confidentially, before another extension is approved.

Pressure-test this decision

How a client brief works · What you receive

Nobody decided to be here

Programmes rarely fail in one meeting; they fail across eight unremarkable ones. Each extension was individually defensible (a dependency slipped, a vendor re-planned, a scope item turned out to be three scope items) and each approval was smaller than the courage required to stop. The cumulative position was never on any single agenda, which is why a programme can be eighteen months late without the organisation ever having chosen to accept eighteen months of lateness. Recognising that the current state was arrived at rather than decided is the first step towards making an actual decision about it.

Count the incentives in the room

  • The sponsor's reputation is fused to the programme: killing it reads as a verdict on their judgement, so their optimism is structural rather than personal.
  • The systems integrator bills by the month and re-plans for a living: an extension is revenue, a rescue is a change order, and a kill is a lost account.
  • The delivery team reports green because amber invites scrutiny and red invites blame: status reporting has become career risk management rather than programme information.
  • Steering committee members approve extensions because a write-off would land in someone's current-year numbers, and nobody volunteers to host it.
  • Finance flags the variance but does not own the outcome, so its warnings arrive as commentary rather than as decisions.

The question that ignores the past

Everything already spent is gone on both branches of the decision, which makes it irrelevant to the choice, and emotionally central to everyone in the room. The reframing that works is brutally simple: if this programme did not exist, would we start it today, paying only the remaining cost, to get only the remaining value? Put formally on the agenda, that question routinely produces a different answer from the one the status packs imply, because it strips out the two things doing most of the talking: the money that cannot be recovered and the reputations attached to it.

Continue and kill are not the only doors

Binary framing flatters the incumbent plan, because a full kill looks catastrophic next to one more quarter. The options worth pricing sit between the poles: descope to the increment that actually pays for itself, pause and re-contract with the integrator on different terms, replace delivery leadership while keeping the objective, or salvage the completed assets into a smaller programme. Each of these has a cost and a face-saving path attached. A steering committee that sees three priced alternatives behaves differently from one shown a cliff and a treadmill.

Who can answer without flinching

Not the sponsor, the integrator or the delivery team: each of their answers is predictable from their position before they speak. A credible answer needs people with nothing at stake in the current plan: finance building a today-forward case from scratch, an independent delivery review with explicit licence to report red, and operators who have taken comparable write-offs elsewhere. Selected senior operators from the Global Board who have stopped, rescued and rescoped programmes of this scale can say what stopping actually cost them, and what continuing cost the organisations that could not bring themselves to choose.

Frequently asked questions

Who should own the continue-or-kill recommendation?

Someone whose year does not change with the answer. In practice that means moving the recommendation away from the sponsor and the programme team to a portfolio owner or the CFO, with the sponsor given the explicit, face-saving role of presenting the options rather than defending one of them.

How do we get honest status when amber triggers scrutiny?

Change what honesty costs the reporter. A re-baselining amnesty (no consequences for restating dates and costs candidly within a defined window) combined with progress measured by demonstrated working increments rather than RAG self-assessment usually surfaces the true position within one reporting cycle.

Is a write-off really survivable?

A priced, explained write-off is a loss the board can govern; an open-ended programme is a loss it cannot see the end of. Organisations recover from controlled stops far faster than from the slow version, and hindsight treats the executive who stopped decisively better than the one who presided over the drift.

Put the write-off question to people who have answered it.

Pressure-test this decision