The Lean Startup
Finished Finished May 2026
About
Eric Ries's method for building companies under extreme uncertainty. Instead of elaborate plans and guesswork, treat the startup as a series of experiments: ship a minimum viable product, measure real customer behavior, and learn whether to pivot or persevere — driving toward validated learning with as little waste as possible.
People & Cases
IMVU — Ries's own startup and the book's origin story — the cautionary tale of hitting every milestone while learning nothing customers actually wanted.
Dropbox — Drew Houston's MVP was a simple explainer video that validated demand and a waiting list before the full product was built.
Zappos — Nick Swinmurn tested demand by photographing shoes in local stores and selling them online before ever holding inventory.
Toyota (Taiichi Ohno) — The lean-manufacturing roots Ries adapts for startups — small batches, 'go and see' (genchi genbutsu), and the Five Whys.
Chapter by Chapter
Part One — Vision
What a startup really is, and what counts as progress
The distilled idea. A startup is not a smaller version of a big company; it’s an institution built to create something new under extreme uncertainty. So its job isn’t execution against a plan — it’s learning what to build in the first place.
The chapters.
- Start — Entrepreneurship is management. The Lean Startup applies to anyone creating a new product or service under uncertainty, in any size of organization.
- Define — A startup is a human institution designed to create something new under extreme uncertainty — regardless of sector, size, or funding.
- Learn — Validated learning is the true unit of progress: proving empirically what customers want, not rationalizing what you shipped.
- Experiment — Treat the vision as a set of testable hypotheses. Run experiments to check your riskiest assumptions before betting the company on them.
The mechanism worth remembering. Under uncertainty, the plan is the guess. Progress isn’t shipping features — it’s learning, fast and cheaply, whether the guess is right.
Part Two — Steer
The Build–Measure–Learn loop, and turning the wheel
The distilled idea. A startup is a machine for converting ideas into products, measuring customer response, and learning. The goal is to get through that loop as fast as possible — and to know when to change direction.
The chapters.
- Leap — Name your leap-of-faith assumptions: the value hypothesis (does it deliver value?) and the growth hypothesis (how will it spread?). Go see customers directly.
- Test — Build a Minimum Viable Product: the least you can make to start the loop and test those assumptions with real people (an explainer video, a concierge service, a landing page).
- Measure — Use innovation accounting: baseline, tune, then decide. Prefer actionable metrics and cohort analysis over vanity totals.
- Pivot (or Persevere) — A pivot is a structured change to test a new fundamental hypothesis. Your runway is really the number of pivots you have left, so shorten the loop to earn more of them.
The mechanism worth remembering. Steering beats planning. Point the product at your assumptions, measure honestly, and let the data — not your ego — decide pivot or persevere.
Part Three — Accelerate
Going faster without losing the ability to learn
The distilled idea. Once the loop works, the task is to speed it up and scale it — while keeping the discipline that made early learning possible.
The chapters.
- Batch — Work in small batches. Smaller batches move through the loop faster and surface defects sooner, even though they feel less “efficient.”
- Grow — Sustainable growth comes from past customers via one of three engines of growth — sticky, viral, or paid. Pick one and focus.
- Adapt — Build an adaptive organization. Use the Five Whys to invest in fixes proportional to problems, and avoid it curdling into the “Five Blames.”
- Innovate — Nurture disruptive innovation even inside big companies: give innovation teams scarce-but-secure resources, independent authority, and a personal stake — a sandbox to experiment safely.
The mechanism worth remembering. Speed without discipline just reaches the wrong destination faster. Small batches, a clear growth engine, and root-cause learning let you accelerate and keep steering.
Epilogue — Waste Not
The larger argument
The distilled idea. The deepest waste isn’t inefficient building — it’s building the wrong thing efficiently. Ries’s call is to bring managerial discipline to innovation everywhere, so human effort and creativity aren’t squandered on products nobody wants.
The mechanism worth remembering. Ask not only “can we build this?” but “should we build this?” — and “how do we learn the fastest?” That question, applied relentlessly, is the whole method.
Vocabulary
Validated learning — Progress measured by demonstrating empirically what customers truly want, using real data from experiments — not by shipping features or rationalizing after the fact.
Build–Measure–Learn — The core feedback loop: turn ideas into a product (build), measure how customers actually respond (measure), and learn whether to pivot or persevere — minimizing the total time through the loop.
Minimum Viable Product (MVP) — The smallest version of a product that lets you begin the Build–Measure–Learn loop and test your riskiest assumptions with real customers.
Innovation accounting — A rigorous way to measure a startup's progress: set a baseline, tune the engine toward the ideal, then decide to pivot or persevere — using actionable, not vanity, metrics.
Pivot — A structured course correction designed to test a new fundamental hypothesis about the product, strategy, or engine of growth.
Vanity vs actionable metrics — Vanity metrics (raw totals that only ever climb) flatter but mislead; actionable metrics tie cause to effect and guide real decisions.
Engines of growth — The three mechanisms of sustainable growth — sticky (retention), viral (each user brings more), and paid (unit economics fund acquisition).
The Five Whys — Asking 'why' five times to trace a problem to its root cause, then investing in fixes proportional to the size of the problem.