Minimum Viable Product (MVP)

What is a minimum viable product?

A minimum viable product is the smallest version of a product or feature that already gives real users some value and teaches you something at the same time. The point isn't to ship something half-finished. It's to answer an important question with as little effort as possible: Do people actually want this, and do they use it the way we think?

The term was popularized by Eric Ries in his 2011 book "The Lean Startup", where the MVP kicks off a cycle of building, measuring and learning.

Why an MVP matters

Plenty of teams spend months on features that hardly anyone ends up using. An MVP shortens the path to real feedback. You find out early whether an idea holds up, and you can put your budget where demand is proven. For SaaS teams, that means less feature bloat. For online stores, it means fewer expensive bets on products or tech that don't pay off.

How to use an MVP in practice

• Set a learning goal: Decide upfront which assumption you're testing and what success looks like.
• Cut ruthlessly: Drop everything that isn't needed to answer that one question.
• Start manually: Often you can run a process by hand at first, before automating it.
• Keep it usable: "Minimum" refers to scope, not to usability.

Common mistakes

A frequent mistake is an MVP without a clear learning goal, which ends up being a slightly smaller version of the original wish list. Another one: a hard-to-use MVP flops, and the team concludes the idea failed, when the real problem was the execution. For example, a SaaS team wants to build automated reports. As an MVP, it first sends a manually prepared weekly report to ten customers and watches whether they actually open and use it.