Your SlideShare is downloading. ×
  • Like
  • Save
Lean Startup for Geeks with Eric Ries
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Lean Startup for Geeks with Eric Ries



Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • Truth: The Lean Startup method is not about cost, it is about speed. Lean Startups waste less money, because they use a disciplined approach to testing new products and ideas. Lean, when used in the context of lean startup, refers to a process of building companies and products using lean manufacturing principles applied to innovation. That process involves rapid hypothesis testing, validated learning about customers, and a disciplined approach to product development.
  • Truth: The Lean Startup methodology applies to all companies that face uncertainty about what customers will want. This is true regardless of industry or even scale of company: many large companies depend on their ability to create disruptive innovation. Those general managers are entrepreneurs, too. And they can benefit from the speed and discipline of starting with a minimum viable product and then learning and iterating continuously.
  • Truth: There’s nothing wrong with raising venture capital. Many lean startups are ambitious and are able to deploy large amounts of capital. What differentiates them is their disciplined approach to determining when to spend money: after the fundamental elements of the business model have been empirically validated. Because lean startups focus on validating their riskiest assumptions first, they sometimes charge money for their product from day one – but not always.
  • Truth: Lean Startups are driven by a compelling vision, and they are rigorous about testing each element of this vision against reality. They use customer development, split-testing, and actionable analytics as vehicles for learning about how to make their vision successful. But they do not blindly do what customers tell them, nor do they mechanically attempt to optimize numbers. Along the way, they pivot away from the elements of the vision that are delusional and double-down on the elements that show promise.
  • I’m not leaving you, I’m pivoting to another man
  • Conference structure


  • 1. hosted by
    The Lean Startup & Continuous Deployment#leanstartup
    “Innovation through experimentation”
    Eric Ries (@ericries)
  • 3.
  • 4. Myth #1
    Lean means cheap. Lean startups try to spend as little money as possible.
    Truth The Lean Startup method is not about cost, it is about speed.
  • 5. Myth #2
    The Lean Startup is only for Web 2.0/internet/consumer software companies.
    Truth The Lean Startup applies to all companies that face uncertainty about what customers will want.
  • 6. Myth #3
    Lean Startups are small bootstrapped startups.
    Truth Lean Startups are ambitious and are able
    to deploy large amounts of capital.
  • 7. Myth #4
    Lean Startups replace vision with dataor customer feedback.
    Truth Lean Startups are driven by a compelling vision, and are rigorous about testing each element of this vision
  • 8. Most Startups Fail
  • 9. Most Startups Fail
  • 10. Most Startups Fail
  • 11. What is a startup?
    • A startup is a human institution designed to deliver a new product or service under conditions of extreme uncertainty.
    • 12. Nothing to do with size of company, sector of the economy, or industry
  • What is a startup?
  • 13. Entrepreneurship is management
    • Our goal is to create an institution, not just a product
    • 14. Traditional management practices fail
    - “general management” as taught to MBAs
    • Need practices and principles geared to the startup context of extreme uncertainty
    • 15. Not just for “two guys in a garage”
  • The Pivot
  • 16. I’
  • 17. The Pivot
    • What do successful startups have in common?
    • 18. They started out as digital cash for PDAs, but evolved into online payments for eBay.
    • 19. They started building BASIC interpreters, but evolved into the world's largest operating systems monopoly.
    • 20. They were shocked to discover their online games company was actually a photo-sharing site.
    • 21. Pivot: change directions but stay grounded in what we’ve learned.
  • Speed Wins
    If we can reduce the time between pivots
    We can increase our odds of success
    Before we run out of money
  • 22. Making Progress
    • In a lean transformation, question #1 is – which activities are value-creating and which are waste?
    • 23. In traditional business, value is created by delivering products or services to customers
    • 24. In a startup, the product and customer are unknowns. We need a new definition of value for startups: validated learning
  • Traditional Product DevelopmentUnit of Progress: Advance to Next Stage
    Problem: known
  • 25. Agile Product DevelopmentUnit of Progress: A line of Working Code
    “Product Owner” or in-house customer
    Problem: known
  • 26. Lean StartupUnit of Progress: Validated Learning ($$$)
    Customer Development
    Hypotheses, Experiments,
    Data, Feedback,
    Agile Development
  • 27. Minimize TOTAL time through the loop
  • 28. Continuous Deployment
    Learn Faster
    Customer Development
    Five Whys
    Build Faster
    Continuous Deployment
    Small Batches
    Minimum Viable Product
    Measure Faster
    Split Testing
    Actionable Metrics
    Net Promoter Score
  • 29. Continuous Deployment Principles
    Have every problem once
    Stop the line when anything fails
    Fast response over prevention
  • 30. Continuous Deployment
    • Deploy new software quickly
    • 31. At IMVU time from check-in to production = 20 minutes
    • 32. Tell a good change from a bad change (quickly)
    • 33. Revert a bad change quickly
    • 34. And “shut down the line”
    • 35. Work in small batches
    • 36. At IMVU, a large batch = 3 days worth of work
    • 37. Break large projects down into small batches
  • Cluster Immune SystemWhat it looks like to ship one piece of code to production:
    • Run tests locally (SimpleTest, Selenium)
    • 38. Everyone has a complete sandbox
    • 39. Continuous Integration Server (BuildBot)
    • 40. All tests must pass or “shut down the line”
    • 41. Automatic feedback if the team is going too fast
    • 42. Incremental deploy
    • 43. Monitor cluster and business metrics in real-time
    • 44. Reject changes that move metrics out-of-bounds
    • 45. Alerting & Predictive monitoring (Nagios)
    • 46. Monitor all metrics that stakeholders care about
    • 47. If any metric goes out-of-bounds, wake somebody up
    • 48. Use historical trends to predict acceptable bounds
    • 49. When customers see a failure
    • 50. Fix the problem for customers
    • 51. Improve your defenses at each level
  • Continuous Deployment
  • 52. There’s much more…
    Build Faster
    Unit Tests
    Usability Tests
    Continuous Integration
    Incremental Deployment
    Free & Open-Source
    Cloud Computing
    Cluster Immune System
    Just-in-time Scalability
    Developer Sandbox
    Minimum Viable Product
    Learn Faster
    Split Tests
    Customer Development
    Five Whys
    Customer Advisory Board
    Falsifiable Hypotheses
    Product Owner
    Customer Archetypes
    Cross-functional Teams
    Semi-autonomous Teams
    Smoke Tests
    Measure Faster
    Funnel Analysis
    Cohort Analysis
    Net Promoter Score
    Search Engine Marketing
    Predictive Monitoring
    Measure Faster
    Split Tests
    Continuous Deployment
    Usability Tests
    Real-time Monitoring & Alerting
    Customer Liaison
  • 54. Thanks!
    • Startup Lessons Learned Blog
    • 55.
    • 56. Getting in touch (#leanstartup)
    • 57.
    • 58.
    • 59. Additional resources
    • 60. Lean Startup Wiki
    • 61. Lean Startup Circle