What is a Minimum Viable Product (MVP)?
A Minimum Viable Product (MVP) is the smallest possible product version that delivers real user feedback to validate assumptions before you invest time and budget in full development.
DEFINITION
The Minimum Viable Product is a central concept from the Lean Startup. Eric Ries defines it as the version of a new product that achieves the maximum learning effect from validated insights with the smallest possible effort. An MVP is not an unfinished product and not a prototype in the classical sense. It is a tool for testing hypotheses. Only what answers a concrete question is built: Does this product solve the problem? Will users pay for it? Do they come back? Typical MVP forms are landing pages, paper prototypes, manual services or concierge MVPs. The most common mistake: an MVP that is actually a complete product and thereby wastes exactly the resources it was meant to save. A good MVP tests exactly one assumption, no more. If the assumption fails, rapid learning and a pivot follow. If it holds, investment continues.
CONNECTIONS
Leadership
Leaders transfer MVP thinking to internal projects: new formats, processes or structures are tested on a small scale first before rolling them out across the whole organisation.
Artificial Intelligence
AI projects benefit from the MVP approach: instead of developing a perfect model, the simplest version that real users can test in real situations is built first.
Project Management
An MVP helps projects gather early feedback and deliberately limit scope. That reduces the risk of delivering a product at the end that misses the need.
KEY POINTS
- An MVP is not a finished product but a learning tool.
- The MVP tests exactly one hypothesis, no more.
- Eric Ries coined the term in The Lean Startup (2011).
- Too many features in the MVP prevent clear learning.
- An MVP can be a landing page, a paper model or a manual service.
EXAMPLE
A team wants to develop a learning platform for leaders. Instead of building an app straight away, it creates a simple website describing the product and offering an email address for registration. After two weeks, 120 people have signed up without a single line of code being written for the platform. The hypothesis is validated; development can now begin.
MISCONCEPTIONS
Is an MVP a cheap, poor product?
No. An MVP is deliberately minimal but not poor. It should work well enough to test a specific assumption. Quality is relative: what is needed for testing must work.
Does an MVP have to be software or an app?
No. An MVP can be a landing page, a manual process, a paper prototype or even a phone call. The form depends on the hypothesis being tested.