The smallest version of a product that lets a team test its core value hypothesis with real users. Conceived as an instrument for learning; widely repurposed as a euphemism for a cheap first release.
The question an MVP exists to answer is "should we keep investing in this?". The question it is usually built to answer is "can we ship something by Q3?". Those are different projects wearing the same acronym.
Last reviewed 3 July 2026 · Free and ungated
Whether the MVP is designed to learn or merely to launch is a question selected senior operators can settle before the investment escalates.
Challenge the assumptions before committingA minimum viable product is the smallest thing a team can put in front of real users that tests the riskiest assumption in the product idea, usually whether anyone wants it enough to use it, pay for it or change behaviour for it. The output that matters is validated learning; the artefact is disposable in principle, however it fares in practice.
Treated properly, an MVP is a decision tool: it converts an argument about the market into evidence, and the decision it feeds has three honest outcomes, invest further, change direction, or stop. That framing has consequences executives should hold onto when an MVP appears in a funding paper. It needs an explicit hypothesis, defined in advance of launch, and a genuine possibility of a negative verdict; an MVP whose only acceptable result is progression is a phase-one build with a fashionable name. It also needs someone empowered to act on a disappointing answer, which is organisationally harder than building the thing.