The Sunk Cost Effect in Product Design: Knowing When to Quit
How attachment to past work can quietly derail great products.

We have all heard this before:
"We can’t stop now. Look how much we’ve already invested.”
It sounds responsible. It sounds strong. It sounds like leadership. But sometimes, it is the most dangerous sentence in the room.
The sunk cost effect is the habit of continuing something just because we have already put time, money, or effort into it. Even when it no longer makes sense. Even when the chances of success are low.
Once we invest a lot into something, walking away feels like failure. It feels like we wasted our time. But past effort should not decide what we do next. What matters is the present situation and the future outcome. We should ask: Does this still make sense moving forward?
In product design, this happens more than we like to admit. A team may spend months researching and designing a feature. Leaders approve it. Developers begin building it. Then new information shows up. User testing reveals problems. The market changes. A competitor releases something better.
Designers raise concerns. But leadership says, “We already approved it,” or “Development has already started.” So the team pushes forward anyway. The result is often a rushed launch, low team morale, and a quiet feeling that the project has become something we just need to finish.
Here is a simple example. A company spends a year building a new online product. Right before launch, a major company releases a similar product for free. Competing is almost impossible. The smart move would be to stop and rethink the plan. But after a year of hard work, leadership decides to launch anyway. The choice is no longer about what is best. It is about not wanting the year to feel wasted.
History shows us this pattern too. The Concorde was a supersonic jet that could fly from London to New York in about three hours. It was fast and impressive. But it was a financial failure. Even after it was clear the plane would not make money, governments kept funding it. Too much had already been spent to quit. It took a tragic accident to finally shut the program down. Sometimes it takes a crisis to force people to stop.

The sunk cost effect is not about being smart or not. Even people who understand it still fall into it. We are human. We do not like admitting we were wrong. We do not want to look wasteful. We protect our pride. Sometimes ego becomes more important than the product itself.
Many teams use agile methods to reduce this risk. Working in short cycles and testing early can help. Prototyping before fully building something also helps. The less you invest upfront, the easier it is to change direction. The more time and money you put in, the harder it becomes to pivot.
Pay attention to the language people use. If you hear phrases like “We can’t go back now,” or “We’ve invested too much,” that is a warning sign. Pause and ask: Are we making this decision based on facts today, or emotions from the past?
We often hear, “Winners never quit.” But that is not always true. Sometimes quitting is the smartest move. Knowing when to stop takes discipline. It shows respect for time, money, and people.

The goal in product design is not to protect what we already built. The goal is to build what makes sense right now. And sometimes, that means having the courage to walk away.