Minimum Viable Product (MVP)
The smallest version of a product that delivers and validates core value.
An MVP is the leanest version of a product that still solves the core problem and can be put in front of real users to learn from. The goal is maximum validated learning for minimum effort — not a half-built product, but a focused one.
Good MVP design resists feature creep and nails one thing well, so the team can validate demand before investing in scale.
Key characteristics
- The smallest version that delivers real value and tests a core hypothesis.
- Goal is validated learning with minimal effort, not a feature-poor product.
- Reduces risk of building something nobody wants.
- Followed by iteration based on real usage and feedback.
Example
Before building a full marketplace, a team launches a single-category MVP to confirm buyers and sellers actually transact, then expands once proven.
Frequently asked questions
Does MVP mean a low-quality product?
No. It means minimal scope, not minimal quality. The smallest set of features should still work well and be usable — a broken MVP teaches you nothing reliable.
What is the difference between an MVP and a prototype?
A prototype simulates an idea for testing and usually isn't shipped. An MVP is a real, usable product released to real users to learn from actual behaviour.
Related terms
Need this done, not just defined?
I design and build it — Framer sites, product UI/UX, and more.