Minimum Viable Product Explainer
A minimum viable product, or MVP, is the smallest useful version of an offering that can test an important assumption with real users. “Minimum” refers to the least scope needed for credible learning. “Viable” means the experience is coherent and safe enough that feedback reflects the idea rather than obvious neglect.
A team should begin with a hypothesis: a specific customer has a particular problem and will take a meaningful action when offered a proposed solution. The MVP might be a manual service, a limited feature set, a prototype, a landing-page test, or a pilot. The form should match the uncertainty being tested.
Before launch, define evidence that would support, weaken, or invalidate the hypothesis. Sign-ups alone may not prove value; completion, repeat use, willingness to pay, time saved, or problem resolution may be stronger. Qualitative interviews explain why the observed behavior occurred.
An MVP is not permission to ignore security, accessibility, legal duties, or customer trust. A test can also be too narrow to reveal operational cost or retention. Limit exposure, disclose constraints honestly, collect only necessary data, and decide whether to iterate, pivot, expand, or stop based on the evidence.
Choose the uncertainty most likely to make the idea fail if it is wrong.
Build only enough to obtain credible evidence about that assumption.
The experience must be safe, understandable, and useful enough for feedback to be meaningful.
Broken basics can make a good idea look bad.
State in advance what result would support iteration, expansion, a pivot, or stopping.
Learning is valuable only when it changes the next choice.
Explore more "Explainers"
Discover additional explainers across politics, science, business, technology, and other fields. Each explainer breaks down a complex idea into clear, everyday language—helping you better understand how major concepts, systems, and debates shape the world around us.