Your SlideShare is downloading. ×
0
Minimum Viable Product
Minimum Viable Product
Minimum Viable Product
Minimum Viable Product
Minimum Viable Product
Minimum Viable Product
Minimum Viable Product
Minimum Viable Product
Minimum Viable Product
Minimum Viable Product
Minimum Viable Product
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Minimum Viable Product

199,167

Published on

Published in: Business, Technology
2 Comments
239 Likes
Statistics
Notes
  • I hope one lesson learned was to check out the tremor in the camera man before posting. I got jittery just watching. (not to be mean- but constructive)
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Minimum Viable Product, MVP,
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
199,167
On Slideshare
0
From Embeds
0
Number of Embeds
149
Actions
Shares
0
Downloads
0
Comments
2
Likes
239
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Minimum Viable Product#leanstartup
    Eric Ries (@ericries)
    http://StartupLessonsLearned.blogspot.com
  • 2. Why do we build products?
    Delight customers
    Get lots of them signed up
    Make a lot of money
    Realize a big vision; change the world
  • 3. Possible Approaches
    “Maximize chances of success”
    build a great product with enough features that increase the odds that customers will want it
    Problem: no feedback until the end, might be too late to adjust
    “Release early, release often”
    Get as much feedback as possible, as soon as possible
    Problem: run around in circles, chasing what customers think they want
  • 4. Minimum Viable Product
    The minimum set of features needed to learn from earlyvangelists – visionary early adopters
    Avoid building products that nobody wants
    Maximize the learning per dollar spent
    Probably much more minimum than you think!
  • 5. Minimum Viable Product
    Visionary customers can “fill in the gaps” on missing features, if the product solves a real problem
    Allows us to achieve a big vision in small increments without going in circles
    Requires a commitment to iteration
  • 6. Minimize TOTAL time through the loop
    IDEAS
    LEARN
    BUILD
    DATA
    CODE
    MEASURE
  • 7. Examples
    Building IMVU in six months
    2004 “Kerry vs. Bush avatar debate”
    Lean Startup workshop
    VIP link in the header
  • 8. Product Development at Lean Startup
    Unit of Progress: Validated Learning About Customers ($$$)
    Customer Development
    Hypotheses,
    Experiments,
    Insights
    Problem: unknown
    Data,
    Feedback,
    Insights
    Solution: unknown
  • 9. Techniques
    Smoke testing with landing pages, AdWords
    SEM on five dollars a day
    In-product split testing
    Paper prototypes
    Customer discovery/validation
    Removing features (“cut and paste”)
  • 10. Fears
    False negative: “customers would have liked the full product, but the MVP sucks, so we abandoned the vision”
    Visionary complex: “but customers don’t know what they want!”
    Too busy to learn: “it would be faster to just build it right, all this measuring distracts from delighting customers”
  • 11. Thanks!
    • Startup Lessons Learned Blog
    • 12. http://StartupLessonsLearned.blogspot.com/
    • 13. Getting in touch (#leanstartup)
    • 14. http://twitter.com/ericries
    • 15. eric@theleanstartup.com
    • 16. The Lean Startup Workshop
    • 17. October 30, 2009 in San Francisco
    • 18. December 10, 2009 in New York
    • 19. http://training.oreilly.com/theleanstartup/

×