Transcript
Page 1: Quest for a minimum viable product - Eric Rogness

Quest for a minimum viable product

Page 2: Quest for a minimum viable product - Eric Rogness

What is a minimum viable product?

• …that version of a new product which allows a team to collect the maximum amount of

validated learning about customers with the least effort.

Page 3: Quest for a minimum viable product - Eric Rogness
Page 4: Quest for a minimum viable product - Eric Rogness

There are valid reasons not to build an MVP, which runs counter to lean startup principles.

Page 5: Quest for a minimum viable product - Eric Rogness

1. You are building a sustaining innovation product.

Page 6: Quest for a minimum viable product - Eric Rogness

Why?

• Your customers are smart. They understand the problem and solution and so are believable. The features they ask for likely represent their true needs.

• Competition is everywhere. You can see what’s working and what isn’t.

http://pandodaily.com/2013/02/04/three-reasons-not-to-build-a-minimum-viable-product/

Page 7: Quest for a minimum viable product - Eric Rogness

2. You don’t care if you’re wasteful.

Page 8: Quest for a minimum viable product - Eric Rogness

3. You achieve product-market fit.

Page 9: Quest for a minimum viable product - Eric Rogness

Points uncovered in discussion

• Waterfall development is always fraught with risk, no matter your resources. Lean product development helps you learn from the very start

• MVP: The donut has to at least be edible• Corporations may have less to gain from a public

beta. If they are developing a new product for their existing market, they can – Share early iterations privately with their customers– Get valuable feedback from real people– Clearly set expectations and avoid damaging brand

Page 10: Quest for a minimum viable product - Eric Rogness

Quest for a minimum viable product


Recommended