When to let go of an idea before it's too late

This is perhaps the hardest question in product management: not “what should we do next?” but “should we keep going at all?” Let's look at how to tell a temporary difficulty from a real “time to stop” signal.

The first dangerous situation is when the team rushes to build and launch the product, skipping the stage of testing hypotheses about the customer. It seems faster that way. In reality, it often leads to setbacks and lost months, because the product is built on untested assumptions.

The second dangerous situation arises after launch: the team starts actively scaling a model that has not actually been validated yet, chasing growth rather than sustainable economics.

A good, if painful, example is the story of Quibi. The company raised $1.75 billion before it even launched and assembled a star team and celebrities for its content, only to shut down just six months after launch. The problem wasn't money or execution: the founders bet tens of millions on the untested hypothesis that people needed short premium video content specifically for “moments on the go,” such as on the subway, in line or between tasks. The hypothesis was never tested cheaply on a small audience. Instead, they immediately built a full-fledged product and began a large-scale launch, with a T-Mobile partnership and content licensing worth millions of dollars. When it turned out that the audience was not willing to pay and did not watch the content to the end, it was too late to change anything: too much had been invested in infrastructure that could not quickly be turned in another direction. Babson College entrepreneurship professor Hiroyuki Yamakawa, commenting on this story, gives Quibi's leadership credit for stopping rather than continuing to burn money on a service that was clearly not taking off, and sums it up in a simple rule: the sooner you stop it, the better for everyone.

There is a simple practical test that helps you avoid a Quibi-scale failure. If the team asks, “Give us another six months and a little more money, and we'll definitely get through this slump,” then, in the experience of seasoned executives, the right answer is more often “no.” Companies are rarely disciplined enough to shut down projects in time, and it is almost always better to make this decision earlier than seems necessary.

Three questions worth asking yourself before continuing. Is user retention growing, even slowly, after several honest attempts to improve it? Do the product's economics add up structurally, with any problems coming down to execution alone? And does the team still have substantive ideas for development, not just cosmetic tweaks? If the answer to all three questions is “no,” that's a strong signal to stop, and the sooner you do, the lower the cost of stopping.

And finally: abandoning an idea is also a decision based on data, not on team fatigue or a stubborn unwillingness to admit a mistake.

Sources:

1. Babson Thought & Action — The Lessons Learned from a $1.7 Billion Failure
2. Yahoo Finance — Quibi shuts down: Why the $1.75 billion streaming app failed
3. Failory — 7 Reasons Quibi Failed Despite Raising $1.8B