The Lean Startup - Revision history

Wikilah admin at 14:13, 2 February 2026

2026-02-02T14:13:34Z

← Older revision		Revision as of 22:13, 2 February 2026
Line 1:		Line 1:


	{{Insert top}}{{Insert quote panel		{{Insert top}}{{Insert quote panel
	\| {{The Lean Startup/random quote}}		\| {{The Lean Startup/random quote}}
Line 105:		Line 103:
	{{Youtube thumbnail \| fEvKo90qBns \| Eric Ries at Google on ''The Lean Startup''}}		{{Youtube thumbnail \| fEvKo90qBns \| Eric Ries at Google on ''The Lean Startup''}}
	{{Youtube thumbnail \| QaoVWtLX038 \| Validate your business idea — ''The Lean Startup'' summary}}		{{Youtube thumbnail \| QaoVWtLX038 \| Validate your business idea — ''The Lean Startup'' summary}}


	{{The Almanack of Naval Ravikant/thumbnail}}		{{The Almanack of Naval Ravikant/thumbnail}}

Wikilah admin at 07:55, 17 January 2026

2026-01-17T07:55:02Z

← Older revision		Revision as of 15:55, 17 January 2026
Line 1:		Line 1:


	{{Insert top}}{{Insert quote panel		{{Insert top}}{{Insert quote panel
	\| {{The Lean Startup/random quote}}		\| {{The Lean Startup/random quote}}
	}}		}}

			{{Section separator}}
	== Introduction ==		== Introduction ==

Line 30:		Line 33:
	Since publication, the book has sold more than one million copies in more than thirty languages and debuted at No. 2 on the {{Tooltip\|New York Times Advice best-seller list}} in September 2011.<ref name="PenguinUK2011">{{cite web \|title=The Lean Startup \|url=https://www.penguin.co.uk/books/185058/the-lean-startup-by-ries-eric/9780670921607 \|website=Penguin Books UK \|publisher=Penguin Random House \|date=6 October 2011 \|access-date=10 November 2025}}</ref><ref name="Wired2012Upstart">{{cite news \|title=In Silicon Valley, Eric Ries has the stage -- and the crowd is going wild \|url=https://www.wired.com/story/the-upstart \|work=Wired \|date=18 June 2012 \|access-date=10 November 2025 \|last=Greenwald \|first=Ted}}</ref>		Since publication, the book has sold more than one million copies in more than thirty languages and debuted at No. 2 on the {{Tooltip\|New York Times Advice best-seller list}} in September 2011.<ref name="PenguinUK2011">{{cite web \|title=The Lean Startup \|url=https://www.penguin.co.uk/books/185058/the-lean-startup-by-ries-eric/9780670921607 \|website=Penguin Books UK \|publisher=Penguin Random House \|date=6 October 2011 \|access-date=10 November 2025}}</ref><ref name="Wired2012Upstart">{{cite news \|title=In Silicon Valley, Eric Ries has the stage -- and the crowd is going wild \|url=https://www.wired.com/story/the-upstart \|work=Wired \|date=18 June 2012 \|access-date=10 November 2025 \|last=Greenwald \|first=Ted}}</ref>

			{{Section separator}}
	== Part I – Vision ==		== Part I – Vision ==

Line 44:		Line 48:
	🧪 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.''		🧪 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 ==		== Part II – Steer ==

Line 58:		Line 63:
	🔄 {{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.''		🔄 {{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 ==		== Part III – Accelerate ==

Line 81:		Line 87:
	''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>		''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 ==		== Background & reception ==

Line 93:		Line 100:
	🌍 '''Impact & adoption'''. {{Tooltip\|General Electric}}’s {{Tooltip\|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—{{Tooltip\|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 {{Tooltip\|U.S. National Science Foundation}}’s {{Tooltip\|I-Corps program}}, which uses {{Tooltip\|Lean LaunchPad}}/Lean Startup methods to commercialize academic research, and ''{{Tooltip\|Wired}}'' reported early experiments in municipal government via {{Tooltip\|Code for America}}.<ref name="MITSMR2019" /><ref name="Wired2012Upstart" />		🌍 '''Impact & adoption'''. {{Tooltip\|General Electric}}’s {{Tooltip\|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—{{Tooltip\|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 {{Tooltip\|U.S. National Science Foundation}}’s {{Tooltip\|I-Corps program}}, which uses {{Tooltip\|Lean LaunchPad}}/Lean Startup methods to commercialize academic research, and ''{{Tooltip\|Wired}}'' reported early experiments in municipal government via {{Tooltip\|Code for America}}.<ref name="MITSMR2019" /><ref name="Wired2012Upstart" />

			{{Section separator}}
	== Related content & more ==
			== See also ==

	=== YouTube videos ===
	{{Youtube thumbnail \| fEvKo90qBns \| Eric Ries at Google on ''The Lean Startup''}}		{{Youtube thumbnail \| fEvKo90qBns \| Eric Ries at Google on ''The Lean Startup''}}
	{{Youtube thumbnail \| QaoVWtLX038 \| Validate your business idea — ''The Lean Startup'' summary}}		{{Youtube thumbnail \| QaoVWtLX038 \| Validate your business idea — ''The Lean Startup'' summary}}

	=== CapSach articles ===
	{{The Almanack of Naval Ravikant/thumbnail}}		{{The Almanack of Naval Ravikant/thumbnail}}
	{{Zero to One/thumbnail}}		{{Zero to One/thumbnail}}
Line 105:		Line 111:
	{{Shoe Dog/thumbnail}}		{{Shoe Dog/thumbnail}}
	{{The E-myth Revisited/thumbnail}}		{{The E-myth Revisited/thumbnail}}
	{{~~CS/Self-improvement~~ book summaries/thumbnail}}		{{book summaries/thumbnail}}
	{{Insert before References}}		{{Insert before References}}

			{{Section separator}}
	== References ==		== References ==
	{{reflist}}		{{reflist}}

	[[Category:Self-improvement books]]
	[[Category:CS articles]]
	{{Insert bottom}}		{{Insert bottom}}

Wikilah admin at 13:28, 16 November 2025

2025-11-16T13:28:10Z

Show changes

Wikilah admin at 10:10, 11 November 2025

2025-11-11T10:10:16Z

← Older revision		Revision as of 18:10, 11 November 2025
Line 87:		Line 87:

	=== CapSach articles ===		=== CapSach articles ===
	{{~~Digital~~ ~~Minimalism~~/thumbnail}}		{{The Almanack of Naval Ravikant/thumbnail}}
	{{~~Four~~ ~~Thousand~~ ~~Weeks~~/thumbnail}}		{{Zero to One/thumbnail}}
	{{The ~~One~~ Thing/thumbnail}}		{{The Hard Thing About Hard Things/thumbnail}}
	{{~~Make~~ ~~Your Bed~~/thumbnail}}		{{Shoe Dog/thumbnail}}
	{{The ~~Magic~~ ~~of Thinking Big~~/thumbnail}}		{{The E-myth Revisited/thumbnail}}
	{{The Compound Effect/thumbnail}}
	{{CS/Self-improvement book summaries/thumbnail}}		{{CS/Self-improvement book summaries/thumbnail}}
	{{Insert before References}}		{{Insert before References}}

Wikilah admin at 09:06, 11 November 2025

2025-11-11T09:06:20Z

Show changes

Wikilah admin at 03:14, 11 November 2025

2025-11-11T03:14:30Z

Show changes

Wikilah admin at 02:55, 11 November 2025

2025-11-11T02:55:46Z

← Older revision		Revision as of 10:55, 11 November 2025
Line 56:		Line 56:
	=== III – Accelerate ===		=== III – Accelerate ===

			📦 '''9 – Batch.''' James Womack and 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 decades ago after 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; Toyota’s production lines institutionalized rapid detection with the andon cord so anyone could stop the line when defects appeared. Product development often lags behind: at the iPhone 4 release, Apple touted more than 1,500 changes, yet those changes reached customers in a single, giant batch. 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 still fresh and risk was still small. Continuous deployment proved feasible even in regulated settings: Wealthfront pushed more than a dozen releases per day in an SEC-regulated environment. The point is not speed for its own sake but 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 instead of episodic. In this frame, “faster” means fewer surprises and less rework because evidence arrives earlier. Treating development as flow—rather than a series of big launches—aligns effort with real customer feedback and cuts preventable waste. ''The biggest advantage of working in small batches is that quality problems can be identified much sooner.''
	📦 '''9 – Batch.'''

			🌱 '''10 – Grow.''' 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, the book insists, 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 all 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; 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 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.''
	🌱 '''10 – Grow.'''

			🦎 '''11 – Adapt.''' A real incident at 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 didn’t know the right procedure, which traces to the absence of training, which traces to a manager who considered training a luxury. Walking the 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 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. The lesson generalizes: treat defects and outages as opportunities to improve the system that produced them, not as moments for blame. Pull the andon cord early, bring the right people to the table, and make fixes small, quick, and durable. As quality rises, speed can rise 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.''
	🦎 '''11 – Adapt.'''

			💡 '''12 – Innovate.''' 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 frames 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 the outcome—so experiments yield unambiguous learning instead of politics. Toyota’s shusa model makes the 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, the chapter proposes an innovation sandbox: true split-tests limited to specific segments or territories, owned by one team from end to end, bounded in time, exposure, and a standard report 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 IBM’s PC story—into a repeatable practice that a parent organization can sustain and reintegrate. Intuit’s 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 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. Teams learn to 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 don’t 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.'''

			♻️ '''13 – Epilogue: Waste Not.''' The year marks a century since Frederick Winslow Taylor’s 1911 treatise on scientific management, which popularized management by exception, standardized tasks, and the task-plus-bonus system that helped power twentieth-century prosperity. Those techniques, and later lean manufacturing, proved that work can be studied and improved, yet they also carried prejudices and rigidities that treated people as automatons. The epilogue argues that modern waste comes less from how we assemble things 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 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. It even imagines a Long-Term Stock Exchange where firms report on 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 as well as productive—less blame, more candor, and fewer meetings in which evidence is ambiguous by design. Seen this way, efficiency is not the finish line; it is a property of systems that measure truth early. A century after Taylor, 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.'''

			🤝 '''14 – Join the Movement.''' The closing chapter maps a practical route from reading to practice as the Lean Startup movement spreads beyond Silicon Valley to local ecosystems worldwide. An official site at theleanstartup.com hosts case studies, talks, and links to the Startup Lessons Learned blog so practitioners can learn directly from applied examples. Meetups make the work local: as of this writing there are over 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 Lean Startup Wiki catalogs events and resources for teams that don’t use Meetup.com. The Lean Startup Circle—founded by 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 your 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.'''

	== Background & reception ==		== Background & reception ==

Wikilah admin at 02:22, 11 November 2025

2025-11-11T02:22:08Z

← Older revision		Revision as of 10:22, 11 November 2025
Line 46:		Line 46:
	=== II – Steer ===		=== II – Steer ===

			🦘 '''5 – Leap.''' In 2004, three college sophomores—Mark Zuckerberg, Dustin Moskovitz, and Chris Hughes—arrived in 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 Harvard undergraduates were using the site without a dollar of paid marketing. That pattern validated two leap-of-faith assumptions: a value hypothesis (students found the product genuinely useful) and a growth hypothesis (adoption accelerated through tight campus networks). The chapter names those two assumptions as the riskiest parts of any plan and urges teams to make them explicit. Experiments then revolve around turning those assumptions into testable hypotheses rather than debating abstractions or copying precedents. Planning runs “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 won’t work, the remedy is 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.''
	🦘 '''5 – Leap.'''

			🧫 '''6 – Test.''' Groupon’s origin story begins with The Point, an activism platform in Chicago that struggled until a simple, handmade experiment—twenty people buying a two-for-one pizza coupon in the restaurant below the office—proved a different path. Early “MVP” execution was unapologetically 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 Dropbox: a short screencast seeded with in-jokes for the Digg community triggered rapid sign-ups—more than 10,000 Diggs within twenty-four hours—before expensive sync technology was built. The concierge MVP shows the same logic at human scale: in Austin, CEO Manuel Rosso and his VP of product built 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 Max Ventilla and Damon Horowitz fake hard technology behind Aardvark’s Q&A interface, learning what to build only after real use revealed it; Google later acquired Aardvark for a reported $50 million. Across these cases, tests elicit behavior, not opinions, and they define success in advance so results are unambiguous. The point is not to be frugal for its own sake but to learn faster than rivals can copy features or spend on polish. When an experiment teaches nothing, the effort was waste; when it teaches quickly, even a crude artifact is a win. ''A minimum viable product (MVP) helps entrepreneurs start the process of learning as quickly as possible.''
	🧫 '''6 – Test.'''

			📏 '''7 – Measure.''' Startups begin as models on paper; progress becomes real only when learning is made visible through innovation accounting. At IMVU, an early 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. Cohort analysis replaced aggregates: each month’s new users was 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 MVP, tune the engine of growth with targeted changes, and 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. Grockit’s founder Farbood Nivi drew on years at Princeton Review and 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.''
	📏 '''7 – Measure.'''

			🔄 '''8 – Pivot (or Persevere).''' Votizen demonstrates how evidence turns into course correction: CEO 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, @2gov, helped citizens contact their elected officials quickly via existing networks such as Twitter while converting that digital intent into paper letters delivered to congressional offices. With 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, engine of growth, platform, or even the underlying technology. The discipline is to treat each pivot as a new strategic hypothesis and test it with a fresh MVP. By making the stakes explicit and the evidence public, fear of being wrong gives way to momentum from learning. Misapplied pride or attachment to past effort is the enemy; the method respects vision by insisting it meet 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.''
	🔄 '''8 – Pivot (or Persevere).'''

	=== III – Accelerate ===		=== III – Accelerate ===

Wikilah admin at 02:05, 11 November 2025

2025-11-11T02:05:52Z

← Older revision		Revision as of 10:05, 11 November 2025
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 ===

Wikilah admin at 01:42, 11 November 2025

2025-11-11T01:42:20Z

← Older revision		Revision as of 09:42, 11 November 2025
Line 36:		Line 36:
	=== I – Vision ===		=== I – Vision ===

			🚀 '''1 – Start.'''
	🚀 '''1 – Start.''' Entrepreneurship is framed as a managerial discipline for environments of extreme uncertainty, where progress is measured not by output but by learning. The chapter introduces the Build–Measure–Learn feedback loop as a steering mechanism: turn ideas into products, observe real customer behavior, and decide when to pivot or persevere. Planning yields to rapid, evidence‑driven adjustments aimed at building a sustainable business. ''Entrepreneurship is management.''

			🧭 '''2 – Define.'''
	🧭 '''2 – Define.''' The scope of “entrepreneur” expands beyond garage founders to intrapreneurs inside large firms, and “startup” is defined by context rather than size or sector. A detailed case on Intuit’s SnapTax shows a constrained early release validating demand—more than 350,000 downloads in its first three weeks—illustrating how disciplined experimentation can thrive in a corporate setting. The chapter argues that cultivating entrepreneurship requires explicit executive support and a new management paradigm. ''A startup is a human institution designed to create a new product or service under conditions of extreme uncertainty.''

			📚 '''3 – Learn.'''
	📚 '''3 – Learn.''' Validated learning becomes the unit of progress, replacing vanity metrics and “success theater” with empirical evidence that the business model is working. The IMVU story shows how shipping imperfect product, instrumenting behavior, and reading real usage revealed which assumptions were wrong and where value actually resided. Everything a startup does—every feature and campaign—is treated as an experiment designed to produce reliable learning. ''We must learn what customers really want, not what they say they want or what we think they should want.''

			🧪 '''4 – Experiment.'''
	🧪 '''4 – Experiment.''' Ideas are translated into falsifiable hypotheses, experiments are designed to test behavior (not opinions), and learning is maximized by defining clear pass/fail criteria in advance. The chapter rejects the “just do it” approach as activity without insight, urging small, fast tests that reveal causal impact. Evidence, not enthusiasm, determines the next move in the Build–Measure–Learn loop. ''This is one of the most important lessons of the scientific method: if you cannot fail, you cannot learn.''

	=== II – Steer ===		=== II – Steer ===

			🦘 '''5 – Leap.'''
	🦘 '''5 – Leap.''' Leap‑of‑faith assumptions anchor the initial strategy, and progress starts by naming them explicitly as the value hypothesis (do customers find the product valuable?) and the growth hypothesis (how new customers will discover and adopt it). The chapter opens with Facebook’s early traction—roughly 150,000 registered users, little revenue, yet $500,000 raised in 2004 and $12.7 million less than a year later—showing how real engagement (more than half logging in daily) can validate value while campus‑by‑campus expansion tests growth. Analogies and persuasive decks are demoted; what matters is translating those leaps into testable hypotheses that can be measured quickly inside the Build–Measure–Learn loop. ''The problem with analogies like this is that they obscure the true leap of faith.''

			🧫 '''6 – Test.'''
	🧫 '''6 – Test.''' Testing begins with a minimum viable product designed to elicit behaviors, not opinions, from early adopters willing to tolerate flaws in exchange for vision. Examples range from concierge setups to smoke tests, with Groupon’s origin story—rebranded from The Point—using a skinned WordPress blog to post daily deals and even sell T‑shirts via email instructions to prove demand before building infrastructure. The aim is speed of learning: ship the smallest thing that can run a full loop, instrument it, and decide the next experiment. ''A minimum viable product (MVP) helps entrepreneurs start the process of learning as quickly as possible.''

			📏 '''7 – Measure.'''
	📏 '''7 – Measure.''' Measurement shifts to innovation accounting, a discipline for turning leap‑of‑faith assumptions into a quantitative model and tracking progress with learning milestones. Cohort analysis replaces aggregate dashboards, and good metrics follow the three A’s—actionable, accessible, auditable—so teams can see causal effects, share simple people‑based reports, and verify data. The method advances in three steps: establish a baseline with an MVP, tune the engine of growth, then decide whether results justify a pivot or perseverance. ''Innovation accounting enables startups to prove objectively that they are learning how to grow a sustainable business.''

			🔄 '''8 – Pivot (or Persevere).'''
	🔄 '''8 – Pivot (or Persevere).''' When optimization stalls, teams convene regular “pivot or persevere” meetings—every few weeks to a few months—to make a deliberate course correction or recommit to the path. Pivots target fundamentals rather than tweaks, taking forms such as zoom‑in or zoom‑out, customer‑segment or customer‑need shifts, channel or value‑capture changes, engine‑of‑growth switches, or technology/platform moves. The choice is grounded in evidence from innovation accounting and cohort trends and resets the baseline for a new round of experiments. ''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.''

	=== III – Accelerate ===		=== III – Accelerate ===

			📦 '''9 – Batch.'''
	📦 '''9 – Batch.''' The envelope‑stuffing exercise shows how single‑piece flow beats large‑batch processing by surfacing errors sooner and finishing the total job faster. Toyota’s pioneers—Taiichi Ohno and Shigeo Shingo—used SMED and small, general‑purpose machines to shrink changeover time and enable variety, a logic startups reuse to speed learning. Applied to software at IMVU and in other settings, teams ship features one at a time, keep work‑in‑process low, and run more experiments with less waste. ''The biggest advantage of working in small batches is that quality problems can be identified much sooner.''

			🌱 '''10 – Grow.'''
	🌱 '''10 – Grow.''' Sustainable expansion is modeled as a feedback loop driven by one primary engine at a time—sticky (retention), viral (peer‑to‑peer spread), or paid (LTV exceeds CPA). Cohort metrics guide tuning: for the viral engine, focus on behaviors that raise the viral coefficient toward or above 0.9 while ignoring changes that don’t affect the loop. Product work concentrates on the few levers that move the chosen engine rather than “a zillion” optimizations. ''Therefore, I strongly recommend that startups focus on one engine at a time.''

			🦎 '''11 – Adapt.'''
	🦎 '''11 – Adapt.''' Fast organizations build in speed regulators: stop‑the‑line responses, small corrective actions, and the Five Whys to convert defects and outages into durable learning. The method keeps blame low and systems thinking high—bring the right people into the room, make proportional investments, and institutionalize small fixes so quality improves as you scale. The aim is an operating culture that updates itself as conditions change. ''I call this building an adaptive organization, one that automatically adjusts its process and performance to current conditions.''

			💡 '''12 – Innovate.'''
	💡 '''12 – Innovate.''' Established companies and scaling startups need portfolio thinking to run operational excellence and disruptive bets in parallel, which requires dedicated startup teams with scarce but secure resources, independent authority, and a personal stake in the outcome. Executives create a platform for experimentation—an innovation sandbox with clear rules and innovation accounting—so teams can run fast, reversible tests without endless approvals or political risk. Intuit’s SnapTax “island of freedom” and Toyota’s shusa chief‑engineer model illustrate how to grant end‑to‑end ownership while protecting the parent organization. ''In fact, entrepreneurship should be considered a viable career path for innovators inside large organizations.''

			♻️ '''13 – Epilogue: Waste Not.'''
	♻️ '''13 – Epilogue: Waste Not.''' A century after Frederick Winslow Taylor’s Scientific Management, the closing essay argues for disciplined experimentation in modern knowledge work while rejecting the era’s prejudices and rigid top‑down control. The real enemy is preventable waste—projects that burn months of effort without validated learning, large‑batch initiatives that hide defects, and meetings that produce data but no decisions. Redirecting attention to small, auditable experiments can unlock dormant capacity across companies, nonprofits, and government. ''Most of all, we would stop wasting people’s time.''

			🤝 '''14 – Join the Movement.'''
	🤝 '''14 – Join the Movement.''' The final chapter points readers to practical communities—Lean Startup Meetups, the Lean Startup Wiki, and the Lean Startup Circle—so learning happens in local ecosystems with peers. Participation means running small experiments, sharing results, and contributing tools and case studies so the method evolves through practice. If there’s no nearby group, start one and keep cycling through Build–Measure–Learn in public. ''Reading is good, action is better.''

	== Background & reception ==		== Background & reception ==