Minimum Viable Product (MVP) is the simplest version of a product that can be released to test a hypothesis with real users, popularized by Eric Ries’s The Lean Startup (2011). The concept revolutionized product development by replacing “build for months in secret” with “ship fast, learn, iterate.”
The Philosophy
Traditional product development followed waterfall: spend 6-18 months building features based on assumptions, launch with fanfare, discover users don’t want it. MVPs flip this: launch with bare-minimum features solving one core problem, measure user behavior (not opinions), and iterate based on data.
Famous MVP examples:
- Dropbox: Drew Houston’s 3-minute explainer video (2007) validated demand before building syncing tech
- Zappos: Nick Swinmurn photographed shoes at local stores, posted online, bought/shipped when ordered — proving people would buy shoes online
- Airbnb: Founders rented out their own apartment with photos on a basic website to test the concept
The Misconception
Many founders interpreted MVP as “ship broken, ugly products” — leading to the term “Minimum Lovable Product” (MLP) to emphasize quality within constraints. A true MVP isn’t half-assed; it’s ruthlessly focused on one use case done well enough to test the hypothesis.
Cultural Impact
#MVP influenced entire startup culture:
- Launch fast: “If you’re not embarrassed by your first version, you launched too late” (Reid Hoffman)
- Build in public: Indie hackers sharing revenue, metrics, and progress daily
- No-code MVPs: Tools like Webflow, Bubble, Airtable let non-technical founders test ideas in days
- Pivot culture: Changing direction based on MVP learnings (Slack started as a game, Instagram as Burbn check-in app)
By 2020s, “MVP” became startup jargon, sometimes misused to justify shipping incomplete products. But the core lesson endured: validate assumptions with real users before scaling.
References
- The Lean Startup by Eric Ries - Book, 2011
- Dropbox MVP Video - Original 2007 demo