Stopping a project is a result, not a failure

A project can keep moving long after its justification has weakened. People have worked hard, money has been committed and the next milestone looks close enough to make another extension feel reasonable. The question for the sponsor is whether the remaining commitment still deserves a place among the business’s priorities.

Answering that question can lead to a decision to stop. Handled properly, that decision frees resources, limits further exposure and leaves the organisation with useful knowledge. It deserves the same care as a decision to proceed.

Separate the past commitment from the next one

Past expenditure explains how the business arrived here. It helps establish accountability and identify lessons. The forward decision concerns what further time, money and attention will be required, and what the business can reasonably expect in return.

Ask what you would approve today, knowing what you now know. Would the remaining work still be a priority? Would the expected outcome justify the remaining cost? Would you commit the same people if they were available for other work?

Include the consequences of changing course. Contract commitments, transition work, dependencies and disruption can make stopping expensive. Those costs belong in the comparison alongside the cost of continuing.

The aim is an honest assessment of the choices still available. Some past investments create assets worth completing. Others create obligations that need to be managed even when the original ambition is abandoned.

Revisit the reason the project exists

Return to the business outcome. Has the underlying problem changed? Is the intended benefit still valuable? Have operating conditions, customer needs or other investments altered the case?

A team may be delivering competently against a brief that has become less relevant. It may also have learnt that an essential assumption was wrong. Neither situation is resolved by making the status report more positive.

Consider a hypothetical resources business developing a central reporting platform for several sites. During delivery, it discovers that each site uses different definitions for the measures executives want to compare. A new platform can collect the numbers, but agreement on their meaning requires operational work that was never funded.

The sponsor now has a different decision. It could fund that prerequisite work, narrow the platform to measures already consistent across sites, or stop the wider rollout and improve existing reporting. Completion of the original technical scope would not, by itself, establish that the business outcome had been achieved.

Compare credible paths from here

Give the sponsor a small set of workable options. Continuing unchanged is one option only if its assumptions remain credible. Other possibilities include reducing scope, changing the delivery approach, pausing for a specific dependency or closing the project.

For each option, explain the remaining benefit, expenditure, demands on internal capacity and consequences for operations. State what has to be true for it to succeed, and how confident you are in that assessment.

Treat a pause carefully. It needs an owner, a defined reason and a review date tied to evidence. Otherwise, the project may continue consuming money and attention while nobody has explicitly chosen to continue it.

Ask where the released capacity would go. Stopping creates more value when it makes another priority achievable. That might be maintaining a critical asset, resolving a customer problem or finishing a smaller initiative with a clearer benefit.

Make closure part of the decision

A stop decision needs a practical closure plan. Establish which services or processes depend on work already delivered, who will support them and what must be completed to leave operations in a stable position.

Identify useful assets: cleaned data, documented requirements, working integrations, supplier knowledge or lessons about implementation. Preserve them where there is a credible future use. Retaining every component indefinitely can create its own maintenance burden.

Agree the handling of contracts, access, data and any temporary arrangements with the people responsible for them. Assign an owner to each closure action and a date for confirming that it is complete.

Communicate the decision clearly. Explain what changed, which alternatives were considered and what happens next. Recognise the team’s contribution without implying that the project must continue to validate its effort.

Keep accountability and learning together

Stopping should prompt a review of how the original decision was made and how later evidence was handled. Which assumptions went untested? Were concerns escalated early enough? Did governance provide an opportunity to change direction?

Separate those questions from the forward investment decision so that fear of blame does not determine what happens next. Leaders can examine avoidable mistakes while still rewarding people for surfacing information that improves a decision.

At the next review, ask the sponsor to compare the remaining investment with its realistic alternatives. Request a recommendation, the evidence behind it and a plan for the consequences. Continuing, narrowing and stopping should each be choices the business can explain and act on.