MVP (Minimum Viable Product)

The MVP is the smallest thing you can put in front of a real user that generates real learning: build the least that tests the riskiest assumption, ship it, learn, iterate. It is among the most valuable ideas in product development — and the most misused, because 'minimum' is forever being heard as 'unfinished' and 'viable' as 'cheap'.

What It Is

A Minimum Viable Product is the version of a product that delivers just enough value to attract real users while generating the evidence needed to guide what gets built next. Its purpose is learning under uncertainty: the MVP targets the riskiest assumption — will anyone want this, will they pay, does the mechanism work — with the minimum build that tests it. Viable is the operative word: it must genuinely work for the job it claims, not be a broken sketch. The MVP is a strategy, not a phase: the discipline repeats as each increment tests new assumptions, with the product growing through validated iterations.

Why It Matters to You

The executive tensions around MVPs are predictable and manageable. Against stakeholders: an MVP is not the finished product seen early, and managing that expectation is a communication task — what assumption is this testing, what will we learn, what does success look like. Against vanity: an MVP that ships fast but measures nothing generates motion, not knowledge — define the learning metric before building. And against permanent-minimum syndrome: some organisations use MVP language to avoid ever finishing anything. The strongest MVP briefs name their kill criteria too — what result would make us stop this line entirely?

When You'll Meet It

At product inception, feature launches, and innovation programmes. For each MVP, ask three questions: what is the riskiest assumption, what will we measure, and what would make us stop?