library / libedb76f612229ed37
The Lean Startup
In a sentence
A scientific, management-driven approach to building startups under extreme uncertainty by maximizing validated learning through rapid Build-Measure-Learn cycles.
The Lean Startup reframes entrepreneurship as a discipline of management rather than a gamble on genius or luck. Drawing on lean manufacturing, agile development, customer development, and design thinking, Eric Ries argues that the core function of any startup—whether in a garage or inside a Fortune 500 company—is to learn how to build a sustainable business under conditions of extreme uncertainty. Through real-world stories from IMVU, Intuit, Dropbox, Zappos, Wealthfront, Votizen, and others, the book shows how to identify leap-of-faith assumptions, test them with a minimum viable product, measure progress with innovation accounting and actionable metrics, and decide whether to pivot or persevere. The result is a repeatable, teachable method that reduces waste, accelerates feedback, and lets companies—large and small—innovate continuously.
The four lenses
- Science
- Statistics
- Systems
- Strategy
Tags
The model
A causal model linking design levers (MVP, small batches, experimentation, innovation accounting) and contextual conditions (extreme uncertainty) to psychological and behavioral states (validated learning, pivot/persevere decisions) and ultimately to outcomes (sustainable growth, reduced waste).
Conditions of Extreme Uncertaintycontextual condition
The defining context of a startup in which the customer, product, and market are unknown, making traditional forecasting and planning unreliable and requiring an experimental approach to discover a sustainable business.
Minimum Viable Product Practicedesign lever
The practice of building the fastest, least costly version of a product that enables a full turn of the Build-Measure-Learn loop to begin the process of validated learning with minimal effort and development time.
Scientific Experimentationdesign lever
The discipline of treating every product, feature, and initiative as a hypothesis-driven experiment with clear predictions tested empirically against real customer behavior to achieve validated learning.
Small Batch Workingdesign lever
Working in small batches and single-piece flow, including continuous deployment, to accelerate the Build-Measure-Learn feedback loop, surface defects sooner, and reduce work-in-progress inventory.
Innovation Accountingdesign lever
A disciplined quantitative system using actionable metrics, cohort analysis, and learning milestones to establish a baseline, tune the engine, and objectively decide whether a startup is making progress toward a sustainable business.
Adaptive Organization Practicesdesign lever
Organizational practices such as the Five Whys and proportional investment that automatically adjust process and performance to current conditions, regulating speed and building in quality without bureaucracy.
Validated Learningpsychological state
The process of empirically demonstrating that a team has discovered valuable truths about a startup's present and future business prospects, evidenced by positive improvements in actionable core metrics rather than after-the-fact rationalization.
Pivot or Persevere Decision Qualitybehavioral pattern
The behavioral practice of making a clear-eyed, data-grounded structured decision to either change a fundamental strategic hypothesis (pivot) or stay the course (persevere) based on actionable metrics and validated learning.
Engine of Growthbehavioral pattern
The mechanism (sticky, viral, or paid) by which a startup achieves sustainable growth, where new customers come from the actions of past customers, providing a focused set of metrics to drive prioritization and acceleration.
Sustainable Business Outcomeoutcome metric
The ultimate outcome of building a thriving, world-changing business with a working engine of growth, validated value, and the capacity for continuous innovation while minimizing the waste of time, money, and human potential.
How they connect
- minimum viable product → predicts validated learning
- experimentation → predicts validated learning
- small batches → influences validated learning
- innovation accounting → predicts validated learning
- validated learning → predicts pivot persevere decision
- innovation accounting → predicts pivot persevere decision
- pivot persevere decision → influences engine of growth
- engine of growth → predicts sustainable business
- validated learning → mediates sustainable business
- adaptive organization → influences sustainable business
- extreme uncertainty → moderates validated learning
The process
The book's overall operating playbook centers on the Build-Measure-Learn feedback loop, a continuous cycle designed to reduce uncertainty and waste in product development. The core idea is to treat a startup as a series of experiments to test fundamental business hypotheses. This begins with identifying assumptions and building a Minimum Viable Product (MVP) to test them. The results are then measured using actionable, not vanity, metrics, leading to validated learning about what customers truly want. This learning culminates in a critical decision: pivot to a new strategy or persevere with the current one. Supporting this core loop are several key processes. To enable rapid iteration, the playbook advocates for small-batch production, continuous deployment, and workflow management systems like Kanban that prioritize validated learning over just shipping features. When problems inevitably arise, the Five Whys technique provides a framework for root cause analysis, fostering a culture of improvement rather than blame. Once a product finds its footing, the focus shifts to sustainable growth by identifying and optimizing a specific 'engine of growth'—be it sticky, viral, or paid. Finally, the playbook addresses the organizational structures and culture required to sustain this methodology. It details how to build adaptive organizations, structure internal innovation teams within larger companies using 'sandboxes', and foster a quality-first mindset. The entire system is designed to help entrepreneurs navigate the extreme uncertainty of innovation by grounding their decisions in empirical customer data rather than intuition alone.
Build-Measure-Learn Feedback Loop
To create a continuous cycle of product development that turns ideas into products, measures how customers respond, and then learns whether to pivot or persevere, minimizing wasted time and resources.
When to use: Continuously from the inception of a product idea through its entire lifecycle to guide development and strategy.
Step 1Define leap-of-faith assumptions and build a Minimum Viable Product (MVP) to test them.
Entry: A clear hypothesis or set of assumptions about the customer problem and proposed solution.
Exit: An MVP is released to a segment of customers.
In: Product ideas, Leap-of-faith assumptions · Out: Minimum Viable Product (MVP)
ch01 · ch06p01 · ch06p02
Step 2Measure customer interaction with the MVP to collect real, quantitative and qualitative data.
Entry: The MVP is live and accessible to customers.
Exit: Sufficient data has been collected to evaluate the initial hypothesis.
In: MVP, Customer feedback channels · Out: Customer behavior data, Performance metrics
ch01 · ch06p01 · ch06p02 · ch07
Step 3Analyze the data to generate validated learning about what customers want and whether the core hypotheses are true.
Entry: Raw data from the measurement phase is available.
Exit: The team has clear insights on whether the hypothesis was validated or invalidated.
In: Customer behavior data, Performance metrics · Out: Validated learnings, Insights on customer preferences
ch01 · ch06p01 · ch06p02
Step 4Decide whether to pivot (make a structured course correction) or persevere (continue on the current path).
Entry: Validated learning has been generated from the analysis phase.
Exit: A clear strategic decision is made and a new set of hypotheses is formulated for the next loop.
- Pivot or Persevere
In: Validated learnings · Out: Refined product strategy, Decision to pivot or persevere
ch01 · ch06p01 · ch06p02 · ch07
Implement Actionable Metrics
To accurately measure the impact of product changes and gain clear insights into customer behavior by moving away from misleading vanity metrics.
When to use: During the 'Measure' phase of the Build-Measure-Learn loop to ensure data quality and relevance.
Step 1Identify and discard vanity metrics that do not show clear cause-and-effect relationships.
Entry: The team is currently using gross or aggregate metrics to measure success.
Exit: A list of problematic metrics is identified.
In: Current metrics reports · Out: List of identified vanity metrics
ch06p03
Step 2Implement cohort-based metrics to analyze the behavior of specific groups of customers over time.
Entry: The need for deeper, more accurate customer behavior insights is recognized.
Exit: The analytics system is configured to report on customer cohorts.
In: Customer usage data · Out: Cohort analysis reports
ch06p03
Step 3Use split-test (A/B test) experiments to test the impact of new features or changes.
Entry: A new feature or change is ready for release.
Exit: Statistically significant data is collected on the performance of the product variation.
In: Product variations · Out: Split-test results, Validated feature impact
ch06p03 · ch07
Pivot or Persevere Decision-Making
To provide a formal structure for deciding whether to make a significant change in strategy (pivot) or continue with the current approach (persevere) based on validated learning.
When to use: At the end of one or more Build-Measure-Learn cycles, when enough data has been gathered to question a fundamental business hypothesis.
Step 1Schedule regular 'pivot or persevere' meetings with key stakeholders.
Entry: A predefined milestone or time interval has been reached.
Exit: The meeting is scheduled and attendees are confirmed.
Out: Scheduled meeting
ch07
Step 2Compile and present a comprehensive report of product optimization results and customer feedback.
Entry: Data from recent experiments and customer interactions is available.
Exit: All relevant data and insights are presented to the decision-making group.
In: Product performance metrics, Customer feedback reports, Split-test results · Out: Comprehensive performance report
ch07 · ch06p01
Step 3Analyze the data collectively to understand trends and compare results against expectations.
Entry: The performance report has been presented.
Exit: The team has a shared understanding of the current situation.
In: Comprehensive performance report · Out: Shared analysis of business progress
ch07
Step 4Decide to either pivot or persevere.
Entry: The team has analyzed the data and discussed its implications.
Exit: A clear, documented decision is made to either change strategy or continue the current one.
- Pivot or Persevere
In: Shared analysis of business progress · Out: Strategic decision (pivot or persevere)
ch07 · ch06p01
Implement Small Batch Workflow
To increase efficiency, improve quality, and accelerate learning by working in small, complete batches rather than large, sequential ones.
When to use: As the primary method for organizing and executing work within the 'Build' phase of the feedback loop.
Step 1Break down large work items into the smallest possible batches that still deliver value.
Entry: A large batch of work is planned.
Exit: The work is re-scoped into a series of small batches.
In: Product backlog, Large work items · Out: Prioritized list of small work batches
ch08
Step 2Process each small batch through the entire workflow from start to finish before starting the next batch (single-piece flow).
Entry: A small batch of work is ready to be started.
Exit: The small batch is fully completed and delivered.
In: A single small work batch · Out: A completed, value-delivering increment
ch08
Step 3Identify and fix any defects or problems immediately as they are discovered within a batch.
Entry: A defect is found during the processing of a batch.
Exit: The defect is resolved and the batch is completed correctly.
In: Defect report · Out: Resolved defect
ch08
Step 4Continuously work to reduce the setup or changeover time between batches.
Entry: The team is practicing single-piece flow.
Exit: Changeover time between batches is measurably reduced.
In: Process analysis data · Out: Streamlined changeover process
ch08
Continuous Deployment and Quality Control
To enable rapid product updates and learning by deploying changes frequently and safely, with automated systems to protect quality.
When to use: As the technical foundation for the 'Build' phase, enabling the rapid release of small batches.
Step 1Implement an automated deployment pipeline to release code to production quickly and reliably.
Entry: Code changes are managed in a version control system.
Exit: A new feature can be deployed to production with minimal manual intervention.
In: Completed code for a new feature · Out: Deployed feature
ch08
Step 2Empower teams to halt the production line (an 'Andon cord' pull) if a quality issue is detected.
Entry: A quality issue is identified in development or production.
Exit: Work stops until the root cause of the issue is investigated and addressed.
In: Quality metric threshold breach · Out: Workflow halt
ch10
Step 3Develop an automated 'immune system' to monitor product changes and their impact on key metrics.
Entry: A continuous deployment pipeline is in place.
Exit: A monitoring system is live that can automatically roll back defective changes.
In: Deployed changes, Live performance data · Out: Automatic rollback of faulty changes, Team notification
ch08
Kanban for Validated Learning
To manage product development workflow with a focus on validating that features deliver real customer value, not just on completing tasks.
When to use: To manage the flow of work from idea to validated feature.
Step 1Categorize user stories into four states: backlog, in progress, done, and validated.
Entry: A backlog of user stories or feature ideas exists.
Exit: A Kanban board is set up with these four states.
In: User stories · Out: Kanban board
ch06p03
Step 2Define a clear validation criterion for each story.
Entry: A user story is being planned.
Exit: The story has an explicit, measurable validation criterion.
In: User story · Out: Validation criterion
ch06p03
Step 3Limit the number of stories in each state (Work-In-Progress limits).
Entry: The Kanban board is in use.
Exit: WIP limits are established for the 'in progress' and 'done' states.
Out: WIP limits
ch06p03
Step 4Ensure stories are validated through customer feedback or experiments before being considered complete.
Entry: A story is in the 'done' (i.e., technically complete) state.
Exit: The story is moved to 'validated' based on evidence, or the learning is captured and the feature is potentially removed.
In: Completed feature, Customer behavior data · Out: Validated feature
ch06p03
Five Whys Root Cause Analysis
To systematically identify the root cause of a problem, rather than just addressing its symptoms, and develop effective long-term solutions.
When to use: Whenever a problem or unexpected failure occurs that warrants investigation.
Step 1Identify and clearly state the specific problem or symptom.
Entry: A problem has occurred.
Exit: A clear, agreed-upon problem statement is formulated.
In: Problem report, Customer complaint · Out: Problem statement
ch10
Step 2Ask 'Why?' the problem occurred and write down the answer.
Entry: The problem statement is defined.
Exit: The first-level cause is identified.
In: Problem statement · Out: First 'Why' answer
ch10
Step 3Continue asking 'Why?' for each successive answer until the root cause is identified.
Entry: A causal chain is being established.
Exit: The team agrees that the root cause has been found and asking 'Why?' further yields no new insights.
In: Previous 'Why' answer · Out: Root cause identification
ch10
Step 4Develop and implement countermeasures to address the root cause.
Entry: The root cause is identified.
Exit: Action items are assigned and a plan for implementation is in place.
In: Root cause identification · Out: Actionable improvement plan
ch10
Activate an Engine of Growth
To achieve sustainable, long-term growth by identifying and optimizing the specific mechanism through which the startup acquires and retains customers.
When to use: After the initial Build-Measure-Learn loops have validated the core product and business model.
Step 1Analyze customer behavior to determine which engine of growth is naturally at work.
Entry: The product has an initial set of engaged customers.
Exit: The primary engine of growth is identified.
- Choose which engine of growth to focus on.
In: Customer behavior data, Acquisition channel data · Out: Identified primary engine of growth
ch09
Step 2Define and track the key actionable metrics for the chosen engine.
Entry: The primary engine of growth has been identified.
Exit: A dashboard with the key metrics for the chosen engine is established.
In: Identified primary engine of growth · Out: Key performance indicators (KPIs) for growth
ch09
Step 3Focus all product development and marketing efforts on optimizing the metrics for the chosen engine.
Entry: The growth engine and its KPIs are defined.
Exit: Product and marketing roadmaps are aligned with optimizing the engine of growth.
In: Key performance indicators (KPIs) for growth · Out: Optimized growth engine, Sustainable growth
ch09
Structure Internal Innovation Teams
To create a protected space and organizational structure within an established company that enables internal teams to pursue disruptive innovation using Lean Startup methods.
When to use: When an established company wants to launch a new, potentially disruptive product or business line.
Step 1Create an 'innovation sandbox' with clear boundaries for experimentation.
Entry: A strategic decision is made to invest in a new innovation project.
Exit: The rules and boundaries of the innovation sandbox are defined and approved.
In: Innovation project charter · Out: Innovation sandbox definition
ch11
Step 2Assemble a cross-functional team with a dedicated leader.
Entry: The innovation sandbox is defined.
Exit: A fully cross-functional team is formed and dedicated to the project.
In: Project requirements · Out: Dedicated internal startup team
ch11
Step 3Provide scarce but secure resources and grant the team independent authority.
Entry: The team is formed.
Exit: The team has an approved budget and documented authority to operate.
In: Team charter · Out: Secure budget, Delegated authority
ch11
Step 4Establish a standard set of actionable metrics for all experiments within the sandbox.
Entry: The team is ready to begin experimenting.
Exit: A standard set of 5-10 actionable metrics is defined and adopted.
Out: Standardized innovation metrics
ch11
Develop an Adaptive Organization
To create a system that automatically adjusts its processes and training based on the problems it encounters, enabling it to scale without becoming bureaucratic.
When to use: As a startup grows and needs to formalize processes like onboarding and training.
Step 1Use the Five Whys to identify systemic issues that require new processes or training.
Entry: A Five Whys analysis has identified a process or training gap as a root cause.
Exit: A need for a new process or training module is identified.
In: Five Whys root cause analysis · Out: Identified need for adaptation
ch10
Step 2Develop training programs and processes organically and incrementally.
Entry: A need for a new process or training is identified.
Exit: An initial, simple version of the process or training is implemented.
In: Identified need for adaptation · Out: New training module or process
ch10
Step 3Periodically review and experiment with the effectiveness of training and processes.
Entry: A process or training program has been in place for a period of time.
Exit: The effectiveness of the process is measured and insights for improvement are generated.
In: Team performance data, Feedback from employees · Out: Validated learning about internal processes
ch10
Engage with the Lean Startup Community
To connect with other entrepreneurs to share ideas, gain support, and accelerate learning by tapping into a broader network of practitioners.
When to use: Throughout the entrepreneurial journey to combat isolation and access external knowledge and support.
Step 1Find and join a local Lean Startup Meetup group.
Entry: A desire to connect with local peers.
Exit: Attendance at a local meetup event.
In: Internet access · Out: Connection with local entrepreneurs
ch13
Step 2Participate in online communities like the Lean Startup Circle.
Entry: A need for real-time advice or broader perspectives.
Exit: Active participation in an online discussion.
In: Internet access · Out: Access to a global community and resources
ch13
Step 3Attend conferences and workshops on the topic.
Entry: A goal to deepen understanding of the methodology.
Exit: Attendance at a conference or workshop.
In: Conference registration · Out: Enhanced knowledge, New professional connections
ch13
Step 4Utilize official online resources like websites, blogs, and case studies.
Entry: A need for specific information or inspiration.
Exit: Relevant learning materials are found and consumed.
In: Internet access · Out: Curated resources and learning materials
ch13
A candidate measure
The Lean Startup — derived measurement candidates
Conditions of Extreme Uncertainty
forecast error rate; market novelty index; operating history length
self-report suitability: medium
Minimum Viable Product Practice
time to first release; build cost; feature count
self-report suitability: high
Scientific Experimentation
experiments per period; split-test count; hypothesis documentation rate
self-report suitability: high
Small Batch Working
deployment frequency; batch size; cycle time
self-report suitability: medium
Innovation Accounting
actionable metric reports; cohort conversion rates; milestone achievement
self-report suitability: medium
Adaptive Organization Practices
root cause sessions held; prevention investments made; defect recurrence rate
self-report suitability: medium
Validated Learning
cohort conversion change; split-test deltas; retention shifts
self-report suitability: low
Pivot or Persevere Decision Quality
pivots per runway; time-to-pivot; decision data basis
self-report suitability: medium
Engine of Growth
churn rate; viral coefficient; LTV; CPA
self-report suitability: low
Sustainable Business Outcome
revenue; compounding growth rate; retention rate
self-report suitability: low
The story
The reader An entrepreneur or innovator—inside a startup or a large company—who wants to build a successful, sustainable, world-changing business.
External problem
Most startups and new products fail despite hard work, good ideas, and talented teams.
Internal problem
They feel anxious, uncertain, and afraid that their vision will fail without ever getting a fair test.
Philosophical problem
It's wrong to waste people's time, passion, and creativity building products nobody wants.
The plan
- Identify your leap-of-faith assumptions (value and growth hypotheses).
- Build a minimum viable product to begin learning fast.
- Measure progress with innovation accounting and actionable metrics.
- Decide to pivot or persevere based on the data.
- Accelerate through the Build-Measure-Learn loop using small batches and adaptive processes.
Success
- You build a sustainable business that customers want.
- You innovate continuously, even at scale.
- You reduce waste and make confident, data-driven decisions.
- You hold yourself and your team accountable through validated learning.
At stake
- You waste enormous time and resources building products nobody wants.
- You get stuck in the land of the living dead, neither growing nor dying.
- Your venture fails after faithfully executing a flawed plan.
- Your creativity and potential are squandered.
Chapter by chapter
ch01Start
In this chapter, Eric Ries lays the foundation for the Lean Startup methodology, emphasizing the importance of validated learning and iterative product development to swiftly discover what truly resonates with customers.
- The time spent on research, planning, and forecasting should be replaced by learning through direct customer interactions.
- Every startup is a scientific experiment that must be grounded in real-world data.
- Validating learning is the key principle that allows entrepreneurs to pivot or persevere.
- Embracing uncertainty is not a sign of weakness; it is a strategic advantage in the modern startup landscape.
ch02Define
Entrepreneurs are not only those starting ventures in garages but also managers within established companies who must navigate internal complexities to drive innovation amidst uncertainty.
- Entrepreneurship is not confined to startups; established companies must embrace the same principles to thrive.
- A successful startup is defined as a human institution that innovatively operates under high uncertainty.
- The Lean Startup methodology is critical for both nascent ventures and established corporations looking to innovate effectively.
- Innovation thrives when organizations create empowered teams facilitated by leaders who understand and support entrepreneurial processes.
ch03Learn
In the realm of entrepreneurship, learning is not merely an afterthought but a rigorous discipline that facilitates the progress of startups amidst extreme uncertainty, as illustrated by the transformative journey of IMVU.
- Learning is the essential unit of progress for startups, transcending traditional metrics of success.
- Validated learning requires rigorous empirical analysis that continuously informs product direction and strategy.
- Early engagement with potential customers can unveil critical insights about their needs that market research might miss.
- Accepting and understanding failure is crucial for navigating the unpredictability of startup dynamics.
ch04Experiment
In this chapter, the author emphasizes the necessity of viewing startup efforts as experiments, rooted in the scientific method, to derive substantial insights and foster sustainable business practices.
ch05Leap
This chapter examines how startups navigate critical assumptions through empirical testing, using Facebook's early growth as a case study, and emphasizes the importance of validating value and growth hypotheses.
ch06Test
Entrepreneurs are often misled by traditional notions of product development, needing instead to adopt a Minimum Viable Product (MVP) approach that emphasizes rapid learning and iteration through customer feedback.
- The Minimum Viable Product isn’t about being 'the best' but about proving foundational ideas with as little effort as necessary.
- Early adopters thrive on partial solutions; their feedback is critical to developing mainstream products.
- Quality in startups is not predefined; it emerges through iterative processes driven by customer engagement.
- Innovation requires a willingness to embrace imperfection—historically, many successful products started as low-quality iterations.
ch06p01Pivot (or Persevere) (part 1/3)
The chapter addresses the pivotal decision every entrepreneur faces: whether to pivot—change direction—or persevere with their current strategy when confronted with failure and uncertainty in their ventures.
- Most startups fail, not because their founders lack talent, but because entrepreneurs do not rigorously validate their assumptions.
- The Lean Startup methodology encourages learning through experimentation, creating a feedback loop that guides product development.
- Successful innovation requires a pivoting mindset coupled with a commitment to understanding customer behavior rather than relying on what they say.
- Entrepreneurship is a disciplined practice that can be taught, significantly shifting the narrative from a talent-centric view to a process-driven one.
ch06p02Pivot (or Persevere) (part 2/3)
This chapter explores the importance of experimentation in startup success, advocating for a shift from reliance on overly detailed plans to a flexible, iterative approach based on real customer feedback.
- Startups must prioritize experimentation over exhaustive planning to adapt to changing market dynamics.
- The iterative process of developing a minimum viable product allows for rapid feedback and adjustment, essential for survival.
- Embracing validated learning helps differentiate between vanity metrics and actionable data that guides smart business decisions.
- Continuous feedback loops enable startups to pivot quickly and responsively, positioning them better for long-term success.
ch06p03Pivot (or Persevere) (part 3/3)
The chapter interrogates the critical decision-making process of when to pivot versus when to persevere in a startup's development, emphasizing the necessity of actionable metrics and continuous customer feedback.
- Effective decision-making in startups hinges on moving beyond vanity metrics to actionable, clear performance indicators.
- The introduction of split-testing can drastically alter your understanding of what features truly benefit customers.
- A disciplined approach to metrics can empower teams, leading to more meaningful insights and stronger validation of product decisions.
- The kanban system promotes accountability and facilitates real learning throughout the product development process.
ch07Pivot (or Persevere)
Entrepreneurs constantly grapple with the vital decision of whether to pivot their business model or persevere with their current strategy, heavily relying on evidence and judgment to guide their choice.
- The decision to pivot or persevere must be based on clear, actionable metrics rather than hope or partial success.
- Successful entrepreneurs learn to embrace the necessity of pivots, viewing them as essential learning milestones rather than failures.
- Failing to pivot at the right moment can lead to stagnation, draining resources while offering no path to substantial growth.
- Structured meetings focused on critical metrics can facilitate informed decision-making in startups.
ch08Batch
This chapter explores the concept of batch size in work processes, demonstrating how smaller batches can enhance efficiency, reduce waste, and facilitate faster learning, particularly in startup environments.
ch09Grow
Startups often reach a plateau in growth despite early success, and understanding the right engine of growth is critical for sustainable development.
- Sustainable growth comes from a deep understanding of customer mechanics and retention rather than just acquisition.
- Every business must identify its particular engine of growth, whether sticky, viral, or paid, to navigate growth challenges effectively.
- Customer retention should be prioritized, as the balance of new customer acquisition and churn rates determines growth velocity.
- Metrics must be aligned with actual customer interactions to provide meaningful insights into growth strategy efficacy.
ch10Adapt
In a rapidly evolving business landscape, startups must not only embrace growth but also develop adaptive processes to maintain effectiveness, balancing speed with quality and learning.
ch11Innovate
This chapter argues that large organizations can recapture the spirit of innovation through a structured approach to internal startups that balances resource management with entrepreneurial autonomy.
- Organizations can counteract the stifling effects of scale with a dedicated approach to fostering innovation, termed "portfolio thinking."
- Effective internal startup teams require secure resources, independent authority, and personal investment—incentives that should be aligned with long-term success.
- Creating an "innovation sandbox" allows companies to innovate openly while addressing internal fears and protecting relationships with existing clients.
- Recognizing and managing the lifecycle of different innovations is key to maintaining a competitive edge and sustaining growth.
ch12Epilogue: Waste Not
In this chapter, the author reflects on the legacy of scientific management, critiques modern efficiency practices, and advocates for a shift towards understanding and eliminating waste in innovation.
ch13Join the Movement
The Lean Startup movement has expanded globally, fostering a rich network of resources and communities that empower entrepreneurs to innovate and connect without needing to reside in traditional startup hubs.
ch14Join the Movement
The chapter emphasizes the importance of local startup ecosystems and outlines key resources available for aspiring entrepreneurs looking to engage with the Lean Startup movement.
Questions this book answers
- How can entrepreneurs systematically reduce the failure rate of new innovative products?
- What is the right unit of progress for a startup operating under extreme uncertainty?
- How do you decide whether to pivot or persevere?
- How can large established companies foster disruptive innovation internally?
- How do you measure progress when traditional milestones and accounting don't apply?
Glossary
- Conditions of Extreme Uncertainty
- The unpredictable context in which startups operate where customer, product, and market are unknown.
- Minimum Viable Product Practice
- Building the simplest product version that enables a full Build-Measure-Learn loop.
- Scientific Experimentation
- Treating startup activities as hypothesis-driven experiments tested empirically.
- Small Batch Working
- Working in small batches and single-piece flow to accelerate feedback.
- Innovation Accounting
- A quantitative system of actionable metrics and learning milestones for accountability.
- Adaptive Organization Practices
- Practices that adjust process and performance to conditions automatically.
- Validated Learning
- Empirically demonstrated discovery of valuable truths about business prospects.
- Pivot or Persevere Decision Quality
- The quality of structured strategic course-correction decisions.
Related in the library
Tools these methods power