Fail Quick Product Innovation Loop
Launch useful experiments, learn quickly, and redirect resources
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 97%
The loop begins with a concrete market problem and a product small enough to test the proposed solution. Instead of waiting for certainty, the team launches, measures adoption, and watches for changes in the environment that may erase the original need. A weak result is diagnosed quickly: the problem, timing, positioning, distribution, or product itself may be responsible. The team records what the experiment revealed, then closes, revises, or redirects the offering before sunk costs create inertia. Failure is treated as an expected cost of innovation rather than a personal defeat. The resulting learning improves later product selection while preserving attention and capital for the few launches capable of becoming meaningful successes.
Origin
Extracted from Masters in Business after Jim Ross described the failed O-Strips ETF and the lessons he drew from launching products.
Core principles
- 01Meaningful innovation requires exposure to failure
- 02A real launch produces better evidence than endless preparation
- 03External changes can invalidate a sound original idea
- 04Failures deserve learning, not prolonged emotional attachment
- 05Resources should move toward products showing durable demand
How to run it
- 1
Define the problem
Specify the customer or market problem the product is intended to solve.
Pro tip Describe the problem independently of the proposed solution.
Watch out A memorable ticker or clever concept cannot compensate for a weak need.
- 2
Set success evidence
Choose measurable signals that would demonstrate adoption, retention, or sustained usefulness.
Pro tip Set thresholds before emotional investment in the launch grows.
Watch out Do not redefine success after weak results arrive.
- 3
Launch the credible test
Release the smallest version that can genuinely solve the problem and generate market evidence.
Pro tip Move fast without compromising legal, operational, or customer safeguards.
Watch out Waiting for every detail to be perfect can make the product years late.
- 4
Monitor the premise
Check whether the original problem still exists and whether outside developments have changed the opportunity.
Pro tip Track substitutes and infrastructure changes alongside product metrics.
Watch out A third party can eliminate the need even when execution is competent.
- 5
Diagnose and decide
Determine whether to improve, reposition, or close the product based on the evidence.
Pro tip Use a short written postmortem to separate facts from hindsight narratives.
Watch out Do not keep a failed product alive solely because of prior investment.
- 6
Transfer the learning
Apply the lesson to selection, timing, and design decisions for the next experiment.
Pro tip Preserve reusable insights even when the product is discontinued.
Watch out Failure without documented learning is merely repeated cost.
In the wild
Ross's team developed an ETF to solve a closing-price problem affecting Nasdaq stocks. After the product launched, Nasdaq fixed the underlying market problem, weakening the product's reason to exist. Attempts to reposition it as a technology-stock ETF failed, demonstrating how an external change can invalidate a sensible original premise.
→ The failed launch became a lesson in recognizing changed conditions and moving on quickly.
Common mistakes
Waiting for certainty
Trying to make every decision perfect can delay a product until the market opportunity has passed.
Confusing branding with demand
A strong ticker or memorable name can attract attention but cannot sustain a product whose underlying use case has disappeared.
Losing sleep over losers
Excessive attachment to failed experiments diverts attention from understanding and scaling successful products.
Is it for you?
Best for
It is best for teams launching novel products into changing or poorly understood markets.
Not ideal for
It is not ideal for safety-critical products where rapid launches could expose users to unacceptable harm.
From the transcript
“If you don't take risks and fail,”
“just feel quick, fail quick, feel quick,”
“learned from learn from it. Move on to the”
From the episode
Jim Ross Recounts the Rise of the SPYs