A Framework for Deciding When to Cancel a Project
Where no stop condition was written, a running project can still be judged: forward cost, forward value, and the work it displaces, with evidence from someone other than the sponsor.
A project with no stop condition still has to be judged by something.
The previous note in this series argued for writing the stop condition before a project starts. That advice helps the next initiative. It does nothing for the ones already running, most of which began with a business case, an owner and a budget code, and no sentence describing the circumstances in which they would end. The question that reaches the leadership team about those projects is rarely whether to write a criterion. It is whether to cancel this one, now, with the sponsor in the room and a year of work behind it. Writing the condition in advance is the cleaner route. This note is for the other case.
What the framework replaces
Without a framework, a cancellation discussion is conducted in the past tense. How much has been spent, how hard the team has worked, what was promised to whom, how it would look to stop now. All of it is true and none of it decides anything, because none of it can be changed by the choice in front of the room. The only inputs that bear on the decision are what finishing will still cost, what finishing will still deliver, and what the same people could do instead. A framework is a way of keeping the discussion on those three and off the rest.
Three questions about the future carry the whole decision.
They are asked in a fixed order, and each is answered in writing before the next is opened.
- Forward cost: what it takes to reach the original outcome from today, estimated by the people who will do the work and set beside their last two estimates.
- Forward value: what finishing is worth given what is now known, written without reference to the original business case.
- Displaced work: what the same people and the same senior attention would produce if the project stopped, named specifically.
Forward cost and forward value
Forward cost is not the remaining budget. It is the effort needed to reach the benefit that justified the project, and the useful signal is its direction. An estimate to finish that has moved back a month at each of the last three reviews is evidence about the project, whatever the explanation offered each time. Forward value is rebuilt from current evidence. The original case usually rested on a belief about customers, a partner, a regulation or a price point, and the first task is to check which of those beliefs the last six months have confirmed.
The question nobody asks
The third question is the one that gets skipped, because it moves the discussion away from the project and onto the portfolio. A project can have a positive forward value and still be the wrong thing to continue. A pattern seen in digital banking product teams: a redesign of a checkout step is most of the way through and its case still holds, while the same four engineers are the only people able to diagnose a conversion drop in the payment flow that is already live. The redesign is worth finishing in the abstract. It is not worth finishing this quarter. Competing priorities resolve at the point of contention, and that point is usually a named group of people, not a budget line.
Evidence has to come from someone other than the sponsor.
The sponsor is the person best placed to explain every data point and least placed to read them. That is not a question of honesty. A sponsor holds the context in which a weak adoption curve is a timing issue and a slipped milestone is a dependency, and the context is often correct. It is also impossible to distinguish from a story told to protect the project.
Who holds the numbers
The remedy is mechanical. The three answers are assembled by someone without a stake in the outcome, a finance partner or the lead of an adjacent team, and presented in a fixed shape: the current estimate to finish beside the previous two, evidence of use or commitment from outside the project team, and a list of the assumptions in the original case marked as confirmed, open or broken. The sponsor then responds to the page rather than producing it.
Signals that are hard to argue with
Three tend to appear together by the time a cancellation is under discussion: the estimate has moved at several consecutive reviews, the evidence for value is described only in the future tense, and the defence of the project has shifted from what it will deliver to how much has been put into it.
A project defended by its effort rather than its outcome has usually already answered the question.
When the case for continuing is made in terms of investment rather than result, the framework has answered, and the meeting is about how to say so.
Cancelling well is part of the decision, not its aftermath.
Teams that stop projects badly tend to treat the choice as binary and the aftermath as someone else's task. Both habits make the next cancellation harder, because the people watching learn what a stop costs them.
Three outcomes, not two
The meeting has three available results. The project continues with a new, narrower condition and a date. It stops. Or it is reshaped, with the part that carries the value kept and the rest dropped. Reshaping is the most underused of the three, because it requires someone to say which part of the work was the point, and a sponsor who has defended the whole project is poorly placed to say it. Where the review sits in the regular operating cadence, it can be decided in the slot where other trade-offs for the same people are being made.
What is kept and who moves
Before the meeting closes, the decision names what is salvaged, where each person goes within the week, and who tells the affected stakeholders. A short written record of the three answers and the date goes with it. A cancellation with a written reason becomes a reference point for the next project; one without a reason becomes a rumour about the sponsor.
Where the framework becomes work.
The framework is simple to describe and uncomfortable to run, mostly because it is run on a project somebody owns. The practical start is small. Take the oldest live initiative on the list, and in one session with a finance partner write down its forward cost, its forward value and the work it displaces. The answer is sometimes to continue, and then the project is stronger for having been asked.
That session is the kind of work our consulting practice does inside the growth discipline pillar, and it is often run as an outside read on a portfolio where every sponsor has a reasonable account of why their project is the exception.
Continue