What it is
A Minimum Viable Product (MVP) is the smallest version of a product that lets a team test a core assumption with real users and get real feedback — not the smallest version of the final product, but the smallest experiment that produces a meaningful learning. The term comes from Eric Ries’s Lean Startup, and the emphasis is deliberately on “viable,” not just “minimal”: an MVP still has to actually deliver value, or the test doesn’t tell you anything about real demand.
An MVP can take different forms depending on what you’re trying to learn — a landing page that measures signup intent, a concierge service where humans manually do what the product will eventually automate, or a narrow single-feature release to a small user segment.
When to use it
Use an MVP approach when the biggest risk to a new product or feature is whether anyone actually wants it — not how well it’s engineered. It’s the right move before committing significant engineering time to a new product line, a major pivot, or a feature nobody has validated demand for yet.
Common pitfalls
- Confusing “minimum” with “low quality.” An MVP that’s broken or unusable doesn’t test demand — it tests tolerance for bugs, which is a different and less useful signal.
- Building an MVP nobody asked for. The “minimum” should map to a genuine hypothesis about user value, not just be the smallest slice of a roadmap that was already decided.
- Never graduating past MVP. Some teams ship the MVP, see mediocre metrics, and declare the idea dead — without acknowledging the MVP was too thin to represent the real value proposition.
- Skipping the validation step entirely. An MVP only pays off if there’s a clear plan for what you’ll measure and what result would change your decision.