What is a minimum viable product (MVP)?

Minimum viable product (MVP), explained

Eric Ries, who popularized the term through the Lean Startup movement, defined the MVP in 2009 as that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. In the same post he adds a caveat that's often forgotten: the MVP, despite the name, is not about creating minimal products.

The key word is learning. An MVP exists to test your riskiest assumption: that people have this problem, that they'll use this solution, that they'll pay. Sometimes the right MVP is a working product. Sometimes it's a landing page with a waitlist, a manual service behind a simple form, or a demo video. Whatever teaches you the most for the least effort.

In launch culture, "MVP" has come to mean "the first version we launch". That's fine, as long as it's still framed as an experiment. Decide what you expect to learn before you launch it: activation rate, retention after a few weeks, conversion to paid, the kind of feedback you get. Then launch to the right audience, not just anyone.

The common failure is the opposite of minimal: months of building features nobody asked for before a single user sees it. The other failure is launching something so broken or unclear that it teaches nothing, because people leave before they reach the core value.

A good MVP launch pairs well with honest positioning. Say it's early. Invite feedback. Users forgive rough edges when they're told the truth and see you respond quickly.

Why it matters for founders

An MVP keeps you from spending months on the wrong product. Framed as a learning experiment, even a small launch gives you evidence to decide what to build next.

Example

Before building an integration-heavy product, a founder launches a landing page and runs the service manually for ten customers. Eight keep paying after a month, which justifies building the automation.

Common mistakes

• Building for months before any user sees the product.
• Launching without deciding what you want to learn.
• Shipping something so broken that users never reach the core value.