MVP<br />@orenraboy<br />www.totango.com<br />

Minimum<br />Viable <br />Product<br />@orenraboy<br
/>www.totango.com<br />

You don’t know what you
need to build<br />1<br />Only customers can teach you<br />2<br />Find out before running out of cash<br />3<br />@orenraboy<br />www.totango.com<br />

Maximum Learning<br />Minimum<br />Cost<br />

Presentation<br />Post<br />Landing Page<br />Mockup<br
/>Demo<br />Working Code<br />

Not as Simple as it
Sounds!<br />1. Deciding what to validate<br />2. Overestimating minimal<br />

in MVP-Land:<br />1<br />Month to
first working version<br />20<br />Early feedback customers<br />2<br />Releases a week<br />What have we learned?<br />

Solution<br />Value<br />Problem<br />

Lesson I <br />MVP is
a process <br />

Lesson II<br />Focus on what
you <br />want to validate<br />

Lesson III <br />Measure!<br />

Lesson IV <br />MVP is
no excuse for poor design<br />

RECAP<br />Learn fast, learn often<br
/>It’s harder than it looks, but gets easier with practice<br />it’s a process not a milestone<br />MVP isn’t a hack – Design It:<br />What do you want to validate?<br /> How will you measure it?<br />

Thanks<br />@orenraboy<br />www.totango.com<br />