Skip to content
Module
Product and data

MVP (minimum viable product): definition and examples

An MVP, or minimum viable product, is the smallest version of a product that lets a team test a hypothesis with real users. The term is credited to Frank Robinson (2001); Steve Blank and then Eric Ries, in The Lean Startup, popularized it as part of a build, measure, learn loop. An MVP is therefore judged by what it teaches the team, not by how many features it includes.

Definition written by Alex Dionisio, Senior Product Manager. Updated November 13, 2026.

Why it matters for a PM

An MVP protects the team from the most expensive risk of all: spending months building something nobody wants. For a PM, it forces a clear statement of the riskiest assumption and of the evidence that would confirm it, which turns a debate of opinions into an experiment. It also makes it possible to drop an idea early without drama.

Example

A team is considering a meeting room booking service for coworking spaces. Instead of building the platform, it publishes a page describing the offer with a booking form that a team member handles manually for a month. The number of confirmed bookings and feedback from the first customers show whether automation is worth it.

MVP vs prototype vs proof of concept vs beta: what is the difference?

A prototype explores a solution, often without users in a real situation: a clickable mockup, a usability test. A proof of concept (POC) checks that something is technically feasible, for instance that an AI model reaches the accuracy you need on your own data. A beta is a nearly finished version opened to a limited group to iron out the last defects. An MVP tests a value or market hypothesis: do people want this enough to commit to it?

Confusing them has a price. A team that thinks it is launching an MVP while actually building a beta spends months on polish before checking demand. Conversely, presenting a technical proof of concept as market validation gives leadership false comfort.

How do you choose the right form of MVP?

Start from the riskiest assumption. If the doubt is about interest, a page describing the offer and counting sign-ups or pre-orders may be enough. If the doubt is about the value delivered, a service run by hand, sometimes presented as automated, lets you observe real usage before writing any code. If the doubt is about repeat use, you need a working version, however narrow, used over several weeks.

Then pick a signal that costs the user something: a payment, time, data they hand over. Interest expressed in interviews or surveys tends to overstate demand. Set the length of the experiment and the decision threshold before launch as well, so the target does not move once the numbers come in.

What should you ask before launching an MVP?

Which hypothesis are we testing, and what will we do if it turns out to be wrong? How many users do we need for the result to mean something? Who handles the manual work hidden behind the experience, and how long can we keep it up? What are we promising early customers about their data, support and continuity of service?

That last question is often skipped. An MVP reaches real customers; if it shuts down, they need to be told, refunded or helped toward another option. Planning the exit from day one is part of a well-designed experiment, and it protects the trust of the people who agreed to try a product that is still rough around the edges.

What happens after an MVP?

There are three possible outcomes. A clear positive signal means investing in the next version, knowing that an MVP's code often has to be rebuilt. A negative signal means stopping, or changing the underlying hypothesis, which Eric Ries calls a pivot. An ambiguous signal, which is common, calls for a tighter experiment with a narrower audience or a sharper measure, rather than leaving an inconclusive version running forever. Whatever the outcome, writing down what the team learned keeps the next debate grounded in evidence instead of memory.

Key points

  • Start from a precise hypothesis and the signal that would validate or invalidate it.
  • An MVP can be a landing page, a manual service or a prototype, not necessarily code.
  • Minimum does not mean sloppy: the experience must stay credible enough to produce a reliable signal.
  • Decide in advance what you will do after each possible result.

Common mistakes

  • Calling a late, full first release an MVP.
  • Choosing the scope from accumulated requests rather than from the hypothesis to test.
  • Launching without a metric or success criterion, then interpreting the result after the fact.
  • Leaving an MVP in production indefinitely without deciding what comes next.

Go further with Module

The courses and lessons that cover this concept:

Guide on this topic