Entrepreneurship

Minimum Viable Products

What "minimum viable" actually means (a learning instrument, not a bad first draft) and how to scope a first version that ships in weeks and earns its keep.

  • Beginner
  • 15 min total
  • 12 chapters

What decision this helps you make: What goes in version one, what waits, and when "not yet good enough" is exactly good enough to ship.

What this topic is

A minimum viable product is the smallest thing you can put in customers' hands that delivers the core value AND generates real learning about whether to continue. Eric Ries's definition centers the learning, not the product.

Why it matters

The two ways young companies waste their lives are building too much before contact with customers, and shipping something so broken it tests nothing. MVP discipline is the narrow path between. It's why some teams learn in six weeks what others learn in eighteen months.

Who should learn it

Founders scoping version one, teams inside companies launching new offers, and anyone who has ever said "just one more feature before launch."

What you will understand

  • The MVP's real job: maximum learning per unit of effort
  • Cutting scope by the ONE core job, not by polishing everything a little
  • MVP shapes that aren't software (or aren't even products)
  • The quality line: what must be great, what may be absent

Prerequisites

Common misconception

"MVP means a low-quality version of the full product." Backwards on both ends: an MVP is NARROW, not shoddy. It does one job extremely well and simply doesn't do the other jobs at all. A buggy version of ten features tests nothing; a reliable version of one feature tests everything that matters.