Product roadmaps often suffer from the "sunk cost fallacy" – prioritizing features based on the resources already invested, rather than their future value. A study on airline loyalty programs found that carriers which expanded their route networks to serve existing customers actually lost market share to more agile competitors. Similarly, Netflix expanded its DVD rental service in the early 2000s, despite the rise of streaming. This common mistake leads to suboptimal resource allocation and missed opportunities. As a professional, you're likely to face similar dilemmas. By prioritizing features solely based on sunk costs, you risk undermining your product's long-term potential.
ren
Building & Strategy
The "Sunk Cost" Trap That's Killing Product Roadmaps
Airlines have lost over $10 billion in ticket revenue by following a single, well-intentioned strategy.
Key insights
Prioritize features based on their future value, not just sunk costs.
Regularly assess and prune non-essential projects or features.
Introduce a "stop doing" list to optimize resource allocation.
Make data-driven decisions, rather than relying on emotional attachment to sunk costs.
Go deeper
The sunk cost fallacy was first identified by psychologist Barry Schwartz in his 2003 book "The Paradox of Choice." The concept has since been applied to various fields, including economics and psychology. Companies like Netflix and airlines have lost billions due to this misguided approach. By understanding the sunk cost fallacy, you can avoid similar pitfalls.
The sunk cost fallacy is closely related to the concept of "sunk cost recovery" in economics. This phenomenon occurs when businesses attempt to recoup losses by doubling down on a failing strategy, rather than cutting their losses and moving on. In the context of product development, this can lead to further investment in a suboptimal feature, further exacerbating the problem.