Building B2B Minimum Viable Products (MVP)

5,035 views
4,634 views

Published on

Slides from Lean Startup Israel meeting - Lessons learned from building MVP (min. viable product) for validating product roadmap and features in a B2B environment. by Oren Raboy

Published in: Technology
0 Comments
8 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
5,035
On SlideShare
0
From Embeds
0
Number of Embeds
251
Actions
Shares
0
Downloads
20
Comments
0
Likes
8
Embeds 0
No embeds

No notes for slide
  • deals with the following facts-of-life of a startup
  • …this is reality, so MVP says “build something to engage”
  • “product” is confusing a bit…can be many things.any thing that helps you learn more.Here are some tools that are known in the industry… We’ll share what use in a second.
  • fast into the marketlots of customers giving feedbackmany releases so we can iterate fast…
  • this is the process we follow:ppt used to validate problemwireframe validate solutionsoftware validate that we got it right.  this is the proof in the pudding.
  • Validate all 3-steps. Go up & go downexample from a different company: we had an idea, spent 2-3 weeks defining a solution; we weren’t ready to share with potential customers, because we wanted to “be ready”. when we met with customers we had a good architecture view and mock-ups of how we plan to solve the solution; 10-min into the meeting it was clear that the problem we were trying to solve wasn’t real. after a few of these we had good ideas on other things we could do… but we ran out of steam and never followed through…… at @totango, guy&omer were much more diligent in their vision validation process. they spent time going back to their initial industry contacts until they felt they had found a good ‘hole to dig in’ . avoid the urge to dive-deep / “develop-code”; spend time validating visions.
  • Email example: got good signalsstarted implementing a “minimal version”… spent lots of time on a email system (scheduling, templating)nobody used it… because we didn’t get the content of the report rightswitch to manual sending… now getting traction.Lesson: wasted time… wasted effort (need to redo entire report system)it’s like code… u need to designfirst, address your bigger riskssame example: give email example where we rushed to implement the mechanism… no one used, the info. wasn’t interesting… spent a lot of time on this. … ended by creating manual reports … quick iterations and now we know… and need to redesign the email engine.
  • most important part of the design, figure out what you want to measure in advance….Qualitive vs. Quantativewhat do I want him to say: “agree to beta; connect us with someone [CEO->VP Sales]Quantative: metrics: are people using? we released a few times with out the right instrumentation in place, was really hard to tell if the mvp was effective or not.
  • we just found this to be true; when you implement MVP you are doing a lot of “selling”. you need to invest in that; a ppt needs to look nice mockups need to “look real” working code needs to have a polished interfacewithout it, you can’t get your audience’s attention for quality feedback;
  • the goal is to learn as fast as you can…not just about the beginning, at any point in your product you can do an MVPMVP are effective when you think them through, not just hack them out… Thinking means: What are we trying to validate, how will we know (measure)
  • Building B2B Minimum Viable Products (MVP)

    1. MVP<br />@orenraboy<br />www.totango.com<br />
    2. Minimum<br />Viable <br />Product<br />@orenraboy<br />www.totango.com<br />
    3. 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 />
    4. Maximum Learning<br />Minimum<br />Cost<br />
    5. Presentation<br />Post<br />Landing Page<br />Mockup<br />Demo<br />Working Code<br />
    6. Not as Simple as it Sounds!<br />1. Deciding what to validate<br />2. Overestimating minimal<br />
    7. 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 />
    8. Solution<br />Value<br />Problem<br />
    9. Lesson I <br />MVP is a process <br />
    10. Lesson II<br />Focus on what you <br />want to validate<br />
    11. Lesson III <br />Measure!<br />
    12. Lesson IV <br />MVP is no excuse for poor design<br />
    13. 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 />
    14. Thanks<br />@orenraboy<br />www.totango.com<br />

    ×