MVP
Minimum Viable Product
In short
An MVP is the simplest version of a product that real users can use, built to test a key assumption and learn as much as possible with the least effort.
What is an MVP?
An MVP, or Minimum Viable Product, is the smallest version of a product that delivers enough value for early users to try it and give meaningful feedback. The goal is learning: an MVP tests whether a core idea solves a real problem before a team invests months building a complete product. The term was coined by Frank Robinson in 2001 and popularized by the Lean Startup movement around 2011.
Teams usually build an MVP by identifying the riskiest assumption, such as whether people will pay for a feature, and cutting everything that does not help test it. The MVP is released, the team measures how people use it, and then it decides whether to improve the product, change direction (called a pivot), or stop. This loop is often described as build, measure, learn.
A popular illustration: if the goal is to help people get around, an MVP is not a single car wheel, which nobody can use, but a skateboard, which is basic yet actually gets someone from A to B. An MVP does not even have to be software; a landing page that collects sign-ups, or a service run by hand behind a simple website, can validate demand. Startups use MVPs to test new business ideas, and established companies use them to trial new features.
An MVP is often confused with a prototype. A prototype is usually an internal mockup for exploring a design and is not meant for real users, while an MVP is a working product that real users can use. In software architecture, MVP can also stand for Model-View-Presenter, a design pattern related to MVC that has nothing to do with product strategy.
Key takeaways
- An MVP is built to learn whether an idea works, not to be a finished product.
- It focuses on testing the riskiest assumption with the least effort.
- Minimum means small scope, but viable means it must still be usable and valuable.
- Feedback from an MVP decides whether to continue, pivot, or stop.
- An MVP is used by real users, unlike an internal prototype.
Readers ask
What is the difference between an MVP and a prototype?
A prototype is a rough model, such as clickable mockups, used to explore or explain a design, usually without real users. An MVP is a working product released to real users to test whether they actually want it.
How long should it take to build an MVP?
There is no fixed rule, but an MVP should be built as quickly as possible, typically in weeks rather than months, because its purpose is to start learning from real users early.
Does MVP mean low quality?
No. An MVP has a small scope, but what it does should work reliably; a buggy product can fail for reasons that have nothing to do with the idea being tested.
See also
- AgileTeams & Process, p. 2Agile is an approach to software development that delivers working software in small, frequent increments and adjusts plans based on regular feedback.
- User StoryTeams & Process, p. 30A user story is a short, plain-language description of a feature told from the user's point of view, explaining who wants it, what they want, and why.
- ScrumTeams & Process, p. 21Scrum is an Agile framework in which a small team delivers a product in fixed-length cycles called sprints, using defined roles, events, and artifacts.
- Technical DebtSoftware Architecture, p. 45Technical debt is the future cost of extra work created when developers choose a quick or limited solution now instead of a better approach that takes longer.
- MVCSoftware Architecture, p. 29MVC is an architectural pattern that splits an application into a Model for data and logic, a View for display, and a Controller that handles user input.
- Proof of ConceptTeams & Process, p. 19A proof of concept (PoC) is a small, quick experiment built to show that an idea or technology can work in practice before investing in building it properly.
Spotted a mistake or something missing on this page?Suggest an edit