Sunk cost fallacy at work

The sunk cost fallacy at work is a decision bias where past investments influence current choices even when those investments cannot be recovered. In practice this means continuing projects, defending initiatives, or sticking with vendors because of what has already been spent, rather than assessing future value and risk.

Being able to name these features helps leaders take a step back and treat past investments as context, not a binding reason to continue. That mental separation creates space for objective reassessment at checkpoints.

**Loss aversion:** people prefer avoiding the feeling of having 'wasted' past investment more than pursuing a better alternative.

**Identity and reputation:** managers or teams tie personal pride or status to earlier decisions and resist reversing them.

**Social pressure:** groups reinforce commitment to avoid admitting a collective mistake.

**Confirmation bias:** teams seek information that supports previous choices and ignore contradictory signals.

**Organizational incentives:** reward systems that praise persistence can make stopping look like failure.

**Poor governance:** lack of clear review gates or exit criteria lets projects drift on past inertia.

Projects continue past clear deadlines because 'we've already spent so much'.

Teams add features or resources instead of cutting scope after negative test results.

Frequent reframing: leaders change success metrics to justify continuing initiatives.

Meetings dominated by defense of past choices rather than fresh options and trade-offs.

Decision makers defer to precedent or seniority instead of updated data.

Procurement or vendor relationships persist despite declining performance because of initial onboarding costs.

Low morale when team members who raised concerns are ignored or labeled as disloyal.

Repeated small investments (pilot after pilot) used to avoid admitting a strategic error.

Big initial investments announced publicly (time, budget, executive sponsorship).

High visibility projects tied to a leader's reputation.

Lack of predefined exit criteria or success metrics.

Rewarding persistence in performance reviews without assessing outcomes.

Long vendor onboarding or migration costs that make switching costly in perception.

Emotional stakes after public commitments (town halls, press, leadership statements).

Sparse or delayed feedback loops from users or customers.

Sunk staffing allocations that make reassigning people feel disruptive.

Establish decision gates: require go/no-go checkpoints with clear criteria and data requirements.

Use pre-mortems and red-team reviews to surface reasons to stop before escalation.

Separate roles: assign an objective reviewer or devil's advocate for major continuations.

Quantify forward-looking value: focus planning on marginal benefit of future effort, not past spend.

Normalize stopping: document cases where stopping was the right choice and share outcomes.

Define and publish exit criteria when projects start, including timelines and metrics.

Rotate reviewers: bring fresh eyes from other teams to reassess long-running initiatives.

Build safe signals: create structured ways for staff to raise concerns without reputational risk.

Adjust incentives: link rewards to outcomes and learning, not only duration or endurance.

Time-box reinvestment: if continuing, limit additional resources and require a strict re-evaluation date.

Use dashboards that highlight remaining effort vs. expected gain so decisions are visible.

Opportunity cost: focuses on what is foregone by continuing a project, whereas sunk cost fallacy focuses on overweighing irrecoverable past investments.

Confirmation bias: connects because teams seek supportive evidence for prior choices; differs by being about information processing rather than investment-driven persistence.

Escalation of commitment: closely related and often a behavioral consequence; sunk cost fallacy is a common psychological driver behind escalation.

Decision hygiene: practical practices (gates, metrics) that reduce many biases, including sunk cost effects, by structuring choices.

Accountability mechanisms: systems like peer reviews that differ by creating external checks to counteract inward-driven persistence.

Loss aversion: a cognitive tendency that underpins sunk cost behavior by making prior loss feel more salient.

Post-mortem culture: when done constructively, it connects by turning past failures into learning rather than reputational damage that fuels sunk cost decisions.

Herd behavior: social dynamics that can magnify sunk cost tendencies when groups collectively commit to a path.

Project governance: structural controls that can prevent or enable sunk-cost-driven continuations depending on design.