Killing Projects Is a Leadership Skill. Most Leaders Never Learn It.
Introduction
Organizations are excellent at starting things and terrible at stopping them. The courage to cancel a project, shut down a legacy process, or eliminate a meeting that has outlived its purpose is one of the most valuable and least developed skills in leadership.
Every organization has a graveyard. Not the visible one where failed initiatives get acknowledged and learned from. The other kind. The one filled with projects that are technically still running, still consuming budget and attention and the energy of people who privately know the work is going nowhere, but that nobody has the authority or the courage to officially end. The zombie portfolio. The list of things the organization is doing because it started them, not because they are still worth doing.
Most leaders are never taught to manage that list. They are taught to prioritize, to execute, to lead through uncertainty and build momentum toward new goals. They are almost never taught to stop. And the absence of that skill has a cost that compounds quietly across every quarter the dead weight stays on the books.
Why organizations can't stop what they've started
The psychology behind this pattern has been studied since the 1970s, when Daniel Kahneman and Amos Tversky identified loss aversion as one of the most reliable and most irrational features of human decision-making. Their research found that people feel the pain of a loss roughly twice as intensely as they feel the pleasure of an equivalent gain. In organizational terms, this means canceling a project that cost two million dollars feels psychologically worse than the two million dollars of future cost that continuing it will generate. The loss is concrete and immediate. The future cost is abstract and deniable.
Barry Staw at UC Berkeley built on this work to study what he called escalation of commitment, the organizational tendency to increase investment in a failing course of action precisely because of what has already been spent. The Concorde supersonic jet became so associated with this pattern that researchers now sometimes call it the Concorde fallacy. The British and French governments continued funding a project that had long since ceased to be commercially viable because the billions already invested made abandonment feel politically impossible. Google continued investing in Google+ for years after it was clear the platform would never compete meaningfully with Facebook, reportedly because leadership had committed so publicly that retreat felt like failure rather than clarity.
These are not stories about unintelligent people making obviously bad decisions. They are stories about intelligent people making predictable decisions, driven by a cognitive bias that organizational culture almost universally reinforces rather than corrects.
The cost hiding in plain sight
The sunk cost fallacy represents one of the most costly cognitive biases in organizational life, responsible for failed projects, destroyed shareholder value, ruined careers, and missed opportunities measured in the billions of dollars annually. That cost does not announce itself. It accumulates quietly in the ongoing budget of projects that should have been stopped six months ago, in the calendar time consumed by meetings that exist out of habit rather than necessity, in the attention and energy of people whose best thinking is being applied to work the organization has already privately given up on but has not officially ended.
There is also a less visible cost that may be more significant in the long run. Every zombie project on the list is occupying a slot that a genuinely valuable initiative could fill. Organizations have finite capacity for attention, budget, and talent. A team grinding through a project that nobody believes in anymore is not available for the work that could actually move things forward. Keeping the dead alive does not just waste the resources going into it. It crowds out the things worth investing in.
Why stopping feels like failing
The reason this pattern is so persistent is that organizational culture has, in most companies, built a deeply asymmetric relationship with starting and stopping. Starting something is celebrated. It signals ambition, initiative, forward momentum. Stopping something, even intelligently and deliberately, reads in most organizational cultures as giving up. Leaders who cancel projects worry about being seen as indecisive or lacking conviction. Teams that shut down work they recognize is going nowhere worry about what it says about their judgment that they pursued it in the first place.
Research on psychological safety in the context of project termination points to the same dynamic that surfaces in every other domain where honest organizational assessment is required. In environments where admitting a project is not working carries a personal reputational cost, people avoid making that admission for as long as possible. The project continues not because anyone believes in it but because the cost of stopping it feels higher than the cost of continuing, which is precisely the trap that the sunk cost fallacy is designed to create.
What gets lost in this calculation is the distinction between the cost already spent, which cannot be recovered regardless of what happens next, and the cost still ahead, which is entirely within the organization's control. The rational question is never whether the investment to date was worth it. That is settled. The only question that actually matters for the next decision is whether the future return justifies the future cost. When the answer is no, the courageous and the intelligent response are the same thing: stop.
What it actually takes to build a culture that can stop
Organizations that develop the ability to kill projects intentionally do not leave that capability to individual courage. They build it into structure, because structure is more reliable than courage and does not require a hero in every room.
The most effective structural intervention is establishing what some organizations call kill criteria before a project begins, specific, agreed-upon conditions that would trigger a project review or termination, defined when the team is still optimistic and before sunk cost thinking has taken hold. When those criteria exist in advance, stopping a project that meets them is not a failure of conviction. It is a demonstration of discipline. The decision was already made. The data just confirmed it.
Stage-gate review processes serve a similar function, building in regular structured moments where a project must re-justify its continuation against current evidence rather than past investment. The question at every gate is not whether this was a good idea when it started. The question is whether it is a good use of resources from this point forward. That reframe, consistently applied, is one of the more powerful antidotes to escalation of commitment that organizational design has produced.
Leaders can also change what gets rewarded. Organizations that only celebrate projects that launch and succeed are training their people to hide the ones that should stop. Organizations that explicitly recognize intelligent termination, that treat the early, clear-eyed cancellation of a project that is not working as a mark of judgment rather than a mark of failure, create an environment where stopping is a legitimate and valued option rather than a last resort pursued only after everything else has failed.
What this requires from individual leaders
Beyond the structural, there is a personal dimension to this that no process can fully replace. Leaders who are good at stopping things share a quality that is less common than it sounds: they are genuinely more committed to what the organization needs than to what their past decisions say about them. They have separated their identity from the projects they have championed, which means they can update their position when the evidence changes without experiencing that update as a personal defeat.
That separation is harder than it sounds in environments where leadership credibility is built partly on the confidence with which decisions are made and defended. The leader who championed a project eighteen months ago and now stands up to recommend shutting it down is doing something that requires more confidence, not less, than the leader who continues defending it because the alternative is admitting the original call was wrong.
Stopping well is not the opposite of confident leadership. It is one of its clearest expressions.
If you want your leaders to develop the judgment to prioritize ruthlessly and the confidence to stop what is no longer working, Juan Bendana builds keynotes around the psychology of confident decision-making, courageous leadership, and what it takes to lead an organization toward what matters most. His talks are built for leadership conferences, corporate events, and sales kick-offs where organizations are ready to move faster by doing less, better.
The most confident thing a leader can say is not yes to something new. Sometimes it is finally, clearly, no to something old.