Key Takeaways
Treat uncertainty as a management problem, not a forecasting failure
Separate the known from the guessed. Eric Ries’s case begins at GE, where leaders faced a five-year plan for a new engine and a forecast projecting billions in future revenue. The engineering was challenging, but many commercial assumptions remained untested: which customers would buy, what they needed, and how GE would reach them. The Startup Way treats entrepreneurship as a management discipline for work where reliable forecasts are impossible, rather than as a personality trait or a privilege reserved for new companies.
Keep execution and discovery together. GE first considered a simpler engine for one use, then realized an existing model could be modified to test demand. The first customer order followed far sooner than the original plan allowed. The point is not to discard operational discipline. Established processes remain valuable for producing known products reliably; experimentation is needed to discover what should be built next.
The useful distinction is not between old companies and startups, but between work with known requirements and work where the requirements themselves are uncertain. That resembles the broader organizational challenge of balancing exploitation, improving what already works, with exploration, searching for what might work. A single management system tends to privilege one side. The book’s contribution is to make uncertainty visible as a distinct operating condition, so leaders can choose appropriate controls instead of misreading every missed forecast as poor execution. The caution is that uncertainty does not excuse weak planning: teams still need explicit hypotheses, limits on spending, and evidence of learning.
Give uncertain work small, cross-functional teams and protect the core
Make the team the unit of discovery. Ries calls the internal startup the basic organizational unit for highly uncertain projects. Unlike a conventional project passed between departments, it is a small, dedicated, cross-functional group that can test an idea with customers and adjust without waiting for every function to hand off its work. The approach does not require every employee or project to become a startup. Routine work can remain in established operating systems.
Let successful experiments find a home. Airbnb created a small team to explore new trip-related services while its core lodging business continued to operate. The arrangement gave the experiment time and focus without confusing it with day-to-day product improvements. A successful internal startup may eventually join an existing division or become a new one. The organization needs to decide that pathway before success makes the experiment threatening to established managers.
Small teams can reduce coordination costs because fewer people need to share information and decisions. Cross-functional membership also brings customer, technical, and commercial questions into the same room, where trade-offs can be resolved earlier. This is especially useful when work crosses departmental boundaries. However, smallness is not a universal virtue. Safety-critical engineering, regulated services, and large infrastructure projects still require specialized review and broad coordination. The stronger principle is proportionality: keep the discovery team as small as possible while including the expertise needed to make its experiments responsible and informative.
Test customer behavior before polishing the product
Expose assumptions early. A leap-of-faith assumption is a belief that must prove true for a project to succeed, such as whether customers have a problem or will use a proposed feature. The College Scorecard team, building a tool to help students compare colleges, initially assumed users wanted side-by-side comparisons. Instead of spending months programming the feature, the team took cardboard phone mockups to the Washington Mall and watched students use them. No one cared about the comparison function, so the team dropped it before investing heavily.
Build to learn, not to impress. A minimum viable product, or MVP, is an early product or test designed to produce useful evidence with limited time and cost. The team used real behavior, not survey answers alone, to refine its design. The cycle of building, measuring, and learning repeats until evidence supports either continued effort or a change in direction.
Observed behavior can reveal friction that interviews miss, especially when people struggle to predict what they will do in a hypothetical situation. The cardboard prototypes also show that an experiment need not resemble a finished product to be informative. Still, behavior is not self-explanatory. A feature’s apparent failure may reflect poor instructions, an unrepresentative test group, or a prototype that does not convey its value. Good experiments therefore pair observation with careful interpretation, and they test a clear claim rather than treating any customer reaction as a verdict.
Fund learning milestones, not fictional revenue forecasts
Measure what predicts the outcome. Innovation accounting is a way to evaluate progress when familiar measures such as revenue, profit, or market share are still tiny or misleading. It begins with simple measures of customer behavior, then connects those measures to a business case and, when evidence improves, to estimates of future financial value. This lets finance compare projects on evidence instead of on confident but untested forecasts.
Make funding respond to evidence. GE’s Flash Liquid Expander project looked promising on paper, but customer conversations undermined key assumptions about its market. After about seven months and $30,000 of testing, the team stopped rather than spending years and millions developing a product without a viable market. Ries calls staged resource allocation metered funding: teams control an agreed budget, then earn further investment by showing validated learning. A growth board reviews evidence and makes funding decisions.
This approach treats early projects less like miniature mature businesses and more like options whose value depends on what the team learns. A small experiment can be worth financing if it sharply reduces uncertainty about a large possible opportunity. That is more sophisticated than judging a project by early revenue alone. Yet numerical dashboards can create false confidence too. Metrics are proxies, and teams can optimize a proxy while missing the underlying customer need. A growth board therefore needs both transparent measures and informed judgment, with clear criteria for when the evidence is strong enough to scale or stop.
Make transformation earn scale through three deliberate phases
Prove, spread, then redesign. Ries describes organizational change in three phases. First, run a limited set of projects to learn what works locally and build credible examples. Next, scale the practices through training, executive champions, and internal coaches. Finally, use the evidence and organizational support gained to change the deeper systems that keep people returning to old habits, such as budgets, procurement, and performance reviews.
Use crisis without relying on crisis. HealthCare.gov’s 2013 launch failed dramatically: only six people enrolled on the first day. A small team brought contractors and government staff together, focused on urgent issues, and made progress visible. Within weeks, the site’s reliability improved sharply. The rescue was possible partly because early government technology experiments had already built skills and relationships. A crisis can open a door, but preparation determines whether an organization can walk through it.
The phases address a real political problem: asking an organization to change its deepest rules before anyone has demonstrated a workable alternative invites resistance. Early projects create evidence, and evidence can make broader change credible. This is a useful sequencing principle, not a universal timetable. Organizations differ in urgency, authority, and exposure to risk, so phases may overlap or recur. The model also makes a practical point about change: training alone is insufficient. If budgets, incentives, and approval rules still punish experimentation, people will sensibly return to the behavior those systems reward.
Change leaders’ questions from blame to evidence
Hold teams accountable for learning. In uncertain work, a missed forecast may reflect a bad assumption rather than careless execution. Ries recommends that leaders ask what a team learned and what evidence supports that conclusion. Those questions do not remove responsibility. They shift it from defending a predetermined plan to testing whether the plan is moving toward its goal.
Treat failure as a decision point. Amazon’s Fire phone produced a $170 million write-down, but the company kept the team together and moved its people to other projects, including the Echo and Alexa. The failure became useful because the organization had room to absorb the loss and carry learning forward. Teams also need regular pivot-or-persevere reviews: moments to decide whether evidence supports continuing the current strategy or changing course while holding on to the underlying purpose.
The change in questions matters because leaders shape what employees feel safe reporting. If every setback is treated as evidence of incompetence, bad news gets delayed until it is expensive. If learning is valued without scrutiny, however, teams can relabel poor execution as experimentation. The productive middle ground is psychological safety paired with demanding inquiry: people can report unwelcome results, but they must show how the test was designed, what it revealed, and what they propose to do with that knowledge.
Turn legal, HR, and finance from gates into launch systems
Align rules with the work. GE’s old annual performance system measured engineers partly on limiting rework. That incentive made a faster, more experimental design process personally risky, even when the company wanted faster learning. GE tested a replacement approach, Performance Development at GE, based on continuing conversations rather than a single annual rating. In one pilot, 80 percent of participating employees completed a year-end summary, compared with fewer than 2 percent under the old system.
Make constraints usable. A software team feared that legal would block a small customer test. Once the general counsel understood the limited exposure, the test was approved. The legal department later developed a short guide clarifying which experiments teams could run without a special review. Functions such as legal and finance can protect the organization while helping teams act faster, if their processes distinguish small, bounded tests from genuinely high-risk decisions.
The examples show why culture cannot be changed by slogans alone. Performance measures influence behavior even when senior leaders say they want speed and experimentation. Revising the rules can release effort that employees were previously spending on compliance theater or self-protection. This does not make gatekeeping inherently bad. Legal, safety, and financial controls exist because real harms occur. The design challenge is to make the level of review match the level of risk, so low-liability learning is not treated like a full commercial launch.
Treat the company’s own structure as a product to improve
A successful first act is not enough. Ries calls the shift from a successful young company to a durable institution a second founding. At this stage, leaders must build systems that preserve experimentation as the organization grows. Airbnb’s Trips initiative illustrates the effort: after the original lodging product had succeeded, a dedicated team explored a broader travel experience rather than relying only on incremental improvements to the core.
Build the ability to change again. The book’s larger aim is continuous transformation: testing organizational structures and management practices, scaling those that work, and discarding those that do not. The proposed entrepreneurship function supports internal startups, experimental internal systems, corporate development, and organizational change. Its purpose is not to create a permanent innovation department that owns every new idea, but to give the organization responsibility and skills for managing uncertain work wherever it appears.
Treating structure as something that can be tested is a valuable corrective to the belief that an organization’s chart and procedures are fixed facts of nature. It also raises the risk of endless reorganizations, which can consume attention without improving customer outcomes. The book’s insistence on experiments offers a safeguard: organizational change should have a defined hypothesis, limits on disruption, and measures of its effects. A structure deserves to persist not because it is new or fashionable, but because it helps people create value more reliably.
Reduce the safety-net penalties that make entrepreneurship a rich person’s option
Look beyond the founder stereotype. Ries argues that people’s willingness to start businesses depends on their vision, access to skills and resources, and exposure to personal risk. The book cites a RAND finding that U.S. entrepreneurship rates rise when people become eligible for Medicare at age sixty-five, suggesting that health coverage can affect the decision to start a company. It also reports that immigrants founded 44 percent of Silicon Valley startups and 51 percent of billion-dollar startups in the figures it discusses.
Experiment with access. Proposed policies include easier paths for immigrant founders, portable health coverage, startup education, small-business loans, and ways for unemployed people to use support while testing a business idea. These are proposals, not proven universal remedies. The underlying point is that a society cannot expect broad entrepreneurship if the costs of failure are manageable only for people with savings, family support, or unusual credentials.
This argument expands entrepreneurship from a business method into a question of who gets the chance to take risks. The book’s emphasis on limited-liability experiments has a social analogue: policies can make early attempts less financially ruinous without guaranteeing that every attempt succeeds. That distinction matters because support can reduce barriers while still leaving outcomes uncertain. Any policy should be tested for who benefits, who bears the cost, and whether it creates durable opportunity rather than simply subsidizing ventures that would have happened anyway.
Analysis
The Startup Way is best understood as a proposal to extend the management system of startups into established institutions without discarding the strengths of conventional management. Its central diagnosis is that organizations often use forecast-based accountability for two fundamentally different kinds of work. In stable operations, forecasts and standardization can coordinate complex production. In uncertain projects, those same tools reward persuasive estimates, delay contact with customers, and make teams conceal evidence that the plan is wrong.
Ries’s alternative is not unstructured creativity. It is a disciplined learning system: small cross-functional teams test consequential assumptions, record observable changes in customer behavior, and receive additional resources only when evidence warrants them. The practical force of the idea comes from connecting product experimentation to the less glamorous machinery of management: finance, HR, legal review, procurement, executive sponsorship, and promotion. Without those connections, innovation pilots remain isolated and employees bear the career risk of acting differently.
The book’s strongest stories expose how ordinary organizational incentives can produce waste without any individual behaving irrationally. The unused microwave buttons, the five-year engine plan, and the performance system that discouraged rework show how locally sensible decisions can add up to poor outcomes. The response is to assign ownership for discovering whether work creates value, not merely for completing assigned tasks.
The argument has limits. Evidence from successful companies and transformation pilots can show feasibility, but it does not prove that every organization benefits from the same structures or that every promising metric predicts durable returns. Small experiments can mislead when tests are poorly designed, and learning language can be used to excuse weak execution. The most credible version of the method therefore preserves safety standards, uses explicit risk limits, and demands auditable evidence. Its deepest contribution is a managerial question: what kind of uncertainty are people facing, and what system would make truthful progress visible?
Review Summary
The Startup Way received mixed reviews. Many praised its application of Lean Startup principles to large organizations and appreciated the real-world examples, particularly from GE. Readers found value in the entrepreneurial mindset and innovation strategies presented. However, some criticized the book for redundancy, lack of novel ideas, and overemphasis on corporate examples. Critics felt it didn't offer enough practical guidance for smaller startups. Overall, reviewers agreed the book provides useful insights for fostering innovation in established companies, but opinions varied on its relevance and effectiveness across different organizational sizes.
People Also Read
Glossary
The Startup Way
Entrepreneurial management at scaleA management approach that combines reliable execution of established work with experimentation for uncertain opportunities. It treats entrepreneurship as a discipline that organizations can support through small teams, customer tests, evidence-based accountability, and systems for allocating resources. The approach applies across companies, nonprofits, and government, and aims to make continuous innovation and organizational adaptation repeatable.
internal startup
Team for uncertain workA small, dedicated team inside an existing organization that tests a new product, service, business model, or process under substantial uncertainty. It combines the skills needed to build, understand customers, and make commercial decisions. Unlike a conventional project team, it can run experiments and change its strategy while remaining accountable for evidence and contained use of resources.
leap-of-faith assumptions
Critical untested beliefsClaims that must be true for a project’s strategy to succeed, but that have not yet been established by evidence. They may concern customer needs, product features, technology, distribution, or business models. Teams identify and prioritize the riskiest assumptions, then design experiments to learn whether they hold before committing heavily to development or scale.
minimum viable product
Smallest useful learning testAn early product, prototype, or other experiment designed to generate the greatest useful learning about customers while limiting time, effort, and cost. It need not be a polished or fully functioning product. Its purpose is to test important assumptions through real behavior and value exchange, then inform the next experiment or strategic decision.
validated learning
Evidence-based customer learningLearning grounded in observable evidence rather than in a team’s predictions or impressions. It is demonstrated by measuring how customers behave in response to a product or experiment, and by assessing whether behavior changes across tests. Useful measures should clarify cause and effect, be understandable to the people doing the work, and be credible enough to audit.
build-measure-learn feedback loop
Iterative test cycleA repeated process in which a team builds an experiment, measures customer responses, and uses the results to decide what to change or test next. The aim is to shorten the time between an idea and meaningful evidence. Each cycle should connect to a specific assumption and produce a practical next action.
pivot
Strategic change, same visionA significant change in a startup’s strategy while retaining its underlying vision. Evidence from experiments may show that the original product, customer segment, or route to market is unlikely to work. A pivot applies what the team has learned to a revised approach, rather than treating continued commitment to the original plan as proof of discipline.
innovation accounting
Financial evaluation of learningA framework for evaluating progress in projects whose conventional financial measures are initially too small to be useful. It begins with leading indicators of customer behavior, connects them to a business case, and can translate new evidence into estimates of future financial value. It helps teams and finance compare projects using learning and assumptions rather than unsupported forecasts.
metered funding
Evidence-based staged investmentA funding approach that gives a team control over an agreed budget while making further resources conditional on evidence of progress. Funding is released in stages as assumptions are tested and learning improves. Unlike annual project budgets that often continue by default, metered funding is intended to limit downside, focus teams, and make stopping or expanding a project a deliberate decision.
growth board
Internal startup oversight groupA group of leaders that acts as an internal equivalent of a startup board for experimental teams. It reviews evidence, provides strategic guidance, serves as a central accountability point, and makes funding decisions. A growth board is meant to support candid pivot-or-persevere decisions, rather than function as a conventional stage-gate review that judges teams mainly against fixed forecasts.
second founding
Institutional redesign for growthThe stage when an organization must build management systems that can sustain its original innovative capacity as it grows. The work may involve changing incentives, performance evaluation, resource allocation, and functional processes. Ries treats it as a renewed founding effort because leaders must create an institutional structure that supports new opportunities without abandoning the organization’s existing responsibilities.
Golden Sword
Executive obstacle-clearing agreementA way for an experimental team to make a clear offer to senior leaders: the team commits to faster learning, visible progress, and controlled spending, while requesting executive support, secure funding, or cross-functional help. The exchange gives leaders a direct role in removing barriers and helps teams obtain the limited authority and resources needed to test their plans.
FAQ
What's The Startup Way about?
- Entrepreneurial Management Focus: The Startup Way by Eric Ries emphasizes integrating entrepreneurial principles into established organizations to drive innovation and growth.
- Cultural Transformation: It outlines how organizations can shift their culture to embrace experimentation, agility, and a startup mindset.
- Practical Framework: The book provides a structured approach with phases of transformation and tools to measure success, helping organizations thrive amidst uncertainty.
Why should I read The Startup Way?
- Relevance to Modern Businesses: It offers insights into how traditional companies can adapt and innovate in rapidly changing environments.
- Proven Strategies: The book includes real-world examples and case studies from companies like GE and Toyota, showcasing effective application of its principles.
- Actionable Framework: Provides a clear guide for implementing entrepreneurial management practices, aiding leaders and managers in navigating challenges.
What are the key takeaways of The Startup Way?
- Five Key Principles: Continuous Innovation, Startup as Atomic Unit of Work, The Missing Function, The Second Founding, and Continuous Transformation.
- Importance of MVPs: Emphasizes Minimum Viable Products (MVPs) for testing assumptions and gathering validated learning quickly.
- Cultural Shift: Highlights the need for a cultural shift to embrace failure as a learning opportunity, encouraging iteration and pivoting.
What is the Lean Startup method mentioned in The Startup Way?
- Scientific Approach to Innovation: A systematic approach to creating and managing startups, focusing on building a minimum viable product and learning from results.
- Build-Measure-Learn Loop: Involves a continuous cycle of building, measuring, and learning to adapt quickly to market needs.
- Validated Learning: Demonstrates progress through measurable outcomes, allowing informed decisions based on actual data.
What are the phases of transformation in The Startup Way?
- Phase One: Critical Mass: Focuses on building a foundation for change by experimenting and gathering success stories.
- Phase Two: Scaling Up: Successful practices are rolled out across the organization, supported by executive champions and internal coaching.
- Phase Three: Deep Systems: Addresses deeper organizational structures to ensure the entrepreneurial mindset is embedded throughout the company.
What is innovation accounting in The Startup Way?
- Framework for Measurement: Evaluates progress when traditional metrics are not applicable, focusing on leading indicators.
- Three Levels of Innovation Accounting: Includes a simple dashboard, a comprehensive business case, and translating learning into net present value.
- Common Vocabulary: Creates a common language for teams and finance, improving communication and understanding of innovation efforts.
How does The Startup Way define a startup?
- Human Institution: Defined as a human institution designed to create a new product or service under conditions of extreme uncertainty.
- Focus on Uncertainty: Highlights the need for flexibility and adaptability in unpredictable environments.
- Broader Application: Extends beyond traditional startups to include internal projects within established companies.
What role do growth boards play in The Startup Way?
- Accountability Mechanism: Serve as a single point of accountability for internal startups, ensuring teams are responsible for their progress.
- Funding Decisions: Provide metered funding based on validated learning, encouraging experimentation and reducing fear of failure.
- Strategic Guidance: Act as a sounding board for teams, offering strategic insights and support.
What is the significance of the "minimum viable product" (MVP) in The Startup Way?
- Testing Assumptions: Allows teams to test hypotheses with minimal resources, validating or invalidating assumptions quickly.
- Iterative Learning: Focuses on creating a product with just enough features to gather feedback, fostering continuous improvement.
- Foundation for Growth: Lays the groundwork for scaling successful products, emphasizing learning and adaptation over perfection.
How does The Startup Way address the challenges of large organizations?
- Combining Management Styles: Integrates traditional management practices with entrepreneurial methods for efficiency and innovation.
- Empowering Employees: Encourages employees to act like entrepreneurs, contributing ideas and taking initiative.
- Creating a Supportive Environment: Outlines strategies for supporting experimentation and risk-taking by removing bureaucratic obstacles.
What role do leaders play in implementing the principles of The Startup Way?
- Setting the Vision: Articulate a clear vision aligned with the principles of the Startup Way, guiding teams through uncertainty.
- Championing Change: Actively support new methods and practices, overcoming resistance and ensuring successful implementation.
- Fostering a Culture of Learning: Promote a culture that values learning and experimentation, encouraging teams to embrace failure.
What are the best quotes from The Startup Way and what do they mean?
- “Failure is not an option.”: In a startup context, failure is a necessary part of the learning process, leading to greater innovation.
- “I EAT FAILURE FOR BREAKFAST.”: Emphasizes viewing failure as an opportunity to learn and grow, encouraging a culture of innovation.
- “Think big. Start small. Scale fast.”: Advocates for ambitious visions with incremental progress through small experiments, highlighting agility.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.