The Lean Startup: Difference between revisions
Content deleted Content added
No edit summary Tag: Reverted |
No edit summary |
||
| (11 intermediate revisions by the same user not shown) | |||
Line 3:
}}
{{Section separator}}
== Introduction ==
Line 24 ⟶ 25:
}}
📘 '''''{{Tooltip|The Lean Startup}}''''' is a 2011 business book by entrepreneur {{Tooltip|Eric Ries}} that sets out a management system for building new ventures under conditions of extreme uncertainty
It popularizes the {{Tooltip|build–measure–learn
Organized into three parts—Vision, Steer, and Accelerate—the book develops its ideas through case-led chapters and devices
Ries writes in an instructive, managerial register,
Since publication, the book has sold
{{Section separator}}
== Chapter summary ==▼
== Part I – Vision ==
''This outline follows the Crown Business hardcover first edition (2011, ISBN 978-0-307-88789-4).''<ref name="OCLC876623825">{{cite web |title=The lean startup : how today's entrepreneurs use continuous innovation to create radically successful business |url=https://search.worldcat.org/title/The-lean-startup-%3A-how-today%27s-entrepreneurs-use-continuous-innovation-to-create-radically-successful-business/oclc/876623825 |website=WorldCat.org |publisher=OCLC |access-date=10 November 2025}}</ref>▼
''Bibliographic details (publication date and total pages) are also reflected in the publisher’s catalogue.''<ref name="PRH2011">{{cite web |title=The Lean Startup by Eric Ries: 9780307887894 |url=https://www.penguinrandomhouse.com/books/210088/the-lean-startup-by-eric-ries/ |website=PenguinRandomHouse.com |publisher=Penguin Random House |date=13 September 2011 |access-date=10 November 2025}}</ref>▼
===
🚀 Picture a startup team in a conference room arguing about process while a veteran manager insists “process kills creativity.” Lean Startup reframes both views: entrepreneurship is disciplined management under uncertainty. Traditional planning and forecasting—built for long, stable operating histories—routinely fail where neither stability nor history exists. The approach draws on {{Tooltip|Lean manufacturing}} ({{Tooltip|Ohno}}, {{Tooltip|Shingo}}), adapting small batches, just-in-time, and waste elimination to new-product development, with {{Tooltip|Validated learning}} as the unit of progress. The method centers on the {{Tooltip|build–measure–learn loop}}: turn ideas into products, measure customer behavior with actionable metrics, and decide whether to pivot or persevere. {{Tooltip|Innovation accounting}} replaces vanity metrics so teams can see real progress and be accountable. Speed and quality become allies when faster cycles shorten learning rather than excuse chaos. Treat startups less like rocket launches and more like continuous steering with a hand on the wheel. The result is a managerial discipline for creating value faster and with less waste. ''Entrepreneurship is management.''
=== Chapter 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 way to turn vision into results. Mark illustrates a broader reality: entrepreneurs are everywhere, including intrapreneurs who form autonomous teams, navigate corporate politics, and still need a systematic way to make breakthroughs. A startup is “a human institution designed to create a new product or service under conditions of extreme uncertainty,” decoupling entrepreneurship from company size or sector. Senior leaders can cultivate entrepreneurship; {{Tooltip|Intuit}}’s years-long shift under {{Tooltip|Scott Cook}} and {{Tooltip|Brad Smith}} made {{Tooltip|SnapTax}} possible by pairing autonomy with a new management paradigm. 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 inside any organization that depends on innovation. The same uncertainty and the same discipline apply in government, nonprofits, and enterprises. ''A startup is a human institution designed to create a new product or service under conditions of extreme uncertainty.''
=== Chapter 3 – Learn ===
📚 {{Tooltip|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 buying PR or a Super Bowl ad, investing instead in experiments that could show whether product work was leading toward massive success. Over time, those experiments produced a repeatable way to measure progress and cut waste; years later, “sixty million avatars” stood as evidence that learning, not luck, powered the outcome. The lesson generalizes: treat every startup as a grand experiment and ask not “Can this be built?” but “Should it be built?” and “Can we build a sustainable business around it?” Break plans into testable pieces and run empirical tests rather than debate opinions. Actionable metrics and {{Tooltip|Innovation accounting}} separate signal from vanity noise so teams can learn when to pivot or persevere. {{Tooltip|Validated learning}} becomes the unit of progress for products, 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.''
=== Chapter 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. {{Tooltip|Zappos}} tested whether customers would buy shoes online without owning warehouses; founder {{Tooltip|Nick Swinmurn}} photographed local inventory, posted it on the web, and fulfilled purchases by hand before scaling—a {{Tooltip|minimum viable product}} that prioritized learning over polish. {{Tooltip|Dropbox}} validated demand before building complex sync technology by posting a short demo video seeded with Easter eggs for the {{Tooltip|Digg}} community, which triggered more than 10,000 Diggs in 24 hours. Remove any feature, process, or effort that does not directly contribute to the learning sought. Legal, branding, and competitive fears are acknowledged but weighed against the far greater risk of not learning fast enough. Proper experiments protect teams from opinion wars and enable rapid iteration, especially when measured with actionable metrics. Think big, start small, and let data guide the next bet. ''If you cannot fail, you cannot learn.''
{{Section separator}}
== Part II – Steer ==
===
🦘 In 2004, three college sophomores—{{Tooltip|Mark Zuckerberg}}, Dustin Moskovitz, and {{Tooltip|Chris Hughes}}—arrived in {{Tooltip|Silicon Valley}} with a fledgling campus social network and, despite little revenue and only 150,000 registered users, raised $500,000 in venture capital, followed less than a year later by $12.7 million. Investors cared that usage was intense and spreading: more than half of active users returned every day, and within weeks of launch on 4 February 2004, nearly three-quarters of {{Tooltip|Harvard}} undergraduates were using the site without paid marketing. Two assumptions sit at the center: a value hypothesis (students found the product genuinely useful) and a growth hypothesis (adoption accelerated through tight campus networks). Make those assumptions explicit and turn them into tests rather than debate abstractions or copy precedents. Plan “backwards” through the loop: decide what must be learned, specify the measurement, then build the smallest product that can produce that learning. With each iteration, evidence replaces rhetoric, and the engine of growth either catches or stalls. When learning shows the model will not work, make a deliberate strategic change, not incremental polishing. Analogy-driven storytelling gives way to data about real behavior. ''The problem with analogies like this is that they obscure the true leap of faith.''
🧫 {{Tooltip|Groupon}} began with {{Tooltip|The Point}}, an activism platform in {{Tooltip|Chicago}} that struggled until a handmade experiment—twenty people buying a two-for-one pizza coupon in the restaurant below the office—proved a different path. Early {{Tooltip|MVP}} execution was scrappy: a basic blog, coupons as PDFs assembled by hand, and manual fulfillment, which nonetheless put the company on pace for $1 billion in sales and deals across more than 375 cities worldwide. A video MVP did similar work for {{Tooltip|Dropbox}}: a short screencast seeded with in-jokes for the {{Tooltip|Digg}} community triggered rapid sign-ups—more than 10,000 Diggs within twenty-four hours—before expensive sync technology was built. A concierge MVP showed the same logic at human scale: in {{Tooltip|Austin}}, CEO {{Tooltip|Manuel Rosso}} and his VP of product built {{Tooltip|Food on the Table}} around a single paying family, visiting weekly, curating recipes tied to the local grocer’s specials, and collecting a $9.95 check by hand. As confidence grew, the team replaced visits with e-mail, automated price parsing, and later online payments, scaling only what proved useful. A “Wizard of Oz” variant let {{Tooltip|Max Ventilla}} and Damon Horowitz fake hard technology behind {{Tooltip|Aardvark}}’s Q&A interface, learning what to build only after real use revealed it; {{Tooltip|Google}} later acquired {{Tooltip|Aardvark}} for a reported $50 million. Across these cases, tests elicit behavior, not opinions, and define success in advance so results are unambiguous. The aim is to learn faster than rivals can copy features or spend on polish; when a test teaches nothing, the effort was waste. ''A minimum viable product (MVP) helps entrepreneurs start the process of learning as quickly as possible.''
=== Chapter 7 – Measure ===
📏 Startups begin as models on paper; progress becomes real only when learning is made visible through {{Tooltip|Innovation accounting}}. At {{Tooltip|IMVU}}, an early {{Tooltip|MVP}} was buggy and sales were low, but the team shipped new features daily for roughly seven months and still saw funnel metrics flat, forcing a clearer view of what to measure. {{Tooltip|Cohort analysis}} replaced aggregates: each month’s new users were tracked from registration through first login and beyond, revealing, for example, that about 60% of those who joined in February 2005 logged in at least once. With that lens, the work proceeds in three steps: establish a baseline with an {{Tooltip|MVP}}, tune the {{Tooltip|engine of growth}} with targeted changes, then decide to pivot or persevere. Vanity metrics—page hits, raw totals—obscure cause and effect; actionable metrics tie specific changes to outcomes and make next steps obvious. Accessibility matters too: reports must be simple, people-based, and widely shared so every contributor can see the same story. Auditable data lets anyone spot-check results, which curbs “success theater” and builds trust when hard calls are needed. {{Tooltip|Grockit}} founder Farbood Nivi drew on years at {{Tooltip|The Princeton Review}} and {{Tooltip|Kaplan}} and institutionalized this discipline with daily split-test summaries mailed to every employee, making learning milestones concrete. When the baseline stops moving despite honest tuning, the numbers make the case for a pivot without drama. ''Innovation accounting enables startups to prove objectively that they are learning how to grow a sustainable business.''
=== Chapter 8 – Pivot (or Persevere) ===
🔄 {{Tooltip|Votizen}} shows how evidence becomes course correction: CEO {{Tooltip|David Binetti}} gathered early signals from prospective civic participants—interest in action, trust in verified voter status, and frustration with an empty social network—and refocused the product on a single feature that worked. The result, {{Tooltip|@2gov}}, helped citizens contact their elected officials quickly via existing networks such as {{Tooltip|Twitter}} while converting that digital intent into paper letters delivered to congressional offices. With {{Tooltip|Innovation accounting}} as a guide, each milestone shortened the time between iterations, revealing what to keep and what to drop. To keep decisions from drifting, teams schedule regular “pivot or persevere” meetings—neither so frequent that noise overwhelms signal nor so rare that sunk costs lock in a bad path. A pivot is not a tweak; it changes a fundamental element—scope (zoom-in/zoom-out), customer segment or need, channel, value capture or business architecture, {{Tooltip|engine of growth}}, platform, or technology. Treat each pivot as a new strategic hypothesis and test it with a fresh {{Tooltip|MVP}}. Make the stakes explicit and the evidence public so fear of being wrong gives way to momentum from learning. Misplaced pride or attachment to past effort is the enemy; vision earns its keep by meeting the market. ''That change is called a pivot: a structured course correction designed to test a new fundamental hypothesis about the product, strategy, and engine of growth.''
{{Section separator}}
== Part III – Accelerate ==
===
📦 {{Tooltip|James Womack}} and {{Tooltip|Daniel Jones}} tell a simple story: a parent and two daughters, ages six and nine, sit at a table to stuff newsletters into envelopes—address, stamp, fold, insert, seal—and debate whether to do all of one step first or finish each envelope one by one. Running the process reveals what lean manufacturers learned after {{Tooltip|World War II}}: large batches hide mistakes until late, while small batches surface problems early and finish steady streams of completed work. The contrast scales beyond paper and stamps; {{Tooltip|Toyota}}’s production lines institutionalized rapid detection with the {{Tooltip|andon cord}} so anyone could stop the line when defects appeared. Product development often lags: at the {{Tooltip|iPhone 4}} release, {{Tooltip|Apple}} touted more than 1,500 changes, yet those changes reached customers in a single, giant batch. {{Tooltip|IMVU}} flipped that pattern by building one feature at a time with engineers and designers working side by side, releasing immediately to a small slice of users, and reading behavior within hours. The feedback loop shortened from weeks to minutes, so adjustments happened while context was fresh and risk was small. Continuous deployment proved feasible even in regulated settings; {{Tooltip|Wealthfront}} pushed more than a dozen releases per day in an {{Tooltip|SEC}}-regulated environment. The aim is faster discovery of what fails, so teams spend less time polishing the wrong thing. Small batches reduce work-in-process, make defects visible where they occur, and keep learning continuous rather than episodic. In this frame, “faster” means fewer surprises and less rework because evidence arrives earlier. Treat development as flow—rather than a series of big launches—to align effort with real customer feedback and cut preventable waste. ''The biggest advantage of working in small batches is that quality problems can be identified much sooner.''
🌱 Two very different companies—a consumer collectibles business and a B2B software vendor—show the same problem: early revenue, investor interest, and active customers, yet flat growth curves when asked to scale. Sustainable growth follows one rule—new customers come from the actions of past customers—and those actions concentrate into three engines: sticky, viral, and paid. The sticky engine is about retention: make the product valuable enough that cohorts continue to use and pay, and improvements that raise retention speed the loop disproportionately. The viral engine depends on use itself spreading the product; {{Tooltip|Hotmail}}’s 1996 tweak—“P.S. Get your free e-mail at Hotmail”—attached to every outgoing message brought a million sign-ups in six months, two million five weeks later, and a $400 million acquisition at roughly twelve million users eighteen months after launch. Viral growth is quantified by the {{Tooltip|Viral coefficient}}; when each active customer reliably brings in more than one additional user, the loop accelerates without paid spend. The paid engine is arithmetic: lifetime value must exceed cost per acquisition, and the margin between LTV and CPA determines how fast paid campaigns can expand without subsidy. Vanity totals distract here; actionable, people-based cohort metrics show whether tuning truly moves the chosen engine. Chasing every idea creates noise; focusing on the few inputs that drive the loop produces compounding effects. Once one engine works, switching engines—or mixing them—becomes a strategic choice rather than a guess. Pick the loop, instrument it carefully, and tune only the levers that change its speed. ''Therefore, I strongly recommend that startups focus on one engine at a time.''
🦎 A real incident at {{Tooltip|IMVU}} begins with customer complaints after a new release: a feature fails because a server misbehaves, which traces to an obscure subsystem used incorrectly, which traces to a developer who did not know the right procedure, which traces to the absence of training, which traces to a manager who considered training a luxury. Walking the {{Tooltip|Five Whys}} turns a technical outage into a human systems problem, and the fix follows a proportional rule: if the fault is minor, invest an hour now on the first step of an eight-week plan and escalate only if the issue recurs. Over time, that cadence of small corrective investments accumulates into robust process without freezing the team in bureaucracy. The same proportional approach led {{Tooltip|IMVU}} to build a training program strong enough that new engineers were productive on day one, with mentors assigned, a living curriculum, and shared accountability between mentor and mentee. Orientation itself became an experiment, revised as evidence mounted, so the program grew more effective and less burdensome with each cohort. Treat defects and outages as opportunities to improve the system that produced them, not as moments for blame. Pull the {{Tooltip|andon cord}} early, bring the right people to the table, and make fixes small, quick, and durable. As quality rises, speed rises with it because teams stop tripping over the same hidden faults. Organizations that evolve in this way maintain agility even as headcount climbs and product complexity grows. A culture that links problems to learning—rather than to punishment—keeps improving on its own. ''I call this building an adaptive organization, one that automatically adjusts its process and performance to current conditions.''
💡 In a large-company product meeting, senior managers argued over a pricing experiment they had run: custom reports filled the room, the data-warehouse team fielded questions, and yet no one could agree what the numbers meant or which customers had actually seen the test. That muddle underscores the need for internal startup teams with the right setup—scarce but secure resources, independent authority to build and change, and a personal stake in outcomes—so experiments yield unambiguous learning instead of politics. {{Tooltip|Toyota}}’s {{Tooltip|shusa}} model makes ownership concrete: a chief engineer holds final authority over every aspect of a new vehicle, embodying end-to-end responsibility rather than functional turf. To keep innovation “in the open” without blindsiding colleagues, an innovation sandbox sets clear rules: true split-tests limited to specific segments or territories, owned by one team from end to end, bounded in time and exposure, and reported on a standard set of five to ten actionable metrics. Because every team inside the sandbox uses the same metrics and monitors customer reactions in real time, good ideas survive scrutiny and bad ones die quickly. The approach turns black-box breakthroughs—like {{Tooltip|IBM}}’s PC story—into a repeatable practice that a parent organization can sustain and reintegrate. {{Tooltip|Intuit}}’s {{Tooltip|SnapTax}} shows how a small “island of freedom” can run rapid tests within a big company while still reporting transparently. Portfolio thinking follows: protect the core, seed disruptive bets, and measure each one with {{Tooltip|Innovation accounting}} until it is either folded back in or retired. The effect is cultural as much as technical, replacing status contests with evidence and giving would-be founders a path to build inside. Trade heroics for cadence: short cycles, clear gates, and visible outcomes. In this frame, autonomy is not an indulgence but a control system that keeps risk small and learning fast. When that platform exists, people who thrive on creating the new do not have to leave to do their best work. ''In fact, entrepreneurship should be considered a viable career path for innovators inside large organizations.''
▲💡 '''12 – Innovate.'''
♻️ A century after Frederick Winslow Taylor’s 1911 treatise on scientific management popularized management by exception, standardized tasks, and the task-plus-bonus system, the lesson is mixed. Those techniques, and later {{Tooltip|Lean manufacturing}}, showed that work can be studied and improved, yet they also carried prejudices and rigidities that treated people as automatons. Modern waste comes less from how things are assembled and more from building the wrong things at industrial scale—failed launches, large-batch death spirals, and “success theater” that dresses up opinion as fact. The remedy is not more exhortation or slower, bigger plans but a research-driven practice for innovation: form hypotheses, run experiments, and hold teams accountable to {{Tooltip|Validated learning}}. Taylor’s spirit of systematic inquiry becomes a call for startup testing labs, shorter cycle times, and public-private collaborations that compare methods with objective outcomes. A {{Tooltip|Long-Term Stock Exchange}} is imagined where firms report on {{Tooltip|Innovation accounting}} alongside profits, align executive pay to long-horizon results, and reduce incentives for vanity metrics. The vision extends to organizational “superpowers”: anyone, even a junior employee, can surface testable assumptions, design a learning plan, and avoid pseudoscience by proving cause-and-effect with cohort behavior over time. Rather than choosing between speed and quality, teams get both by bypassing work that does not lead to learning and by shrinking batch size when uncertainty is high. The payoff is humane and productive—less blame, more candor, and fewer meetings in which evidence is ambiguous by design. Efficiency is not the finish line; it is a property of systems that measure truth early. A century on, the greatest untapped resource is not muscle or machines but attention and imagination. ''Most of all, we would stop wasting people’s time.''
▲♻️ '''13 – Epilogue: Waste Not.'''
🤝 A practical route from reading to practice emerges as the Lean Startup movement spreads beyond {{Tooltip|Silicon Valley}} to local ecosystems worldwide. The official site at theleanstartup.com hosts case studies, talks, and links to the {{Tooltip|Startup Lessons Learned}} blog so practitioners can learn directly from applied examples. Meetups make the work local; there are more than a hundred groups, with large communities in San Francisco, Boston, New York, and Chicago, and simple tools exist to find or start one. A community-maintained {{Tooltip|Lean Startup Wiki}} catalogs events and resources for teams that do not use Meetup.com. The {{Tooltip|Lean Startup Circle}}—founded by {{Tooltip|Rich Collins}}—runs an active mailing list with thousands of entrepreneurs trading tactics, metrics tips, and field reports every day. Reading lists point newcomers to customer-development classics and contemporary blogs, turning scattered insights into a shared vocabulary for experiments. The emphasis stays on doing: form a small team, run a test in a local context, and share results so others can build on what works. As participation grows, the method evolves through documented practice rather than slogans. That open, peer-to-peer cadence mirrors the process it advocates: short loops, clear metrics, and concrete next steps. The destination is not a club but a habit of learning in public. ''Reading is good, action is better.''
▲''
▲🤝 '''14 – Join the Movement.'''
▲''Bibliographic details (publication date and total pages) are also reflected in the publisher’s catalogue.''<ref name="PRH2011">{{cite web |title=The Lean Startup by Eric Ries: 9780307887894 |url=https://www.penguinrandomhouse.com/books/210088/the-lean-startup-by-eric-ries/ |website=PenguinRandomHouse.com |publisher=Penguin Random House |date=13 September 2011 |access-date=10 November 2025}}</ref>
{{Section separator}}
== Background & reception ==
🖋️ '''Author & writing'''. Ries came to the book as a programmer-turned-entrepreneur: he co-founded {{Tooltip|IMVU}} and served as its CTO, wrote the
📈 '''Commercial reception'''. According to its UK publisher, the book has sold
👍 '''Praise'''. The ''{{Tooltip|Financial Times}}'' ({{Tooltip|Philip Delves Broughton}}, 18 September 2011) praised the
▲📈 '''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.<ref name="PenguinUK2011" /> Upon release it entered the New York Times Advice best-seller list at No. 2 in September 2011, reflecting strong early demand.<ref name="Wired2012Upstart" />
👎 '''Criticism'''. Some technologists and investors quoted in ''{{Tooltip|Wired}}'' argued that the philosophy can trade vision for “plodding validation,” with critics
▲👍 '''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.<ref name="FT2011">{{cite news |title=Book review: The Lean Startup |url=https://www.ft.com/content/8a022f32-de33-11e0-9fb7-00144feabdc0 |work=Financial Times |date=18 September 2011 |access-date=10 November 2025 |last=Broughton |first=Philip Delves}}</ref> 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.<ref name="HBR2013" /> A feature in ''Wired'' lauded the method’s “inexorable logic,” commending its demand for real-world testing and actionable metrics over intuition or hype.<ref name="Wired2012Upstart" />
🌍 '''Impact & adoption'''. {{Tooltip|General
▲👎 '''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.<ref name="Wired2012Upstart" /> In Harvard Business Review, Scott D. Anthony cautioned that MVPs are easily misapplied, warning against letting “the minimal” eclipse “the viable.”<ref name="HBR2012MVP">{{cite web |title=The Dangers of the Minimal Viable Product |url=https://hbr.org/2012/04/the-dangers-of-teh-minimal-via |website=Harvard Business Review |publisher=Harvard Business Publishing |date=9 April 2012 |access-date=10 November 2025 |last=Anthony |first=Scott D.}}</ref> 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.<ref name="HBR2019Mollick">{{cite web |title=What the Lean Startup Method Gets Right and Wrong |url=https://hbr.org/2019/10/what-the-lean-startup-method-gets-right-and-wrong |website=Harvard Business Review |publisher=Harvard Business Publishing |date=21 October 2019 |access-date=10 November 2025 |last=Mollick |first=Ethan}}</ref> 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.<ref name="MITSMR2019">{{cite web |title=Why Large Companies Struggle With Lean |url=https://sloanreview.mit.edu/article/why-large-companies-struggle-with-lean/ |website=MIT Sloan Management Review |publisher=Massachusetts Institute of Technology |date=27 November 2019 |access-date=10 November 2025}}</ref>
{{Section separator}}
▲🌍 '''Impact & adoption'''. General Electric’s FastWorks program applied Lean Startup principles to speed up development cycles and decision-making, illustrating diffusion into heavy industry.<ref name="HBR2014GE">{{cite web |title=How GE Applies Lean Startup Practices |url=https://hbr.org/2014/04/how-ge-applies-lean-startup-practices |website=Harvard Business Review |publisher=Harvard Business Publishing |date=23 April 2014 |access-date=10 November 2025}}</ref> Universities incorporated the approach into curricula—Harvard Business School, for example, integrated the ideas into entrepreneurship teaching soon after publication.<ref name="Wired2012Upstart" /> 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.<ref name="MITSMR2019" /><ref name="Wired2012Upstart" />
== See also ==
{{Youtube thumbnail | fEvKo90qBns | Eric Ries at Google on
{{Youtube thumbnail | QaoVWtLX038 | Validate your business idea — ''The Lean Startup'' summary
▲{{Youtube thumbnail | fEvKo90qBns | Eric Ries at Google on “The Lean Startup” (82 min)}}
▲{{Youtube thumbnail | QaoVWtLX038 | Validate your business idea — Lean Startup summary (14 min)}}
{{
{{
{{
{{
{{
▲{{The Compound Effect/thumbnail}}
{{Insert before References}}
{{Section separator}}
== References ==
{{reflist}}
{{Insert bottom}}
| |||