Minimum Viable Product (MVP)
Synonyms: MVP, Earliest Testable Product, minimum feature set, v0, MLP
Definition
Use cases
- The 40-feature MVP: Scope grows every standup. 6 months later, there’s no launch and no user data.
- Minimum without viable: Checkout ships with no error states. Users bail at payment and the team calls it low demand. The idea never got a fair test.
- “Do I need to code my MVP?”: A classic Reddit question. Teams build a full app to test demand that a landing page could check in a week.
How it's used in practice
- Write the bet first: “We believe [user] will [action] because [reason].” No sentence, no build.
- Cut scope in half, twice: This is Eric Ries’s own advice.
- Pick the cheapest test: A landing page, concierge (you do it by hand), Wizard of Oz (fake automation), a clickable prototype, or live code.
- Polish one core flow: The main path gets error states, loading states, and clear copy.
Challenges & limitations
- Nobody agrees on “minimum”: PMs, designers, and engineers draw the line in different places.
- The hack becomes permanent: Users like the quick version, nobody budgets a rebuild, and design debt piles up.
Free resources
- NN/g: MVP, Why It Isn’t Always Release 1 — Short video on running an MVP as a simple experiment
- Building the Minimum Viable Product (Stanford eCorner) — Eric Ries talk clip where the “cut it in half” advice comes from
- How to Design a Lean UX MVP (Toptal) — Think, Make, Check applied to MVP design work
