Protocol

Judge the next tranche, not the money already gone

Past investment explains how you arrived here. It does not make the next investment worthwhile.

Before you use it

Use when
  • An ongoing project or plan has consumed meaningful time, money, effort, or reputation and you must decide whether to keep investing.
Avoid when
  • Past choices can create real future consequences. Contract penalties, transition costs, dependencies, learned assets, reputation effects, salvage value, completion benefits, and option value still count. Do not kill long-horizon work from one noisy period.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Prior investment can pull people toward continuation and hide the opportunity cost of alternatives. At a checkpoint, treat the next tranche as a fresh choice: compare future consequences and alternatives, then buy more commitment only when evidence earns it.

Steps

  1. Rewrite the choice: ‘From today, spend the next [time/money] for [remaining outcome]?’
  2. Exclude irrecoverable spend. Compare future costs and benefits, switching or exit costs, obligations, salvage or learning value, and the best alternative.
  3. If uncertainty can shrink, fund the smallest useful tranche and predefine the evidence for continue, pivot, or stop.

An example

A team has spent six months on an internal tool with weak adoption. It compares one more sprint with buying, simplifying, or stopping, then funds only a test of one adoption bottleneck.

Check your result

Could you justify the decision if the amount already spent were hidden but all future consequences stayed visible?

Keep this limit in mind

  • Past choices can create real future consequences. Contract penalties, transition costs, dependencies, learned assets, reputation effects, salvage value, completion benefits, and option value still count. Do not kill long-horizon work from one noisy period.

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Evidence and sources (4)
Supports

Meta-analytic research on escalation of commitment identifies multiple determinants and theoretical explanations rather than one universal cause.

The synthesis combines heterogeneous escalation settings; it should not be read as a single effect size that transfers unchanged to every project or personal decision.

Cleaning Up the Big Muddy: A Meta-Analytic Review of the Determinants of Escalation of Commitment · Abstract and meta-analytic overview

Supports

Classic field and questionnaire studies found greater persistence after prior investments of money, effort, or time, and some scenarios also showed higher estimates of project success after a sunk cost had been incurred.

The work is foundational but old, and several studies used hypothetical scenarios; it demonstrates a tendency, not that every continuation decision influenced by prior investment is irrational.

The psychology of sunk cost · Abstract

Supports

In resource-allocation setback experiments, opportunity costs were often omitted from the decision frame; making them more explicit shifted choices closer to traditional cost-benefit prescriptions.

The experiments do not establish that explicitly listing alternatives is sufficient to prevent escalation under organizational, political, contractual, or identity pressures.

Opportunity costs and the framing of resource allocation decisions · Abstract

Limits

A 2026 preregistered replication paper found only partial support for one influential personal-responsibility result and failed to replicate two regret-related escalation findings.

These replications challenge specific proposed mechanisms; they do not show that escalation of commitment or sunk-cost effects never occur.

A Replication and Extension of Three Studies Investigating Escalation of Commitment and Regret Aversion · Abstract

All sources (4)
Edition and review

Version 0.2.0 · Published

No review details are supplied for this edition.

Read this idea as JSON · Release details