What Is a Minimum Viable Product (MVP)?
A Minimum Viable Product (MVP) is the smallest version of a product that lets you test a core hypothesis with real users. It is not a half-built product or a demo. It is a functional product with just enough features to attract early adopters, validate a business assumption, and generate learning for future development.
Why MVPs matter
Building a full product before testing it with users is expensive and risky. Teams spend months implementing features based on assumptions that may be wrong. An MVP reduces this risk by putting a real product in front of real users as quickly as possible. The feedback from those users tells you whether your assumptions hold or whether you need to change direction.
The concept was popularized by Eric Ries in The Lean Startup, but the underlying principle is older: learn before you invest. Every successful product started by solving one problem well for a specific group of users, then expanding from there.
How to scope an MVP
Start with a clear hypothesis: “We believe [target users] will [desired behavior] because [reason].” Then identify the minimum set of features required to test that hypothesis. Write a focused PRD that explicitly states what is in scope and what is not. Every feature should map to the hypothesis. If it does not, cut it.
Resist the temptation to add “just one more thing.” Scope creep is the most common cause of MVP failure. The goal is not to build a lovable product on the first try. It is to learn whether you are solving a real problem. Polish and completeness come in subsequent iterations, informed by real user data.
Common mistakes
- Building too much and calling it an MVP. If it takes six months, it is not minimal.
- Building too little and shipping something unusable. An MVP must actually work.
- Not defining success metrics before launch, making it impossible to evaluate results.
- Treating the MVP as the final product instead of the first step in a learning cycle.
- Skipping the hypothesis and just building a smaller version of a full product.
Related terms
- Product-Market Fit
The validation milestone that an MVP is designed to test toward
- PRD
The document that defines what goes into the MVP and why
- User Persona
The target user profile that the MVP is built for
How Vantage helps
Vantage helps scope MVPs by connecting your hypothesis to real product data. Generate a PRD grounded in analytics and user feedback, then extract only the requirements that map to your core hypothesis. Generate prototype variants to validate the concept before writing code.