The Lean Startup: Difference between revisions
No edit summary Tag: Manual revert |
No edit summary |
||
| Line 36: | Line 36: | ||
=== I – Vision === |
=== I – Vision === |
||
🚀 '''1 – Start.''' Picture a startup team sitting in a conference room arguing about process while a veteran manager insists “process kills creativity”; the Lean Startup reframes both views by treating entrepreneurship as disciplined management under uncertainty. It explains why traditional planning and forecasting—built for environments with long, stable operating histories—routinely fail in startups, where neither stability nor history exists. It roots its approach in lean manufacturing (Ohno, Shingo) and adapts small batches, just-in-time, and the elimination of waste to new-product development, with validated learning as the unit of progress. The method centers on the Build–Measure–Learn loop: turn ideas into products, measure customer behavior with actionable metrics, and decide whether to pivot or persevere. Innovation accounting replaces vanity metrics so teams can see real progress and be held accountable. This perspective insists that speed and quality are allies when speed shortens learning—not excuses for chaos. It also warns against treating startups like rocket launches; instead, steer continuously like a driver with a hand on the wheel. The result is a managerial discipline for creating value faster and with less waste. ''Entrepreneurship is management.'' |
|||
🚀 '''1 – Start.''' |
|||
🧭 '''2 – Define.''' At a talk, a Fortune-500 division lead named Mark describes having “kindling, wood, paper, flint, even some sparks,” yet no fire—a metaphor for internal innovation that has structure but lacks a process for turning vision into results. Mark exemplifies the chapter’s point: entrepreneurs are everywhere, including intrapreneurs who form autonomous teams, navigate corporate politics, and still need a way to make breakthroughs systematic. The chapter defines a startup as “a human institution designed to create a new product or service under conditions of extreme uncertainty,” decoupling entrepreneurship from company size or sector. It shows how senior leaders can cultivate entrepreneurship—Intuit’s years-long shift under Scott Cook and Brad Smith made SnapTax possible by pairing autonomy with a new management paradigm. The lesson is that structure alone (skunkworks, separate P&Ls) is not enough; teams need a scientific method for discovery and accountability to learning milestones. Lean Startup practices give intrapreneurs the same tools as garage founders: rapid experiments, clear hypotheses, and measurable learning. In this view, entrepreneurship is a job title inside any organization that depends on innovation. Whether in government, nonprofit, or enterprise, the same uncertainty and the same discipline apply. ''A startup is a human institution designed to create a new product or service under conditions of extreme uncertainty.'' |
|||
🧭 '''2 – Define.''' |
|||
📚 '''3 – Learn.''' IMVU’s founders shipped a crash-prone, feature-light prototype, charged from day one, and learned from real usage rather than “success theater”—stunts that juice vanity metrics without moving fundamentals. The company resisted the temptation to buy PR or a Super Bowl ad, investing instead in experiments that could demonstrate whether product work was leading toward massive success. Over time, those experiments yielded a repeatable way to measure progress and cut waste; years later, “sixty million avatars” stood as proof that learning, not luck, powered the outcome. The chapter generalizes that lesson: see every startup as a grand experiment and ask not “Can this product be built?” but “Should it be built?” and “Can we build a sustainable business around it?” That requires breaking plans into testable pieces and running empirical tests rather than debating opinions. Actionable metrics and innovation accounting separate real signal from vanity noise so teams can learn when to pivot or persevere. Validated learning becomes the unit of progress for product, features, and campaigns. In short, scientific learning—not theatrics—guides decisions under uncertainty. ''In the Lean Startup model, every product, every feature, every marketing campaign—everything a startup does—is understood to be an experiment designed to achieve validated learning.'' |
|||
📚 '''3 – Learn.''' |
|||
🧪 '''4 – Experiment.''' To escape the “just do it” trap—shipping and merely “seeing what happens”—teams design true experiments: explicit hypotheses, empirical tests, and clear pass/fail criteria. Zappos began by testing whether customers would buy shoes online without first owning warehouses: founder Nick Swinmurn photographed local inventory, posted it on the web, and fulfilled purchases by hand before scaling—a minimum viable product that prioritized learning over polish. Dropbox validated demand before building complex sync tech by posting a short demo video seeded with Easter eggs for the Digg community, which triggered more than 10,000 Diggs in 24 hours. These stories illustrate a rule of thumb: remove any feature, process, or effort that doesn’t directly contribute to the learning you seek. Legal, branding, and competitive fears are acknowledged—but weighed against the far greater risk of not learning fast enough. Proper experiments also protect teams from arguing over opinions and enable rapid iteration, especially when measured with actionable metrics. The scientific method replaces alchemy: think big, start small, and let data guide the next bet. ''If you cannot fail, you cannot learn.'' |
|||
🧪 '''4 – Experiment.''' |
|||
=== II – Steer === |
=== II – Steer === |
||
Revision as of 10:05, 11 November 2025
"Innovation accounting enables startups to prove objectively that they are learning how to grow a sustainable business."
— Eric Ries, The Lean Startup (2011)
Introduction
| The Lean Startup | |
|---|---|
 | |
