Minimum Viable Product (MVP)
Minimum Viable Product
The simplest version of a product that can be released to early users to test a core hypothesis, gather feedback, and validate demand before investing in full development.
In-Depth Explanation
A Minimum Viable Product is a version of a product with just enough features to be usable by early customers, who can then provide feedback for future development. The concept, popularised by Eric Ries in "The Lean Startup," focuses on validated learning with minimum effort.
MVP principles:
- Minimum: Build the smallest thing that tests your hypothesis
- Viable: It must work well enough to provide a real user experience
- Product: It must be a complete enough solution that users can evaluate it
What an MVP is NOT:
- A low-quality or broken product
- A prototype that does not work
- A feature list cut in half with no coherent user experience
- A proof of concept for internal use only
MVP approaches:
- Concierge MVP: Manually deliver the service to test demand before building technology
- Wizard of Oz MVP: Appear automated to the user but manually operated behind the scenes
- Landing page MVP: Test demand with a landing page before building the product
- Single-feature MVP: Build one core feature excellently rather than many features poorly
- Piecemeal MVP: Combine existing tools and services to deliver the value proposition
MVP development process:
- Identify assumptions: What do you need to be true for this to succeed?
- Choose the riskiest assumption: Which assumption, if wrong, would invalidate the idea?
- Design the test: What is the minimum product that tests this assumption?
- Build and release: Create the MVP and get it to users quickly
- Measure and learn: Track key metrics and gather user feedback
- Decide: Persevere (continue building), pivot (change direction), or stop
Common MVP mistakes:
- Building too much (not really "minimum")
- Building too little (not really "viable")
- Not having clear success criteria before launch
- Not measuring or listening to feedback
- Falling in love with the product instead of the problem
Business Context
MVPs reduce the risk of building products nobody wants by validating demand and approach before committing significant resources to full development.
How Clever Ops Uses This
Clever Ops frequently helps Australian businesses build MVPs to test business ideas quickly and affordably. We use rapid development approaches to create working products that test core hypotheses, enabling our clients to make data-driven decisions about where to invest.
Example Use Case
"A business tests a new service offering by manually delivering it to 10 customers (concierge MVP) before investing in building the automated platform, discovering that customers value a different aspect than originally assumed."