Quick-and-Cheap Bad-Idea Test
Assume every idea is flawed, then test it before attachment grows
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 98%
Treat every new idea as flawed before becoming emotionally or financially attached to it. Identify the assumption most likely to make the idea fail, then design the quickest, cheapest, easiest test that collides with real people. The goal is not to validate a polished concept or avoid embarrassment; it is to discover how reality differs from the story in your head. Results will often surprise you, but even a failed test usually contains a useful signal. Isolate that glimmer, alter the idea, and run another small test. This sequence replaces delayed certainty-seeking with a journey of discovery. Progress comes from short cycles of exposure, learning, and revision rather than business plans that protect an imagined success from evidence.
Origin
Randolph says every Netflix idea was flawed and that the company spent a year and a half on failed tests before finding its working model. He frames entrepreneurship as discovering why an idea is bad through quick experiments.
Core principles
- 01Every untested idea contains a hidden flaw
- 02The job is to discover why an idea is bad, not prove it is perfect
- 03Real-world contact creates learning that planning cannot
- 04Small surprising signals should direct the next iteration
How to run it
- 1
Assume a flaw
Write the idea without calling it good and identify the assumption most likely to break when customers encounter it.
Pro tip Ask what must be true for the idea to work.
Watch out Confidence and enthusiasm are not evidence.
- 2
Shrink the test
Find the quickest, cheapest, easiest way to expose the risky assumption to real behaviour.
Pro tip Test the assumption rather than building the whole product.
Watch out Do not make the test so artificial that no real customer choice occurs.
- 3
Collide with reality
Put the test in front of real people and observe actions, objections, and outcomes without defending the concept.
- 4
Find the glimmer
Look for the unexpected signal that reveals a better direction, even when the original idea fails.
Pro tip Record surprises before explaining them away.
- 5
Iterate the signal
Change the idea around what you learned and launch the next bounded test.
Pro tip Keep cycles short enough that failed versions remain cheap.
Watch out Waiting for certainty allows attachment and sunk cost to grow.
In the wild
A founder believes small retailers need an automated returns dashboard. Instead of building it, she offers ten retailers a manually produced weekly returns report and asks them to commit to a paid second month. Their objections reveal that reconciliation, not dashboards, is the urgent problem, so the next test focuses on that workflow.
→ The initial idea fails cheaply while exposing a more valuable problem to test.
Common mistakes
Waiting for a foolproof idea
More planning can make an idea feel safer without revealing how customers behave. Start with a bounded real-world test.
Treating failure as the end
A failed version often contains a signal about the problem or a different solution. Extract that signal before abandoning the learning.
Is it for you?
Best for
It is best for entrepreneurs and innovators evaluating a new product, offer, or operating idea under uncertainty.
Not ideal for
It is not ideal when a careless test could cause irreversible harm, violate ethics, or expose users to unacceptable risk.
From the transcript
“our job is to figure out why our idea is a bad idea”
“you figure out a quick and cheap and easy way to try it”
“that's when the learning begins”
From the episode
Marc Randolph: How Netflix Disrupted The Entertainment Industry
Marc Randolph