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. 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.
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.
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