The document discusses the concept of the minimum viable product (MVP) and how it applies beyond software development. It provides definitions of MVP from experts as the smallest possible product that solves the core problem and demonstrates value with the least effort. The author emphasizes that an MVP should not be crappy, useless, or sloppy, and that the MVP process involves honestly assessing what is known and unknown to waste as little effort as possible in getting feedback from the right customers.
1. MVP
APPLYING THE CONCEPTS OF THE MINIMUM
VIABLE PRODUCT TO JUST ABOUT
ANYTHING
Monday, March 4, 13
2. WHAT IS MVP?
The minimum viable product is that version of a
new product which allows a team to collect the
maximum amount of validated learning about
customers with the least effort.
-- Eric Ries
Monday, March 4, 13
3. WHAT IS MVP?
MVP is the concise summary of the smallest
possible group of features that will work as a
stand-alone product while still solving at least the
“core “ problem and demonstrating the
product’s value.
-- Steve Blank & Bob Dorf
Monday, March 4, 13
4. WHAT IS MVP?
Take your product down to worthless and add
one feature back to it.
-- John Barnette
Monday, March 4, 13
5. WHAT IS MVP?
MVP development is being honest about what
we know and what we don’t know. This allows
us to waste as little effort as possible getting a
high quality product in front of the right
audience to find out if it’s what they actually
want*.
-- Me
*and are willing to pay for.
Monday, March 4, 13
10. WHAT ISN’T AN MVP
Crappy ≠ Minimum
Useless ≠ MVP
Sloppy ≠ Viable
Monday, March 4, 13
11. HOW DOES THIS APPLY?
The concept of MVP is absolutely applicable
outside of software development.
• What is my hypothesis?
• What are my constraints?
• Who do I think wants this?
Monday, March 4, 13
12. QUESTIONS?
Peter Bodenheimer
@pbodenheimer
peter@launchpadignition.com
Monday, March 4, 13