The Lean
Startup
Build less, learn more, waste nothing. Replace elaborate planning with validated learning — and treat every launch as a test of a hypothesis.
The three phases
Each phase has a single discipline
Startups don't fail because they can't execute. They fail because they execute the wrong plan.
Before the Lean Startup, the dominant model for building new products was the business plan model: write a comprehensive plan, raise money against it, execute it, and launch. The problem is that the plan is almost always wrong, because it is built on assumptions that have never been tested against reality.
Eric Ries, drawing on lean manufacturing principles and Steve Blank's Customer Development methodology, developed the Lean Startup while leading IMVU between 2008 and 2011. His core insight: replace the plan with a loop.
The core insight
The fundamental shift the Lean Startup demands is a shift in what counts as progress. Traditional metrics measure output: features shipped, revenue generated. Lean Startup metrics measure learning: assumptions tested, hypotheses validated or invalidated.
- 1Write a falsifiable hypothesis — the single assumption that, if wrong, would cause your concept to fail.
- 2Build the minimum artifact to test that assumption. Not a product — a test.
- 3Measure what actually happened against the hypothesis. Use cohort analysis, not aggregate totals.
- 4Learn: was the hypothesis true or false? Pivot or persevere — then write the next hypothesis.
Real-world example
Dropbox did not build a product to validate their concept. Drew Houston made a three-minute video explaining how Dropbox would work. Overnight, the waitlist grew from 5,000 to 75,000. That video was an MVP — the minimum artifact needed to test the assumption that people wanted this product. The experiment cost almost nothing. The learning was worth millions.
When to use it
Use it when
- →Building a new product or business in significant uncertainty
- →You need to learn what customers actually want rather than what you assume
- →Resources are limited and every cycle must produce learning
- →You operate in a new, rapidly changing, or poorly understood market
Do not use it when
- ×The solution is known and the challenge is execution
- ×You operate in a regulated environment where the MVP cannot legally reach users
- ×Stakeholders require a committed delivery plan
Click any phase to see how it works
Click Build, Measure, or Learn to explore each phase. Click Pivot to see the eight pivot types. Switch between MVP types below the loop to see a real-world example of each.
Six versions, one loop
The Lean Startup did not emerge fully formed. It is the product of a lineage of related thinking that began a decade before Ries published the book. Select a version to see what changed.
Where this connects
The Lean Startup answers “what should we build and is it right?” These are the frameworks and methods that answer adjacent questions.
Sources & Further Reading
The Lean Startup
Eric Ries, 2011
The Startup Owner's Manual
Steve Blank and Bob Dorf, 2012
Running Lean
Ash Maurya, 2012
Continuous Discovery Habits
Teresa Torres, 2021