Experiment & MVP
A chapter summary from The Lean Startup by Eric Ries.
“The minimum viable product is the smallest version of the offering that can produce real customer feedback.”
The minimum viable product is the smallest version of the offering that can produce real customer feedback. It is not the smallest version of the planned product; it is the smallest version of any product that can answer the riskiest unanswered question. Sometimes the MVP is a landing page with a signup button. Sometimes it is a concierge service done entirely by hand. Sometimes it is a video describing the product before any code is written.
The hardest discipline of MVP work is willingness to be embarrassed. Founders who wait until the product feels ready almost always wait too long, and the version they ship has been built around their own assumptions instead of around real customer feedback. The MVP is supposed to feel premature. If it does not, you waited too long.
Ries gives specific patterns. The smoke-test MVP — a landing page promising a product that doesn't exist yet, designed to measure whether anyone will sign up. The Wizard-of-Oz MVP — a product that appears automated but is run by humans in the back room, designed to test demand before building automation. The concierge MVP — a hand-delivered service for the first dozen customers, designed to learn what they actually need before generalizing.
All three patterns trade engineering work for learning speed. The learning comes back to the team in days instead of months, and the next iteration is informed by data rather than guesses.
Ries catalogs the forms an MVP can take, each chosen to answer a specific risky question as cheaply as possible. The concierge MVP delivers the service entirely by hand to a handful of customers before any system is built. The Wizard-of-Oz MVP shows customers a polished front end while humans secretly perform the work behind the curtain. The smoke-test landing page measures whether anyone will click 'buy' before the product exists, and Dropbox's famous explainer video validated demand for a product that had barely been built. The unifying principle is to ship the smallest thing that starts the learning loop, which requires overcoming the founder's instinct to perfect the product first — Ries's blunt guidance is that if you are not embarrassed by your first version, you shipped too late. Quality, in this frame, is measured against validated learning rather than polish: a feature is only 'high quality' if it helps confirm or refute a hypothesis about what customers value. The MVP feels reckless precisely because it exposes an unfinished product, but its actual function is to de-risk the much larger bet of building the full product on untested assumptions.
A short summary — and that's the point. Read Stacks chapters are deliberately tight. The full The Lean Startup edition has the examples, the longer argument, and the moments worth re-reading. If this resonated, the Amazon link below buys the actual book and supports the author.
One chapter a week — curated, not algorithm-picked.
If this resonated, the free weekly Read Stacks email sends one curated 4-book stack with the chapter we'd open first. No spam, unsubscribe anytime.
More from The Lean Startup
The Lean Startup sits in a curated reading path — each pairing it with other books that sharpen the same idea. Three nearest peers:
- The 7 Habits of Highly Effective Peopleby Stephen R. CoveyFrom Lead with growth
Stephen Covey converts the first two books into a daily operating system. His seven habits aren't a productivity hack; they're a behavioural framework that compounds character. Begin with the end in mind. First things first. Think win-win. Seek first to understand. Read after Mindset + Drive, the seven habits become the visible expression of a growth-oriented, intrinsically-motivated operator over months and years.
Read first chapter - Driveby Daniel H. PinkFrom Lead with growth
Daniel Pink picks up where Dweck leaves off and asks the next obvious question: if growth is possible, what actually sustains it? His answer — autonomy, mastery, purpose — is the operating principle that explains why most workplace motivation systems fail and what the alternative looks like. Read after Mindset, Drive shows what to BUILD INTO your environment so the growth mindset has fuel, not just permission.
Read first chapter - Mindsetby Carol S. DweckFrom Lead with growth
Start with Carol Dweck because the diagnosis comes first. The fixed-vs-growth mindset distinction is the one piece of psychological vocabulary you cannot afford to skip. Once you can name which mindset is firing in a specific situation — your reaction to feedback, your treatment of your own kids, the way you praise a teammate — every subsequent layer of growth has somewhere to land. Without this foundation, the rest of the stack reads as good advice that doesn't stick.
Read first chapter
From Read Stacks · Learn
If you just read a chapter summary…
You're using the navigation tool the way it was designed to be used. Two short essays on the meta-skill — what summaries actually preserve, and the six retention techniques that decide whether what you just read is still useful six months from now.
- Are book summaries actually useful, or am I just cheating?
Chapter summaries are a navigation tool, not a substitute. Used right, they help you read more books fully — by helping you avoid the wrong ones. Used wrong, they're a comfort blanket that lets you feel like you're reading without engaging with the material.
6 min read
- I read a lot of books but can't remember anything. What works?
Forgetting most of what you read is normal, not a personal failing — your brain wasn't designed to retain prose at the rate modern readers consume it. The practices that DO work share one thing: they force you to USE the material instead of just consuming it. Six specific techniques, each tested across decades.
7 min read