Throwing Good Money After Bad
Hal Arkes and Catherine Blumer published a defining study on the sunk cost fallacy in 1985. They found that people who paid full price for theater tickets were more likely to attend the performance than those who received a discount, even when both groups had identical interest in the show. The money already spent, which was irrecoverable regardless, influenced the decision to attend.
This is the sunk cost fallacy: the tendency to continue investing in something because of what you've already invested, rather than based on future value. Economists call it irrational because past costs shouldn't influence forward-looking decisions. But humans aren't economists. We're loss-averse animals who struggle to write off investments.
In product design, the sunk cost fallacy is both a retention mechanism and a warning sign. Understanding the difference determines whether you're building a product that genuinely serves users or one that traps them.
Why We Can't Let Go
The sunk cost fallacy is driven by several interacting psychological mechanisms.
Loss aversion is the primary driver. Abandoning a project or product where you've invested time, money, or effort feels like confirming a loss. Continuing feels like preserving the possibility of eventual return on investment. Kahneman and Tversky's work on prospect theory explains why: the pain of realized loss is disproportionately larger than the pain of continued investment.
Cognitive dissonance, identified by Leon Festinger, plays a supporting role. People need their actions to be consistent with their beliefs. If you've invested heavily in a product, admitting it's not working creates dissonance between the action (investing) and the belief (this investment was a mistake). Continuing to use the product resolves the dissonance by maintaining the belief that the investment was justified.
Escalation of commitment, studied extensively by Barry Staw, occurs when initial investment leads to increased investment in an attempt to justify the original decision. This creates a cycle where each additional investment makes abandonment feel more costly, leading to more investment.
Waste aversion is distinct from loss aversion. Research by Christopher Olivola has shown that people have a specific aversion to waste, not just loss. Abandoning a product means the time and effort invested was "wasted," which triggers a negative emotional response separate from the economic calculation.
Sunk Costs in the Product Lifecycle
User Onboarding Investment
Onboarding creates the first sunk costs. Users who spend hours setting up a product, importing data, and learning the interface have invested significant effort. This investment makes them reluctant to switch, even if a competitor offers a better solution.
This is the double-edged sword of thorough onboarding. The same investment that creates valuable endowment effects also creates sunk costs that can trap users in suboptimal products. The distinction lies in whether the user continues to derive value from the setup investment. If the data they imported and the workflows they built continue to serve them, that's endowment. If they're staying primarily because they can't face redoing the setup elsewhere, that's sunk cost reasoning.
Subscription Duration and Loyalty
Long-tenure users are disproportionately influenced by sunk costs. Someone who has paid for a product for three years has accumulated a significant monetary investment. Canceling feels like admitting those years of payments were wasted, even if the product no longer meets their needs.
This creates a dangerous metric illusion. Retention rates among long-tenure users can look healthy while satisfaction is declining. The users aren't staying because they're happy. They're staying because leaving feels too costly. This is "zombie retention" and it's a leading indicator of eventual churn, because the sunk cost threshold has a breaking point.
Feature Investment and Platform Lock-in
Users who have built extensive customizations, automations, or integrations face enormous sunk costs when considering alternatives. A team that has spent months building custom workflows in a project management tool has invested labor that doesn't transfer. Switching means starting over.
Platform ecosystems amplify this effect. When users have invested across multiple integrated products, the sunk cost of switching isn't just one tool. It's the entire ecosystem of connected workflows.
When Sunk Cost Retention Fails
Sunk cost retention is inherently fragile because it's based on avoiding pain rather than pursuing value. Several scenarios can break the sunk cost barrier:
A forcing function that disrupts the status quo. A price increase, a major feature change, or a migration requirement forces users to actively re-evaluate rather than passively continuing. During these moments, the sunk cost spell breaks because users are already experiencing the pain of change.
A compelling enough alternative that the perceived gain exceeds the sunk cost pain. When a competitor offers dramatically better functionality plus a migration path, the forward-looking value overwhelms the backward-looking cost.
Accumulated frustration that eventually exceeds sunk cost tolerance. Users who are staying for the wrong reasons are accumulating negative sentiment. Each bad experience adds to the frustration balance. When frustration exceeds the sunk cost anchor, the departure is often sudden and irreversible.
Social influence from peers who have already switched. When colleagues or industry peers switch to an alternative and report positive experiences, it reduces the perceived risk and reframes switching as progress rather than loss.
Building Products Worth Staying For
The alternative to sunk cost retention is genuine value retention: users who stay because the product continues to deliver outcomes they care about.
The key differences between sunk cost retention and value retention are measurable:
- Value-retained users actively use new features and expand their usage over time. Sunk-cost-retained users use the same narrow feature set they always have.
- Value-retained users recommend the product to others. Sunk-cost-retained users warn others about switching costs.
- Value-retained users upgrade willingly when they see value in higher tiers. Sunk-cost-retained users resist any change, including upgrades.
- Value-retained users engage with product updates and communications. Sunk-cost-retained users ignore everything except billing notifications.
Designing for Forward-Looking Value
Products that retain through value rather than sunk costs share several characteristics:
Continuous value delivery through regular improvements that address evolving user needs. If the product is better today than it was six months ago, users have a forward-looking reason to stay.
Low switching costs by design might sound counterintuitive, but making it easy to leave builds confidence in staying. Products that offer robust data export, standard file formats, and API access signal that they're confident in their ongoing value. Users who know they can leave easily are more likely to stay by choice.
Transparent communication about the product's direction helps users make informed decisions. Users who understand the roadmap can evaluate whether the product's future aligns with their needs.
Regular value confirmation through usage reports, ROI calculations, and impact summaries reminds users of the ongoing value they're receiving. This shifts attention from past investment to current returns.
Measuring Sunk Cost vs. Value Retention
Distinguishing between sunk cost retention and value retention requires looking beyond surface-level retention metrics:
- Feature adoption breadth: Value-retained users explore and adopt new capabilities. Sunk-cost-retained users stick to established patterns.
- Net Promoter Score by tenure: If NPS declines with tenure while retention stays stable, sunk costs are likely propping up the numbers.
- Expansion revenue: Value-retained users upgrade and expand. Sunk-cost-retained users maintain or downgrade.
- Support ticket sentiment: Value-retained users ask about capabilities. Sunk-cost-retained users complain about limitations.
- Reactivation after churn: Sunk-cost churners rarely return. Value churners (who left for situational reasons) often do.
These metrics together paint a picture of whether your retention is built on a foundation of value or a house of psychological cards.
Frequently Asked Questions
What is the sunk cost fallacy?
The sunk cost fallacy is the tendency to continue investing in something because of past investment, rather than based on expected future returns. Hal Arkes and Catherine Blumer's research showed this pattern across many contexts, from theater tickets to business investments.
How does the sunk cost fallacy affect product retention?
Users who have invested significant time, money, or effort in a product are reluctant to switch, even when alternatives are better. This creates artificially high retention rates that mask declining satisfaction and eventual churn.
Is sunk cost retention bad for business?
In the short term, it maintains revenue. In the long term, it's fragile. Sunk-cost-retained users don't expand, don't refer, and eventually churn when a forcing function breaks the inertia. Products built on genuine value retention are more durable and generate better unit economics.
How can I tell if my users are staying because of sunk costs?
Look for declining NPS alongside stable retention, low feature adoption breadth, minimal expansion revenue, and complaint-heavy support interactions. Users staying for the wrong reasons show specific behavioral patterns that differ from genuinely satisfied users.
Should I make switching harder to improve retention?
No. Increasing switching costs builds sunk cost retention, which is fragile and corrosive to brand perception. Making it easy to leave but hard to want to leave is the better strategy. Products that are confident in their ongoing value don't need to trap users.