Operations · 3 min read
The smallest version of your idea that can survive in the wild. Not a prototype. Not a beta. The cheapest, ugliest thing that actually solves the problem.
In 2007, Drew Houston wanted to build Dropbox. He had a problem: building it would take years, and he had no way of knowing whether anyone would actually use it. So he didn't build it. He made a three-minute video.
The video showed a fake version of Dropbox doing what the real product would eventually do. He posted it online. His email signup list went from 5,000 people to 75,000 people overnight. That was his answer. Demand confirmed. Now he could build the real thing, knowing people wanted it.
That video was a Minimum Viable Product. The cheapest possible test of the idea before committing real resources.
The concept was popularized by Eric Ries in his book The Lean Startup, and it has since become one of the most quoted (and most misunderstood) ideas in modern entrepreneurship. The misunderstanding usually goes like this: people hear "minimum viable" and they hear "small." They build a small version of their full idea. A simpler website. A smaller restaurant. A lighter version of the eventual product.
That isn't what an MVP is.
An MVP is the smallest thing you can build that tests the riskiest assumption in your idea. The question it answers is not "is my product working?" but "is anyone going to want this?"
A common visualization makes this clear. Imagine you're building a car. The wrong way to MVP it: build a wheel, then an axle, then a chassis, then add a body. Each step on its own is useless. The customer can't ride a wheel. They get nothing until the whole car exists.
The right way: start with a skateboard. Then upgrade to a scooter. Then a bicycle. Then a motorcycle. Then a car. At every stage, the customer can get somewhere. Each version is useful on its own, and each one teaches you something the next version improves on.
This is the heart of the concept. An MVP isn't a smaller version of the final thing. It's the simplest possible version of the value the final thing delivers.
Some famous MVPs were almost embarrassingly simple. Zappos started as a website with photos of shoes the founder had taken at local stores. When someone bought a pair, he'd go buy them in person and ship them. There was no warehouse, no inventory, no supply chain. The MVP was a way to test whether people would buy shoes online at all. Once that was confirmed, the rest could be built.
The MVP question is uncomfortable because it forces you to put something ugly in front of real people before you're ready. But that discomfort is exactly the point. The alternative is spending two years building something polished that no one wants.
Why it matters
Most failed businesses didn't fail because the product was bad. They failed because the founders spent too long building something nobody wanted. The MVP is how you find out, cheap and fast, before the money runs out.
See also