The Lean Startup: Difference between revisions
Content deleted Content added
No edit summary Tag: Manual revert |
No edit summary |
||
Line 36:
=== 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 ===
| |||