Sunk-cost persistence in projects

Sunk-cost persistence in projects means continuing a course of action—keeping a project alive, adding budget, or resisting closure—because of what has already been spent (time, money, reputation), not because the project is expected to deliver enough future benefit. In practical terms it looks like defending choices made months ago even when new information suggests a different path.

This behavior is common in organizations where projects are visible, budgets are large, or decisions have reputational consequences. It is distinct from careful long-term commitment: persistence becomes problematic when the rationale is backward-looking (what was spent) rather than forward-looking (expected return or alignment).

Key characteristics:

Sunk-cost persistence is often subtle: a single defended decision can ripple into repeated resource requests. Recognizing the pattern requires comparing the project’s future prospects to the costs of continuing, not to what was already spent.

**Loss aversion:** people weight prior losses more heavily than equivalent potential gains, so stopping feels like admitting a loss.

**Commitment and consistency:** once a leader or team has publicly endorsed a project, they prefer to appear consistent rather than reverse course.

**Reputational risk:** individuals fear damage to status or credibility if they acknowledge a past error.

**Sunk cost visibility:** large, visible expenditures (big budgets, public launches) create pressure to justify continuing.

**Confirmation bias:** teams seek evidence that supports continuing and downplay negative signals.

**Organizational inertia:** processes and dependencies make project continuation easier than restructuring or stopping.

**Misaligned incentives:** rewards tied to survival or activity rather than outcomes encourage persistence.

Repeated requests for small additional budgets labeled as 'final' fixes

Frequent reinterpretation of success criteria to avoid admitting failure

Meetings dominated by defense of past choices rather than forward planning

Reluctance to run impartial project reviews or scale back scope

Project teams assigned indefinitely rather than reallocated to higher-priority work

Senior leaders publicly endorsing continuation despite opposing evidence

Decisions framed around recovery of past investment instead of opportunity cost

Delay tactics: commissioning new analyses that postpone a stop decision

Emotional language in updates (blame, pride, ownership) overshadowing data

High early publicity (internal town halls, press) that makes reversal embarrassing

Tight personal deadlines tied to career milestones or promotions

Multi-team dependencies that raise the cost of stopping

Large up-front purchases or long vendor contracts

Performance targets tied to launch dates rather than outcomes

Recent restructuring that makes leaders reluctant to scrap projects they inherited

Executive sponsorship that ties identity or reputation to project success

Lack of clear stage gates or kill criteria in the project plan

Handoffs where the successor inherits a high-investment project

Establish stage-gate decisions with explicit stop/continue criteria before major investments are made

Require forward-looking business cases for additional funding that exclude past costs

Use independent project reviews or third-party audits focused on future prospects

Separate advocacy from decision-making: rotate who presents continuation requests

Set short, measurable pilots with pre-agreed success thresholds and automatic review points

Reframe conversations: ask ‘what will we achieve if we continue?’ rather than ‘how much have we spent?’

Make opportunity costs visible by showing what else could be done with the same resources

Create a ‘stop budget’ or dedicated contingency approved for winding down projects cleanly

Encourage leaders to document the reasoning for reversal decisions to reduce reputational risk

Celebrate smart stops publicly as evidence-based leadership rather than failure

Reassign personnel quickly to reduce sunk-cost-driven staffing inertia

Align incentives and KPIs to outcomes (metrics of impact) rather than time-on-project or survival

Sunk-cost fallacy — The cognitive bias that underpins sunk-cost persistence; the fallacy is the individual reasoning error, while sunk-cost persistence describes the organizational pattern of continuing projects.

Escalation of commitment — A behavioral process where additional resources are allocated over time; this often follows sunk-cost persistence when initial investments create momentum to commit more.

Confirmation bias — A tendency to seek supporting evidence; it fuels persistence by making negative indicators less influential in decision meetings.

Opportunity cost — The value of the alternatives forgone; unlike sunk costs (already spent), opportunity cost focuses on future choices and should guide project decisions.

Loss aversion — Emotional weighting of losses over gains; it explains why stopping a project feels like a loss even when continuing is costly.

Status quo bias — Preference for existing states; differs from sunk-cost persistence which specifically ties continuation to prior investments rather than mere comfort with the current state.

Outcome bias — Judging a decision by its result rather than the decision process; recognizing this helps separate poor outcomes due to unpredictability from systematic persistence.

Project governance gaps — Structural weaknesses that allow persistence; fixing governance differs from addressing individual cognitive bias because it changes procedures, not people.

Decision fatigue — Tiredness from repeated choices that can make leaders default to continuation; links to sunk-cost persistence by lowering the willingness to make hard stop decisions.