Organizations are good at starting things and remarkably bad at stopping them. Every company has a graveyard of initiatives that should have been killed months or years before they finally were, projects that absorbed money, talent, and attention long after it was clear they would never deliver. The ability to stop a failing effort cleanly and early is one of the most undervalued disciplines in business, precisely because it runs against powerful psychological and organizational forces. Learning to do it well frees up resources for the bets that actually matter.
Why Stopping Is So Hard
The first obstacle is the sunk cost fallacy, the deep human tendency to keep investing in something because of what has already been spent. A team that has poured a year into a project finds it almost unbearable to admit that year was wasted, so they argue for one more quarter, one more pivot, one more push. But the money and time already spent are gone regardless of what happens next. The only rational question is whether future investment will produce a return, and the past spending is irrelevant to that question. Knowing this intellectually does little to remove the emotional pull.
The second obstacle is identity and reputation. Projects acquire champions whose professional standing becomes tied to their success. Killing the project feels like declaring those people failures, and they naturally resist. Often the champion is senior enough that questioning the project feels like questioning their judgment, which makes everyone below them reluctant to raise concerns. The project survives not because it is working but because no one is willing to bear the social cost of saying it is not.
Deciding the Kill Criteria Before You Start
The single most effective remedy is to define, before a project begins, the conditions under which it should be stopped. When a team commits to a new initiative, they should also commit to the specific signals that would tell them it is not working. These criteria are far easier to set honestly at the start, when no one is emotionally invested in continuing, than in the middle, when stopping feels like personal defeat.
- What result, by what date, would tell us this is working?
- What result would tell us it is clearly failing?
- What assumptions must hold true, and how will we check them?
- Who has the authority to call the project complete or to end it?
With these criteria written down in advance, the conversation about stopping changes character entirely. Instead of someone arguing that a colleague’s project has failed, the team simply checks the agreed signals against reality. The decision becomes a matter of honoring a prior commitment rather than passing judgment on the people involved. This depersonalizes a conversation that is otherwise almost impossible to have well.
Separating the Project From the People
An organization that punishes everyone associated with a stopped project teaches a clear lesson: never let your project be stopped, hide problems, and fight to keep it alive at all costs. This is exactly the wrong lesson, and it guarantees that failing projects will limp along consuming resources. The healthier approach treats a well-reasoned decision to stop as a success, not a failure, because it preserves resources for better uses.
This requires leaders to distinguish carefully between two very different things: a project that was a reasonable bet but did not pan out, and a project that failed because of poor execution or dishonesty about its progress. The first deserves no blame at all; making smart bets means some will not work. The second deserves scrutiny. When leaders consistently make this distinction, people stop fearing the act of stopping and start treating it as a normal, even admirable, part of doing good work.
Reallocating the Freed Resources
Stopping a project is only half the discipline. The other half is making sure the freed resources flow to something more valuable rather than evaporating. In many organizations, killing a project simply means the team disperses and the budget disappears into general overhead, which removes much of the incentive to stop anything. People intuitively understand that ending their project may end their roles, so they keep it alive for self-preservation.
A better system treats stopped projects as a source of capacity to be deliberately redirected. The talented people who were working on the failed effort are exactly the people you want on the next promising bet, and they bring hard-won lessons with them. When stopping a project visibly leads to working on something better rather than to unemployment or limbo, the entire organization becomes far more willing to make these calls. The discipline of stopping and the discipline of reallocating must work together.
The Strategic Payoff of Stopping Well
An organization that can stop projects cleanly enjoys an advantage that compounds over time. It runs more experiments because each one is cheaper when failure is caught early. It learns faster because it is not pouring resources into efforts that have stopped teaching it anything. And it keeps its best people working on its best opportunities rather than trapped in slowly dying initiatives. The companies that win are rarely the ones that never bet wrong. They are the ones that recognize a losing bet early, cut it without drama, and move the chips to a better table. That quiet discipline, unglamorous as it is, separates organizations that learn from those that simply accumulate expensive regrets.