principleDelivery & agility

Minimum Viable Product

The smallest product experiment that can deliver a meaningful experience to early users and generate validated learning about a critical business assumption.

Download Markdown (.md)

01What it means

A minimum viable product, or MVP, is a deliberately limited version of a product used to test important assumptions with real behavior and the least responsible investment. “Viable” means the experiment can produce credible learning and an acceptable user outcome; it does not mean releasing a careless fragment.[1][2]

Minimum scope with responsible learning quality An MVP minimizes investment—not coherence, ethics, or user outcome
Minimum
Smallest coherent scope for the critical assumptionRemove breadth that does not improve the learning decision
Viable
Credible evidence and acceptable user outcomeProtect accessibility, reliability, guardrails, and ethical boundaries

Viability means the release can produce credible behavioral learning for a specific decision and audience.

02Why it matters

Teams can spend months perfecting a solution before learning that the problem, audience, channel, or business model is wrong. An MVP links delivery to a learning goal, limits exposure, and creates evidence for whether to persevere, change direction, expand, or stop before larger costs accumulate.

03When to use it

Use an MVP when a new product or substantial proposition contains high-value uncertainty that real-world use can resolve. Define it after identifying the riskiest assumption. Do not use the label to justify inadequate safety, accessibility, privacy, reliability, or support for the users invited to participate.

04How it works

  1. State the critical assumption and the decision that evidence will inform.
  2. Choose a specific early audience, context, outcome, and ethical boundary for the experiment.
  3. Design the smallest coherent experience capable of testing the assumption.
  4. Set behavioral measures, qualitative learning methods, guardrails, and a review date before launch.
  5. Observe actual use, interpret evidence, and decide whether to iterate, scale, pivot, or stop.

05A practical example

Example

A workplace-learning team is unsure whether managers will return weekly for coaching prompts. Instead of building a full course platform, it offers one high-quality weekly scenario, response guidance, and reminders to a consenting cohort. Retention interviews and repeated use determine whether broader investment is warranted.

06Where it breaks

An MVP can produce misleading evidence if the audience, measure, or experiment does not match the strategic risk. Early adopters may not represent a broader market. A weak first experience can damage trust, and incremental feature delivery may be unsuitable where regulated or safety-critical systems require integrated assurance.

Common mistakes

  • Defining the MVP as the fewest features rather than the smallest credible learning vehicle.
  • Launching without a named assumption, decision rule, or measurement plan.
  • Using “minimum” to excuse poor quality or transfer avoidable risk to users.

07Sources

  1. Minimum Viable Product (MVP)Agile Alliance · Professional glossaryMinimum Viable Product (MVP)
  2. Eric RiesEric Ries · Creator websiteEric Ries
View saved topics

Start typing to search titles, definitions, categories, and frameworks.