MVP (Minimum Viable Product) — Explained with Examples

MVP (Minimum Viable Product) is the smallest possible version of a product that can be released to real users to test a core business hypothesis. Coined by Eric Ries in The Lean Startup, an MVP is not a half-finished product — it’s a vehicle for validated learning with minimal effort.

The goal of an MVP is to maximize learning about customers per unit of effort. It should have just enough features to attract early adopters and collect meaningful feedback. This contrasts with building a full-featured product first and hoping users come. An MVP might be a landing page, a clickable prototype, or a single-feature app. The data gathered informs whether to pivot (change strategy) or persevere (continue building).

Real-world analogy. Before building a full restaurant, a chef sets up a food truck with three menu items. If people line up for the tacos, she knows there’s demand and can invest in a permanent location. If nobody buys, she only wasted a food truck, not a full restaurant build-out.

Example (MVP for a task management app):

Full product idea: Teams, projects, labels, calendar, reports, chat
MVP:             → Single to-do list, add/complete/delete tasks
Hypothesis:      → Users need a faster way to track personal tasks
Success metric:  → 50% of users add a task within the first session

Related terms: Proof of Concept, Prototype, Agile, Lean, Spike

Related tutorial: MVP Design Guide