Kill Hope Before Hope Kills You
Separate belief from hope, and refuse to launch until you're collecting winnings instead of making bets
- Difficulty
- Moderate
- Time to result
- ~days to results
- Steps
- 4
- Confidence
- 92%
An intellectual-honesty discipline for deciding whether a product is really working. Hope is confidence without basis; belief is grounded in your lived experience with the product, users, and data. The best product makers 'collect winnings' — they already know they have a hit before launch — rather than launching to find out. The core test: if you have to ask whether your product is an A, it isn't one.
Origin
Mark Pincus's philosophy, refined over multiple companies including the failure of Tribe and the four-times-killed 'Earth' metaverse project. He distinguishes a Minimum Viable Product from what he calls a Maximum Launchable Product.
Core principles
- 01Hope is confidence without basis — a prayer not founded in your experience with the product or its data
- 02Belief is grounded in real signal: you're addicted to it, friends love it, and the metrics work
- 03Collect winnings, don't make bets — great makers know they have a hit before they launch
- 04If you're asking whether your product is an A, it's not an A — you're full of hope
- 05The word 'viable' is where hope hides; kill 'viable' along with 'hope'
How to run it
- 1
Name the grade honestly
Force the question: is this an A, or a B+? If you find yourself asking 'could this be the one?' the honest answer is that it's an A-minus at best. The power is in admitting it's not it.
Pro tip Use the dating analogy: with the right person you know it and aren't asking; the doubt itself is the answer.
- 2
Test hope vs belief against real signal
Check whether your confidence rests on anything: do you personally love and use it, do friends you show it to love it, and do the metrics show it works? If not, you have hope, not belief.
Pro tip Ask 'did we have to wonder whether GPT was it?' — true signal is unambiguous and makes you dream of new things to do.
Watch out 'This next release will be magical' is the classic hope trap that keeps teams stuck on a losing idea.
- 3
Launch only a Maximum Launchable Product
Distinguish putting a product out to LEARN from launching one you believe will be a hit. Only call something a 'launch' when you believe — not hope — it will win; otherwise label it a learning release.
Pro tip Be crisp about which mode you're in before you ship; conflating the two is how viable-but-mediocre products go to market.
- 4
Pull the plug and mine the B+
When it's honestly a B+, decide what to do with that knowledge: kill it, or use it to learn and hunt for something proven or near-proven nearby. Pulling the plug frees enormous creative energy.
Pro tip Pincus found that within two weeks of killing his four-year project he was more inspired with ideas than he'd been in years.
Watch out Sunk cost is powerful — he killed the same project 'for the fourth time' after $25M and four years before it stuck.
In the wild
Pincus spent four years and $25 million building a web-browser game engine for his metaverse vision, chasing a big ambitious idea and never finding product-market fit. Two weeks before the interview he pulled the plug for the fourth time.
→ In the two weeks after killing it, he was more inspired around new ideas than he had been in four years.
At Tribe, Pincus knew the metrics weren't working — D30 retention was terrible and it was a 'sinking speedboat.' He recognized the signal but hadn't yet internalized cycling to more ideas.
→ He acknowledges that with a kill-hope, test-more-ideas attitude he would have massively changed his odds of success.
Common mistakes
Shipping a 'viable' product on hope
Treating 'minimum viable' as a green light because it MIGHT make it. 'Viable' smuggles hope in — a product being technically viable says nothing about whether real signal exists, so teams launch mediocre products and wait for magic.
Refusing to grade the product honestly
Avoiding the A-vs-B+ question keeps a founder emotionally invested in a losing idea. Without the honest admission that 'this isn't it,' you can't decide whether to kill it or learn from it, and you burn months on hope.
Is it for you?
Best for
Founders and product leaders deciding whether to keep pushing a product that has some traction but no clear breakout signal
Not ideal for
Very early exploration where you deliberately want to ship rough releases purely to learn, and premature grading would kill useful experiments
From the transcript
“Hope is confidence without basis.”
“I like to say they're collecting winnings. They're not making bets. They already know.”
“the difference between launching an MVP, a minimum viable product, and a maximum launchable product.”
“If you're asking whether or not your product is an A, it's not an A.”
“When you have lightning in a bottle, when you have true signal, everything works.”
From the episode
The hidden pattern behind successful products
Mark Pincus (founder of Zynga)