Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The Lean Startup

The Lean Startup

Talk about The Lean Startup book by Eric Ries presented at Agile Warsaw meeting.

Robert Wijas

October 24, 2011
Tweet

More Decks by Robert Wijas

Other Decks in Technology

Transcript

  1. THE LEAN STARTUP

  2. None
  3. From PRWeb

  4. FIVE PRINCIPLES

  5. FIVE PRINCIPLES 1 ENTREPRENEURS ARE EVERYWHERE

  6. FIVE PRINCIPLES 2 ENTREPRENEURSHIP IS MANAGEMENT

  7. FIVE PRINCIPLES 3 VALIDATED LEARNING

  8. FIVE PRINCIPLES 4 BUILD-MESAURE-LEARN

  9. FIVE PRINCIPLES 5 INNOVATION ACCOUNTING

  10. STARTUP

  11. STARTUP A startup is a human institution designed to create

    a new product or service under conditions of extreme uncertainty.
  12. WEB 2.0

  13. WASTE 2.0

  14. ACHIEVING FAILURE On Time? On Budget? With High Quality? With

    Beautiful Design?
  15. SCIENCE EXPERIMENT

  16. Vision Product Strategy

  17. Ideas Build Product Measure Data Learn

  18. Ideas Build Product Measure Data Learn

  19. LEAP OF FAITH VALUE GROWTH

  20. MVP MINIMUM VIABLE PRODUCT Concierge MVP

  21. ENGINES OF GROWTH New customers come from the actions of

    past customers.
  22. • Sticky • Viral • Paid ENGINES OF GROWTH

  23. MEASURE Innovation Accounting

  24. 3 STEPS Establish the baseline Tune the engine Pivot or

    persevere
  25. WARNING Vanity Metrics

  26. THREE A’S Actionable - clear cause and effect Accessible -

    simple, everyone can understand them Auditable - credible to employees
  27. PIVOT OR PERSEVERE

  28. PIVOT Vision Strategy

  29. CATALOG OF PIVOTS • Zoom-in • Zoom-out • Customer Segment

    • Customer Need • Platform • Business Architecture • Value Capture • Engine Growth • Channel • Technology
  30. A STARTUP’S RUNWAY IS THE NUMBER OF PIVOTS IT CAN

    STILL MAKE
  31. A STARTUP’S RUNWAY IS THE NUMBER OF PIVOTS IT CAN

    STILL MAKE
  32. PIVOT IS NOT A FAILURE

  33. ADAPTIVE ORGANIZATION

  34. New release disabled a feature for customers. Because a particular

    server failed. Because an obscure subsystem was used in the wrong way. The engineer who used it didn’t know how to use is properly. Because he was never trained. Because his manager doesn’t believe in training new engineers because his team is “too busy”. WHY? WHY? WHY? WHY? WHY?
  35. GETTING STARTED 1. Be tolerant of all mistakes the first

    time. 2. Never allow the same mistake twice.
  36. KANBAN

  37. Leadership in todays economy means creating platform for experimentation for

    your teams.
  38. Ideas Build Product Measure Data Learn

  39. TOOLS & TECHNIQUES

  40. BUILD CODE FASTER • Unit tests • Usability Tests •

    Continuous Integration • Incremental Deployment • Free & Open-Source Components • Cloud Computing • Cluster Immune System • Just-in-time Scalability • Refactoring • Developer Sandbox
  41. MEASURE FASTER • Split tests • Clear Product Owner •

    Continuous Deployment • Usability Tests • Real-time Monitoring • Funnel Analysis • Cohort Analysis • Net Promoter Score • Search Engine Marketing • Real-Time Alerting • Predictive Monitoring
  42. LEARN FASTER • Split tests • Customer Interviews • Customer

    Development • Five Whys Root Cause Analysis • Customer Advisory Board • Falsifiable Hypotheses • Product Owner Accountability • Customer Archetypes • Cross-functional Teams • Smoke Tests
  43. NOW LETS GO AND CHANGE THE WORLD

  44. RESOURCES • http://www.startuplessonslearned.com/ • http://theleanstartup.com/ • The Lean Startup Wiki

    ! • RailsConf 2011: Eric Ries, "Lessons Learned" • [email protected]: Eric Ries "The Lean Startup" • - Startups - Eric Ries of Lean Startup - TWiST #199