The strongest evidence of founder judgment can be the product you chose to stop. Building proves execution; ending work after the evidence changes proves that you can protect customers, runway and focus when continuation would be easier to defend.
In October 2011, Reed Hastings faced that decision at Netflix. Weeks earlier, the company had announced Qwikster, a separate service for its DVD-by-mail business. Customers would have needed two websites and two accounts for services that had previously lived together. The plan drew immediate criticism, and Netflix reversed it before Qwikster launched.
The form was asking the wrong question
A regional award form usually points founders toward visible output: products launched, markets entered, contracts signed, people hired.
That framing makes the application feel straightforward. Open the document, collect the wins, and describe what the company built.
Then one box changes the argument. It asks for evidence of leadership, resilience or sound decision-making. The newest product looks like the obvious answer, but the harder evidence may sit in the product line the team ended.
That work still consumed engineering time. Someone designed the flow, wrote the code, spoke to customers and argued for another month. Ending it meant accepting that the original reasoning no longer held. It also meant explaining the decision to people who had invested part of themselves in making it work.
A shutdown can look like failure when written as a timeline. It reads differently when written as a decision.
Qwikster showed what reversal costs
Netflix announced Qwikster during a difficult period for the company. The proposed separation followed changes to its DVD and streaming plans, and the customer response was severe. Hastings had already publicly defended the broader direction before reversing the Qwikster decision.
The New York Times documented the reversal at the time. Netflix would keep DVD rentals and streaming under the same website, and the Qwikster name would disappear before the separate service reached customers.
The useful part of this story is the sequence. Netflix did not discover that Qwikster lacked technical feasibility. The company discovered that the proposed experience created a cost customers did not want to carry. Continuing would have protected the appearance of consistency. Stopping protected the customer relationship from one additional complication.
That distinction matters for a founder with limited runway. A product line can function exactly as designed and still be the wrong allocation of the next eight weeks.
The bridge to an award application is direct: the abandoned line may reveal more about leadership than the surviving line. It shows what evidence changed the decision, what the team gave up, and what became possible after resources moved elsewhere.
Write the decision, not the shutdown
“We discontinued the product because it was unsuccessful” gives the reviewer no way to judge the call.
A stronger account starts with the constraint. Perhaps three credible customer requests were pulling one small team toward three different products. Perhaps a pilot required an architecture the core product could not support. Perhaps the new line generated interest but repeatedly failed to reach payment.
Then name the threshold. What did the team need to see by the next review point? A signed contract, repeated use, a shorter implementation path, or evidence that the work supported the main roadmap?
The threshold matters because hindsight can make every shutdown look obvious. It rarely felt obvious while salaries, customer promises and prior effort were still attached to the work.
This is also why a decision record is useful before the outcome is known. Write down:
- The evidence that would justify another cycle.
- The evidence that would trigger a pause.
- The work and cash released if the line ends.
- The customer commitment that still needs a clean handover.
That record protects the decision from becoming a story rewritten after the fact. It also gives you material for an investor update, board discussion or award form months later.
The same tension appears when customers pull a team in competing directions. I explored that constraint in Should I Pause an Engineering Offer When Customers Want Three Different Products?. The difficult part is rarely identifying attractive work. It is deciding which attractive work the company can afford to refuse.
Preserve the evidence before it disappears
Stopped work leaves fewer public traces than launched work. The landing page comes down. The demo stops receiving updates. Team members remember different reasons for the decision.
Before that happens, keep one short internal record. Include the original bet, the signal that weakened it, the options considered, the final call and the resource returned to the core business. Add what remains unresolved. A clean decision does not require pretending that every consequence is known.
Netflix’s Qwikster reversal remains memorable because the company changed course publicly after committing to the plan. Your decision may happen in Accra, Lagos, Berlin or a small team call across all three. The scale differs. The test is similar: when the evidence turns, can you stop defending yesterday’s plan?
On the award form, describe the line you ended with the same care you would give the product you launched. Name the constraint. Show the evidence. Explain what the decision preserved.
Comments
No comments yet.