Canonical · Startup Fundamentals · Book

The Lean Startup / Minimum Viable Product

Eric Ries · 2011

"Startups should build-measure-learn with a minimum viable product to find product-market fit before scaling."

The idea

A startup isn't a smaller version of a big company — it's an organization searching for a business model that doesn't exist yet, under extreme uncertainty. Because of that, the traditional approach of writing a detailed plan and executing it for years is dangerous: you're just executing a guess. Instead, Ries argues you should build the smallest possible version of your product (a Minimum Viable Product), put it in front of real customers immediately, measure what actually happens, and use that data to decide whether to persevere or change direction ('pivot'). Repeat that loop as fast as possible.

Why it works

The mechanism is treating a business plan as a set of falsifiable hypotheses rather than a fixed roadmap. Every assumption — 'people want this,' 'they'll pay this much,' 'this is how they'll find us' — is treated as a guess to be tested with the cheapest possible experiment, not assumed true because it's in a slide deck. An MVP isn't a shoddy version of your final product; it's the minimum thing needed to run one valid experiment and get a real answer. Speed of the loop (build → measure → learn → repeat) matters more than the polish of any single iteration, because each loop is what converts uncertainty into knowledge.

The takeaway — recall it first

Check your understanding

What is the actual purpose of a Minimum Viable Product, according to Lean Startup thinking?

You're Probably Too Early

"Founders are far more likely to fail from being too early — building the right idea before the infrastructure or market is ready — than from being too late, which means a founder's own sense of 'someone must already be doing this' is a poor signal to act on."

Marc Andreessen (via The Startup Archive) · EssayContinue→