| Full title | The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses |
| Author | Eric Ries |
| Language | English |
| Subject | Entrepreneurship; Startups; Innovation management |
| Genre | Nonfiction; Business |
| Publisher | Crown Business |
Publication date | 13 September 2011 |
| Publication place | United States |
| Media type | Print (hardcover); e-book; audiobook |
| Pages | 336 |
| ISBN | 978-0-307-88789-4 |
| Goodreads rating | 4.1/5 (as of 10 November 2025) |
| Website | theleanstartup.com |
📘 The Lean Startup is a 2011 business book by entrepreneur Eric Ries that sets out a management system for building new ventures under conditions of extreme uncertainty; the first U.S. edition was published by Crown Business on 13 September 2011.[1] It popularizes the build–measure–learn feedback loop and concepts such as the minimum viable product (MVP), “validated learning,” pivots, and the use of actionable (rather than vanity) metrics to gauge real progress.[1] Organized into three parts—Vision, Steer, and Accelerate—the book develops its ideas through case-led chapters and devices like “innovation accounting.”[2][1] Ries writes in an instructive, managerial register, pressing a “scientific” approach to entrepreneurship grounded in hypothesis-driven experiments and rapid iteration.[3] Since publication the book has sold over one million copies in more than thirty languages and debuted at No. 2 on the New York Times Advice best-seller list in September 2011.[4][5]
Chapter summary
This outline follows the Crown Business hardcover first edition (2011, ISBN 978-0-307-88789-4).[6] Bibliographic details (publication date and total pages) are also reflected in the publisher’s catalogue.[1]
I – Vision
🚀 1 – Start. Picture a startup team sitting in a conference room arguing about process while a veteran manager insists “process kills creativity”; the Lean Startup reframes both views by treating entrepreneurship as disciplined management under uncertainty. It explains why traditional planning and forecasting—built for environments with long, stable operating histories—routinely fail in startups, where neither stability nor history exists. It roots its approach in lean manufacturing (Ohno, Shingo) and adapts small batches, just-in-time, and the elimination of waste to new-product development, with validated learning as the unit of progress. The method centers on the Build–Measure–Learn loop: turn ideas into products, measure customer behavior with actionable metrics, and decide whether to pivot or persevere. Innovation accounting replaces vanity metrics so teams can see real progress and be held accountable. This perspective insists that speed and quality are allies when speed shortens learning—not excuses for chaos. It also warns against treating startups like rocket launches; instead, steer continuously like a driver with a hand on the wheel. The result is a managerial discipline for creating value faster and with less waste. Entrepreneurship is management.
🧭 2 – Define. At a talk, a Fortune-500 division lead named Mark describes having “kindling, wood, paper, flint, even some sparks,” yet no fire—a metaphor for internal innovation that has structure but lacks a process for turning vision into results. Mark exemplifies the chapter’s point: entrepreneurs are everywhere, including intrapreneurs who form autonomous teams, navigate corporate politics, and still need a way to make breakthroughs systematic. The chapter defines a startup as “a human institution designed to create a new product or service under conditions of extreme uncertainty,” decoupling entrepreneurship from company size or sector. It shows how senior leaders can cultivate entrepreneurship—Intuit’s years-long shift under Scott Cook and Brad Smith made SnapTax possible by pairing autonomy with a new management paradigm. The lesson is that structure alone (skunkworks, separate P&Ls) is not enough; teams need a scientific method for discovery and accountability to learning milestones. Lean Startup practices give intrapreneurs the same tools as garage founders: rapid experiments, clear hypotheses, and measurable learning. In this view, entrepreneurship is a job title inside any organization that depends on innovation. Whether in government, nonprofit, or enterprise, the same uncertainty and the same discipline apply. A startup is a human institution designed to create a new product or service under conditions of extreme uncertainty.
📚 3 – Learn. IMVU’s founders shipped a crash-prone, feature-light prototype, charged from day one, and learned from real usage rather than “success theater”—stunts that juice vanity metrics without moving fundamentals. The company resisted the temptation to buy PR or a Super Bowl ad, investing instead in experiments that could demonstrate whether product work was leading toward massive success. Over time, those experiments yielded a repeatable way to measure progress and cut waste; years later, “sixty million avatars” stood as proof that learning, not luck, powered the outcome. The chapter generalizes that lesson: see every startup as a grand experiment and ask not “Can this product be built?” but “Should it be built?” and “Can we build a sustainable business around it?” That requires breaking plans into testable pieces and running empirical tests rather than debating opinions. Actionable metrics and innovation accounting separate real signal from vanity noise so teams can learn when to pivot or persevere. Validated learning becomes the unit of progress for product, features, and campaigns. In short, scientific learning—not theatrics—guides decisions under uncertainty. In the Lean Startup model, every product, every feature, every marketing campaign—everything a startup does—is understood to be an experiment designed to achieve validated learning.
🧪 4 – Experiment. To escape the “just do it” trap—shipping and merely “seeing what happens”—teams design true experiments: explicit hypotheses, empirical tests, and clear pass/fail criteria. Zappos began by testing whether customers would buy shoes online without first owning warehouses: founder Nick Swinmurn photographed local inventory, posted it on the web, and fulfilled purchases by hand before scaling—a minimum viable product that prioritized learning over polish. Dropbox validated demand before building complex sync tech by posting a short demo video seeded with Easter eggs for the Digg community, which triggered more than 10,000 Diggs in 24 hours. These stories illustrate a rule of thumb: remove any feature, process, or effort that doesn’t directly contribute to the learning you seek. Legal, branding, and competitive fears are acknowledged—but weighed against the far greater risk of not learning fast enough. Proper experiments also protect teams from arguing over opinions and enable rapid iteration, especially when measured with actionable metrics. The scientific method replaces alchemy: think big, start small, and let data guide the next bet. If you cannot fail, you cannot learn.
II – Steer
🦘 5 – Leap.
🧫 6 – Test.
📏 7 – Measure.
🔄 8 – Pivot (or Persevere).
III – Accelerate
📦 9 – Batch.
🌱 10 – Grow.
🦎 11 – Adapt.
💡 12 – Innovate.
♻️ 13 – Epilogue: Waste Not.
🤝 14 – Join the Movement.
Background & reception
🖋️ Author & writing. Ries came to the book as a programmer-turned-entrepreneur: he co-founded IMVU and served as its CTO, wrote the “Startup Lessons Learned” blog, and later worked as an entrepreneur-in-residence at Harvard Business School; these experiences inform the book’s case-led voice and emphasis on “validated learning.”[1] He has described how early failures taught him to avoid “vanity metrics” and to ground product decisions in experiments and customer behavior—themes that run throughout the narrative.[5] The conceptual backbone merges ideas from lean manufacturing and customer development with agile practices, presented as a disciplined, test-and-learn mode of management.[3] Structurally the book is divided into three parts—Vision, Steer, and Accelerate—which frame short chapters and tools like innovation accounting and the build–measure–learn loop.[2][1]
📈 Commercial reception. According to its UK publisher, the book has sold over one million copies worldwide and has been translated into more than thirty languages.[4] Upon release it entered the New York Times Advice best-seller list at No. 2 in September 2011, reflecting strong early demand.[5]
👍 Praise. The Financial Times (Philip Delves Broughton, 18 September 2011) praised the book’s blend of practitioner insight and theory, arguing it had “the chops” to join the canon of influential business books.[7] Harvard Business Review framed the approach as a major shift in how new ventures should be launched, highlighting MVPs, pivoting, and experimentation as core strengths.[3] A feature in Wired lauded the method’s “inexorable logic,” commending its demand for real-world testing and actionable metrics over intuition or hype.[5]
👎 Criticism. Some technologists and investors quoted in Wired argued that the philosophy can trade vision for “plodding validation,” with critics like David Heinemeier Hansson and Ben Horowitz questioning its fit for all contexts.[5] In Harvard Business Review, Scott D. Anthony cautioned that MVPs are easily misapplied, warning against letting “the minimal” eclipse “the viable.”[8] Later, Ethan Mollick noted that while the method improves learning, it can over-index on early customer input for novel technologies and needs complementing with other tools.[9] At the enterprise level, MIT Sloan Management Review reported that large companies often struggle to scale lean practices beyond isolated projects without broader cultural change.[10]
🌍 Impact & adoption. General Electric’s FastWorks program applied Lean Startup principles to speed up development cycles and decision-making, illustrating diffusion into heavy industry.[11] Universities incorporated the approach into curricula—Harvard Business School, for example, integrated the ideas into entrepreneurship teaching soon after publication.[5] Public-sector uptake followed: MIT Sloan highlights the U.S. National Science Foundation’s I-Corps program, which uses Lean LaunchPad/Lean Startup methods to commercialize academic research, and Wired reported early experiments in municipal government via Code for America.[10][5]
Related content & more
YouTube videos
CapSach articles
References
- ↑ 1.0 1.1 1.2 1.3 1.4 1.5 "The Lean Startup by Eric Ries: 9780307887894". PenguinRandomHouse.com. Penguin Random House. 13 September 2011. Retrieved 10 November 2025.
- ↑ 2.0 2.1 "The lean startup — Table of Contents". TUKLAS (UP University Library). University of the Philippines. Retrieved 10 November 2025.
- ↑ 3.0 3.1 3.2 Blank, Steve (May 2013). "Why the Lean Start-Up Changes Everything". Harvard Business Review. Harvard Business Publishing. Retrieved 10 November 2025.
- ↑ 4.0 4.1 "The Lean Startup". Penguin Books UK. Penguin Random House. 6 October 2011. Retrieved 10 November 2025.
- ↑ 5.0 5.1 5.2 5.3 5.4 5.5 5.6 Greenwald, Ted (18 June 2012). "In Silicon Valley, Eric Ries has the stage -- and the crowd is going wild". Wired. Retrieved 10 November 2025.
- ↑ "The lean startup : how today's entrepreneurs use continuous innovation to create radically successful business". WorldCat.org. OCLC. Retrieved 10 November 2025.
- ↑ Broughton, Philip Delves (18 September 2011). "Book review: The Lean Startup". Financial Times. Retrieved 10 November 2025.
- ↑ Anthony, Scott D. (9 April 2012). "The Dangers of the Minimal Viable Product". Harvard Business Review. Harvard Business Publishing. Retrieved 10 November 2025.
- ↑ Mollick, Ethan (21 October 2019). "What the Lean Startup Method Gets Right and Wrong". Harvard Business Review. Harvard Business Publishing. Retrieved 10 November 2025.
- ↑ 10.0 10.1 "Why Large Companies Struggle With Lean". MIT Sloan Management Review. Massachusetts Institute of Technology. 27 November 2019. Retrieved 10 November 2025.
- ↑ "How GE Applies Lean Startup Practices". Harvard Business Review. Harvard Business Publishing. 23 April 2014. Retrieved 10 November 2025.