Dead Projects Walking: How Sunk-Cost Thinking Is Quietly Bankrupting American Portfolios

Somewhere in your organization's portfolio right now, there is almost certainly a project that should not exist anymore. Its original business case has eroded. Its timeline has slipped past the point of strategic relevance. Its sponsor has quietly moved on to shinier priorities. And yet — week after week — a team of capable professionals shows up, burns through budget, and produces status reports that nobody reads with full confidence.

This is not a hypothetical. According to research from the Project Management Institute, organizations waste an average of $97 million for every $1 billion invested in projects and programs. Scale that across the American economy, and the figure approaches $1.7 trillion in annual losses tied to projects that underdeliver, stall, or fail outright. A significant portion of that waste is not the result of poor execution. It is the result of a far more insidious problem: the institutional inability to kill a project that has already, by every measurable standard, failed.

These are zombie projects — initiatives that consume resources without generating value, sustained not by logic but by a combination of psychological bias, political self-preservation, and structural gaps in how organizations govern their portfolios.

The Psychology Behind the Persistence

The most well-documented culprit is the sunk-cost fallacy — the deeply human tendency to continue investing in a failing endeavor because of what has already been spent. In a business context, this manifests as reasoning like: We've already committed $4 million to this platform. We can't walk away now. The rational counter-argument — that the $4 million is gone regardless of what happens next, and that the only relevant question is whether future investment will generate future value — is intellectually obvious. It is also emotionally very difficult to act on.

Behavioral economists Daniel Kahneman and Amos Tversky demonstrated decades ago that humans feel the pain of losses more acutely than the pleasure of equivalent gains. In project environments, this means that the psychological cost of formally declaring a project dead often feels greater to decision-makers than the ongoing financial cost of keeping it alive. Killing a project is a visible, attributable act. Letting it limp along is diffuse and deniable.

For executives who championed a project publicly, the calculus becomes even more fraught. A canceled initiative can read as a leadership failure. In cultures that conflate decisiveness with never reversing course, admitting that a project should not continue feels professionally dangerous — even when the data is unambiguous.

The Political Architecture of Survival

Beyond individual psychology, zombie projects are sustained by organizational structures that inadvertently reward continuation over clarity.

Consider how most American companies fund projects. Annual budgeting cycles allocate resources in advance, and unspent budget often disappears at year-end. Project teams therefore have a structural incentive to keep spending — not because it creates value, but because returning funds signals underperformance and may result in smaller allocations next cycle. The project continues not because anyone believes in it, but because the incentive architecture makes stopping it costly at the team level.

Sponsor accountability compounds the problem. In many organizations, the executive who approved a project is also the executive who must authorize its termination. This creates a closed loop in which the person most motivated to protect the initiative from scrutiny is also the person with the most authority over its fate. Without independent portfolio governance — a steering committee, a PMO with real authority, or a formal stage-gate process — there is no structural mechanism to override that dynamic.

Finally, there is the reporting problem. Status dashboards in most organizations are built to track progress, not to surface failure signals. A project can be weeks behind schedule, over budget, and technically misaligned with current business strategy while still displaying a yellow status indicator and a narrative update that reads: Team is working to resolve current challenges. The language of project reporting is often optimized for reassurance rather than honest assessment.

Building a Kill-Criteria Framework

The antidote to zombie project syndrome is not a cultural pep talk about embracing failure. It is a structured, pre-agreed set of conditions under which a project will be formally reviewed for termination — and a governance process with the authority to act on those conditions.

Here is a practical framework that project leaders can adapt and implement within their organizations:

1. Define Kill Criteria at Project Initiation

Before a project begins, the project charter should include explicit threshold conditions that trigger a mandatory portfolio review. These might include: a cost variance exceeding 25 percent of the approved baseline; a schedule delay that pushes the go-live date past the strategic window the project was designed to address; a change in business conditions that eliminates the original value case; or two consecutive stage-gate reviews without a credible path to recovery. The specifics matter less than the principle: kill criteria must be defined before anyone has emotional or political investment in the outcome.

2. Separate the Decision from the Sponsor

Project termination decisions should not rest solely with the sponsoring executive. An independent portfolio review board — whether that is a formal PMO, a capital allocation committee, or a cross-functional steering group — should have standing authority to initiate a termination review when kill criteria are met. This is not about stripping authority from sponsors. It is about creating organizational cover that makes it safer to make the right call.

3. Reframe Termination as Portfolio Optimization

Language matters. In organizations where killing a project is culturally coded as failure, leaders should deliberately reframe the act. Terminating a project that no longer serves its original purpose is not a defeat — it is a reallocation of scarce resources toward initiatives with stronger return potential. Smart project leaders position this framing proactively, both upward to executives and outward to the broader team.

4. Conduct a Value-Forward Analysis, Not a Backward-Looking Audit

When a project is under review, resist the temptation to relitigate past decisions. The only analytically relevant question is: Given what we know today, does completing this project represent the best use of the remaining investment? A clean, forward-looking business case — stripped of historical justification — often makes the right answer apparent far more quickly than a postmortem-style review.

5. Create a Safe Mechanism for Teams to Surface Concerns

Project teams frequently know a project is in trouble long before leadership acknowledges it. Building a formal channel — whether through structured retrospectives, anonymous portfolio health surveys, or PMO check-ins — allows that ground-level intelligence to reach decision-makers without requiring individuals to put their careers at risk by speaking up in the wrong meeting.

The Competitive Cost of Inaction

It is worth stating plainly what zombie projects cost beyond the budget line. Every dollar and every hour absorbed by a failing initiative is a dollar and an hour that is not available for the next viable opportunity. In fast-moving sectors — technology, healthcare, financial services — the opportunity cost of misallocated resources compounds quickly. Competitors who make cleaner, faster portfolio decisions move faster. They are not smarter. They have simply built the governance structures that make difficult calls possible.

The organizations that consistently outperform their peers are not the ones that never launch projects that fail. Every ambitious portfolio will include some. The differentiator is how quickly and cleanly those organizations recognize failure and redirect resources. That capability is not accidental. It is designed.

Building that design — kill criteria, independent governance, honest reporting, and a culture that treats termination as strategic discipline rather than institutional embarrassment — is one of the highest-leverage investments any project leader or executive can make. The $1.7 trillion problem is real. The solution is not complicated. It is simply difficult, in the way that all genuinely important organizational work tends to be.