Introduction
The introduction is built on the contrast between two of Ries’s stories—the failure of his first startup and the success of IMVU. From the failure, he draws a diagnosis: the mythmaking industry sells the story of “talent + persistence + the right product,” yet Startup Success Is Constructed—the Right Process Can Be Learned: what matters are precisely the “boring things,” process rather than genes. The first instinctive response to market failure was an engineering one—and Market Failure Is Instinctively Treated with Engineering Means, which only multiplies losses. Hence the introduction’s central move: A Startup Does Not Abolish Management, but the Management of the Predictable. Entrepreneurship is a kind of management, but management of a different, experimental kind, because A Startup Is Defined by Uncertainty, Not Size; the method therefore applies both in a garage and in a corporation.
IMVU’s methods worked before there was any theory, but A Working Practice Cannot Be Transferred Without a Common Language. It was this lack of transferability that drove Ries to seek a conceptual framework, which he found in Toyota’s lean manufacturing. The core of the resulting method is as follows:
- A Startup Exists to Learn How to Build a Sustainable Business—validated knowledge, rather than a product or revenue, is both the goal and the measure of progress;
- Users’ Opinions Are Data, Not Commands—the focus is on what customers want, “without asking them”: customers are subjected to experiments rather than having their wishes fulfilled;
- the “Build-Measure-Learn” cycle must be run as quickly as possible, and each turn must yield a “pivot or persevere” decision; without that decision, the loop degenerates into rapid development;
- Waste in Innovation Is Work That Produces No Learning—the method’s mission is to eliminate the principal waste: products that nobody needs;
- Innovation Needs Its Own Progress Accounting—because progress is measured in knowledge, conventional reporting does not register it, so innovation accounting is needed.
A critical caveat: Lean Startup Is Grounded in the Genre It Itself Debunks. The method’s key evidence, the story of IMVU’s success, itself belongs to the genre of success stories that Ries had exposed a page earlier as the product of a sampling error.
1. Start
The chapter opens with an institutional argument: a startup is the building of an organization, an association of people, and management is therefore necessary to it by definition, even before any discussion of uncertainty. This is a second, independent route to the conclusion that “A Startup Does Not Abolish Management, but the Management of the Predictable,” complementing the argument from the condition set out in A Startup Is Defined by Uncertainty, Not Size.
The roots of the Lean Startup method are macroeconomic: during the twentieth century, the effects of productivity growth outweighed job losses, leaving the economy with excess capacity that firms squander—including in failed startups. The general four-stage mechanism of this macroeconomic process is developed in Structural Shifts from Increased Productivity. Thus the question of where to direct the surplus becomes the method’s entry point: Waste in Innovation Is Work That Produces No Learning, and the method supplies the answer—the surplus must be directed toward producing knowledge.
The chapter recounts the Lean movement itself as background material—a change in how production is understood: workers’ contribution, small batches, just-in-time, and waste reduction. In the repository, this is covered by the cluster “This Is Lean,” “Resource and Flow Efficiency,” and “Work in Progress.”
The chapter then repeats and reinforces the introduction’s thesis that startup progress is measured by validated knowledge, through two moves. The first is a claim to scientific status: a theory of entrepreneurial management must make testable predictions, and it does—but A Theory of Managing Uncertainty Is Falsifiable at the Process Level, Not the Outcome Level. The management of the unpredictable is itself predictable; its predictions concern the behavior of organizations, not the fate of products. The second is a mechanism of resistance: the habit of measuring progress in tangible units makes intangible knowledge hard to recognize as progress—a psychological layer of blindness recorded in Innovation Needs Its Own Progress Accounting. The same mechanism also makes the prediction of teams’ complaints come true.
The chapter narrows the startup’s telos in product terms and in tempo: identify the right product—what customers want and will pay for—as early as possible. The mode for achieving this goal is the metaphor of a car: A Startup Is Steered by Feedback, Not Driven by a Pre-Launch Calculation. Day-to-day work is tuning the engine of growth through product, marketing, and process improvements; a mistaken assumption is not a catastrophe but the next turn of the steering wheel; when the engine works and steering has been mastered, one presses the accelerator and scales with maximum acceleration. The cost of the opposite mode is achieved failure: the disciplined execution of a mistaken plan.
The levels of management form a pyramid: vision determines strategy, strategy determines product, and the pace of change is inversely related to height—product is optimized continuously, strategy changes through a pivot, and vision is preserved. The Vision–Strategy–Product Hierarchy Is Built Along a Gradient of Falsifiability, and vision remains the method’s unfalsifiable core. The chapter’s final scene places two frames of failure face to face: for a CFO, failure to deliver a result is a failure of planning or execution, and in either case someone is to blame; for an intrapreneur, a failed experiment is a necessary step from which knowledge is extracted (the management₁ dichotomy appears in A Startup Does Not Abolish Management, but the Management of the Predictable, and the recalculation of the cost of failure in A Startup Exists to Learn How to Build a Sustainable Business).