Sunk Cost Fallacy.

01Overview

The sunk cost fallacy is the tendency to continue an investment because of already-committed resources — time, money, effort — rather than because the future value justifies continuing. Rational economics says past costs are gone regardless of what you do next; only future costs and benefits matter. Human psychology disagrees.

For designers, this matters in two directions: users stay in products they don't love because they've invested in them, and teams build products they shouldn't because they've already spent so much building them. Both are the same bias operating on different people.

02Detailed explanation

Classic demonstration: a theatre company has two performances — one ticket was bought at full price, one as a discount. Both are the same show. During a snowstorm, people in the full-price group are measurably more likely to brave the weather to attend, even though the show experience is identical. The investment already made changes the decision about a future action — even though the past cost is identically irretrievable in both cases.

In product terms: the more time a user has invested in learning a product, the higher the cancellation barrier — not because the product is good, but because leaving "wastes" the accumulated investment. This is closely related to loss aversion (the invested resources feel like they would be "lost" if you quit) and effort justification (effort increases perceived value).

Gamification and streaks work partly on this mechanism: your 40-day Duolingo streak feels like something you'll lose if you stop, even though the streak is only relevant to your future motivation, not your past learning. The streak is a manufactured sunk cost.

03Why it exists

Evolutionary and social pressure to "finish what you started" — abandonment is a social failure marker in many cultures. The mental accounting of "sunk" resources also prevents the brain from having to re-evaluate a decision already made, which is cognitively expensive.

There is also an error-correction argument: if the brain fully discounted sunk costs, it would be vulnerable to manipulation by anyone who could get a small initial commitment out of it (the foot-in-the-door technique works partly for this reason). Sunk cost sensitivity is a partial defence against being easily redirected.

04Effects on users

• Users continue subscriptions past their use date because they "paid for the month" — even when they haven't opened the app in three weeks.
• Partially completed onboarding creates completion pull: finishing feels better than abandoning, even if the user isn't sure they want the product.
• Long form submissions get completed at higher rates when progress is shown — abandonment means "losing" the work already done.
• Gaming streaks work as sunk cost traps: the fear of losing accumulated progress outweighs the motivation to build it.

05Effects on designers & teams

The sunk cost fallacy may be more damaging inside product teams than it is in users:

• Feature retention: "We built it, we can't remove it" — the investment in building a feature becomes the argument for keeping it, long after it's been shown to be unused.
• Design debt: continuing to patch old code instead of rebuilding cleanly because "so much has been invested" in the old architecture, even when the patch cost has now exceeded the rebuild cost.
• Research direction: continuing down a research path because you've "already done three rounds of interviews" even when the direction is clearly wrong.

6Introspective view

Look inward. Teams keep investing in failing features or research directions because of resources already spent.

From an introspective perspective, ask how Sunk-Cost Fallacy may already be shaping your research, critique, planning, and interpretation — not only what users encounter in the finished interface.

7Extrospective view

Look outward. Accumulated progress (streaks, completion) makes users reluctant to abandon — which can aid retention or trap them.

From an extrospective perspective, Sunk-Cost Fallacy is a property of the product experience itself — visible in pricing, copy, defaults, layout, and the moments where users decide whether to continue, convert, or leave.

08Practical takeaways

• Show progress honestly: "40% complete" creates pull; but if users aren't likely to want the product, you're converting them into churners-with-grudges.
• Use streaks to help users reach goals they actually have, not to trap them in products they're ambivalent about.
• Design off-ramps: if a user has been inactive for 30 days and logged back in, they're probably evaluating. Give them a clean path out — it preserves goodwill even in churn.
• For your team: when a feature has sunk cost defenders, run the "if we hadn't built this yet, would we build it today?" test. If the honest answer is no, that answers the question.
• Don't weaponise the fallacy: making cancellation harder because users have invested more is dark-retention, not good product design.

09Design examples

10Ethical risks

Sunk cost is the psychological engine behind a lot of dark-retention patterns — hiding the cancel button, making cancellation a 7-step phone-call process, sending "you'll lose all your data" emails when the data would actually be exportable.

The standard: if a user has decided to leave, help them leave gracefully. Holding them by their sunk costs is not retention — it's hostage-keeping. Users who leave gracefully come back; users who escape begrudgingly become the loudest critics. The long-term cost of dark retention almost always exceeds its short-term gains.

11Related biases