MVP
Definition
MVP stands for Minimum Viable Product — the smallest, simplest version of a product that allows a team to test its most critical assumption about customer value with real users, generating validated learning with the least possible effort.
The term MVP was coined by Frank Robinson and popularized by Eric Ries in "The Lean Startup." It's one of the most misunderstood terms in product development — frequently confused with "beta version," "product v1," or simply "a product with fewer features."
What an MVP is:
- The minimum needed to test a specific hypothesis
- Designed to maximize learning per dollar/hour spent
- Targeted at early adopters who tolerate rough edges in exchange for early access
- A starting point for iteration, not a final state
What an MVP is not:
- A low-quality product (minimum viable doesn't mean minimum quality for its intended purpose)
- Just a feature-reduced version of the full product
- Something you ship and forget
- Always a software product (MVPs can be landing pages, concierge services, paper prototypes, Wizard of Oz experiments)
Classic MVP examples:
- Dropbox's MVP was a video explaining the product — Drew Houston gathered thousands of signups before writing a line of cloud sync code.
- Zappos's MVP was a static website with photos from local shoe stores — when someone ordered, the founder bought the shoes and shipped them manually.
- Airbnb's MVP was a simple website letting the founders rent out their own apartment.
The key question for any MVP: what is the riskiest assumption, and what is the cheapest way to test it? If customers won't pay for the core value, no amount of additional features will save the business.
MVP planning sessions frequently happen on whiteboards — teams sketch what's in scope, what's out, and what they're trying to learn. BoardSnap AI captures those sessions as structured action plans.
Examples
- Landing page MVP gathers 800 email signups before the product exists — validates demand hypothesis
- Concierge MVP: team manually delivers the service for 10 customers to learn what they actually need before automating
- Paper prototype MVP tested with 5 users in 2 hours — saves 3 weeks of engineering on a feature nobody wanted
- MVP scope defined on a whiteboard: 3 features in, 12 features out — team agrees on the one assumption they're testing
- Software MVP ships to 50 beta users, measuring activation rate to validate the core value proposition
Snap a mvp. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.