Method: Lean Startup

← Playbook overview

Strategy-Led Innovation Playbook · Method

Lean Startup

Table of Contents
    Agregue un encabezado para comenzar a generar la tabla de contenido.
    Scroll to Top

    What is the Lean Startup Method?

    Validated learning, the scientific method, and experimentation are at the core of the Lean Startup method. It is a disciplined way to reduce the uncertainty in a business model: name what must be true, test it quickly with real customers, and let the results decide the next move. It focuses on identifying a problem; identifying the riskiest assumptions about the problem and the solution; building experiments around the assumptions; measuring the results from the experiments; and making a decision based on those results.

    Steve Blank defines Lean Startup as having three components:

    1. Business Model Design
    2. Customer Development
    3. Agile Engineering

    The playbook uses these three components across its phases. Business Model Design and Customer Development are covered in Discovery; Agile Engineering is covered in Incubation and Commercialization.

    The Lean Startup method is not “new.” It is based on the work of several thought leaders in industry and academia going back to Steve Blank’s original book on Customer Development in 2003.

    “Experiments are the means to reduce the risk and uncertainty of your business idea.” (David J. Bland and Alexander Osterwalder, Testing Business Ideas)

    The Experiment is the First Product

    “The Lean Startup methodology has as a premise that every startup is a grand experiment that attempts to answer a question. The question is not ‘Can this product be built?’ Instead, the questions are ‘Should this product be built?’ and ‘Can we build a sustainable business around this set of products and services?’ This experiment is more than just theoretical inquiry; it is a first product. If it is successful, it allows a manager to get started with: enlisting early adopters, adding employees to each further experiment or iteration, and eventually starting to build a product. By the time that product is ready to be distributed widely, it will already have established customers.” (Source: Eric Ries)

    Lean Startup turns a business idea into a set of testable bets, and settles each one with evidence instead of opinion.

    The Core Process: From Build-Measure-Learn to Hypothesize-Design-Test-Learn

    Lean Startup emphasizes the Build, Measure, Learn process based on validated learning. However, Dan Olsen’s Lean Product Playbook further modifies this to Hypothesize, Design, Test, Learn, since you really begin with hypotheses, and the term “Build” implies building a product, which doesn’t happen until later.

    What is Validated Learning?

    Validated learning enables you to test (de-risk) the desirability, viability, and feasibility of your product or idea prior to building and launching it. The validated learning curve shows that the more you test your assumptions, the more you learn, and the higher fidelity prototype you will develop.

    1. Practical Implementation Framework

    Identifying and Prioritizing Risky Assumptions

    The Assumption Mapping Process:

    1. List All Assumptions: Document every assumption about customers, problems, solutions, market, channels, and business model

    2. Categorize by Risk Level:

      • High Risk/High Impact: Test first priority
      • High Risk/Low Impact: Test second priority
      • Low Risk/High Impact: Test third priority
      • Low Risk/Low Impact: Test last or assume true

    3. Apply the ICE Framework:

      • Impact: How much will this assumption affect success? (1-10)
      • Confidence: How sure are you this assumption is true? (1-10)
      • Ease: How easy is it to test? (1-10)
      • Priority Score = (Impact × Confidence) ÷ Ease

    Step-by-Step Experiment Design Process

    The HEART Framework for Experiments:

    1. Hypothesis: Clear, testable statement

      • Format: “We believe that [assumption] because [reason]. We will know we’re right when [measurable outcome]”

    2. Experiment Design: Choose appropriate test method

    3. Audience: Define target participants

    4. Resources: Determine time, budget, and tools needed

    5. Timeline: Set start/end dates and milestones

    Experiment Canvas Template:

    • Assumption to Test: What belief are you testing?
    • Hypothesis: If/then statement
    • Success Metrics: How will you measure success?
    • Method: What type of experiment will you run?
    • Duration: How long will the test run?
    • Resources Required: People, budget, tools
    • Risks/Assumptions: What could go wrong?

    2. Common Methodologies and Experiment Types

    MVP (Minimum Viable Product) Types

    1. Concierge MVP

    • Manually deliver the service to early customers
    • Best for: Service-based businesses, complex processes
    • Example: Food delivery service where founder personally delivers orders

    2. Wizard of Oz MVP

    • Front-end appears automated, but humans power the backend
    • Best for: Testing demand for automated solutions
    • Example: Chatbot interface with human operators responding

    3. Landing Page MVP

    • Single webpage describing the product with signup/purchase option
    • Best for: Testing market demand and value proposition
    • Metrics: Conversion rates, email signups, pre-orders

    4. Prototype MVP

    • Basic functional version with core features only
    • Best for: Software products, apps
    • Focus: Core user journey and primary value proposition

    Specific Testing Methods

    A/B Testing Framework:

    1. Define Hypothesis: What you want to test
    2. Create Variants: A (control) vs B (test)
    3. Split Traffic: Random assignment to groups
    4. Set Sample Size: Statistical significance calculator
    5. Run Duration: Until statistical significance achieved
    6. Analyze Results: Statistical significance and practical impact

    Landing Page Test Design:

    • Headline Testing: Value proposition clarity
    • CTA Button Testing: Color, text, placement
    • Feature Emphasis: Which features to highlight
    • Pricing Strategy: Different price points or models

    Smoke Tests:

    • Fake Door Test: Button/feature that doesn’t work yet
    • Pre-order Campaign: Take real pre-orders or deposits. A pre-order is a payment, so it shows willingness to pay.
    • Coming Soon Page: Measure signup interest

    Customer Interview Framework:

    1. Pre-Interview: Research participant background
    2. Opening: Set context, build rapport (5 minutes)
    3. Problem Discovery: Understand current challenges (15 minutes)
    4. Solution Testing: Present concept, get feedback (15 minutes)
    5. Wrap-up: Next steps, follow-up permission (5 minutes)

    Interview Question Types:

    • Open-ended: “Tell me about the last time you…”
    • Behavioral: “How do you currently handle…”
    • Hypothetical: “If there was a solution that…”
    • Ranking: “Prioritize these features by importance…”

    3. Measurement Techniques and Metrics

    Actionable vs. Vanity Metrics

    Actionable Metrics (focus on these):

    • Customer Acquisition Cost (CAC)
    • Lifetime Value (LTV)
    • Monthly Recurring Revenue (MRR)
    • Net Promoter Score (NPS), supporting evidence only
    • Product-Market Fit Score (Sean Ellis survey), supporting evidence only
    • Conversion rates by funnel stage

    Vanity Metrics (avoid obsessing over):

    • Total users/downloads
    • Page views
    • Social media followers
    • Press mentions

    The AARRR Metrics Framework (Pirate Metrics)

    Acquisition: How do users find you?

    • Traffic sources
    • Cost per acquisition
    • Conversion rate from visitor to user

    Activation: Do users have a great first experience?

    • Time to first value
    • Onboarding completion rates
    • Feature adoption rates

    Retention: Do users come back?

    • Daily/Monthly Active Users (DAU/MAU)
    • Cohort retention rates
    • Churn rates

    Revenue: How do you monetize?

    • Revenue per user
    • Conversion to paid
    • Average order value

    Referral: Do users tell others?

    • Viral coefficient
    • Net Promoter Score
    • Referral rates

    Decision-Making Frameworks

    The Three Outcomes Framework:

    1. Proceed: Strong validation, continue building
    2. Pivot: Some validation but major changes needed
    3. Stop: No validation, abandon or completely restart

    Pivot Decision Criteria:

    • Customer Feedback: Consistent negative feedback on core value proposition
    • Usage Metrics: Low engagement or high churn
    • Market Response: Poor market traction despite multiple iterations
    • Team Learning: Discovered better opportunities

    4. Common Failure Points and Troubleshooting

    Typical Pitfalls in Experiment Design

    1. Confirmation Bias

    • Problem: Designing experiments to confirm existing beliefs
    • Solution: Actively seek disconfirming evidence

    2. Testing Too Many Variables

    • Problem: Cannot determine which change caused results
    • Solution: Test one variable at a time

    3. Insufficient Sample Size

    • Problem: Results not statistically significant
    • Solution: Use sample size calculators, run longer tests

    4. Short Test Duration

    • Problem: Missing seasonal or cyclical effects
    • Solution: Run tests for full business cycles when possible

    Handling Inconclusive Results

    When Results Are Mixed:

    1. Segment the Data: Look for patterns in user groups
    2. Extend the Test: Run longer for more data
    3. Refine the Hypothesis: Make it more specific
    4. Try Different Methods: Switch experiment type

    When You Can’t Get Clear Signal:

    1. Increase Effect Size: Make changes more dramatic
    2. Improve Measurement: Better tracking and metrics
    3. Change Sample: Test with different user groups
    4. Simplify the Test: Focus on single, clear outcome

    5. Industry-Specific Applications

    B2B vs B2C Differences

    B2B Considerations:

    • Longer Sales Cycles: Experiments may take months
    • Smaller Sample Sizes: Fewer potential customers
    • Complex Decision Making: Multiple stakeholders
    • Higher Touch Sales: Personal relationships matter more
    • Focus Areas: Problem validation, solution fit, pricing models

    B2C Considerations:

    • Faster Feedback Loops: Quick user reactions
    • Larger Sample Sizes: More potential customers
    • Emotional Decision Making: Feelings drive purchases
    • Viral Potential: Word-of-mouth and social sharing
    • Focus Areas: User experience, viral mechanics, pricing psychology

    Software vs Physical Product Adaptations

    Software Products:

    • Rapid Iteration: Updates can be deployed quickly
    • A/B Testing: Easy to test different versions
    • Analytics: Detailed user behavior tracking
    • Low Marginal Cost: Adding users costs little

    Physical Products:

    • Prototyping Costs: Physical prototypes are expensive
    • Manufacturing Lead Times: Changes take longer
    • Inventory Risk: Overproduction risk
    • Testing Methods: Focus on 3D models, renderings, pre-orders

    Service-Based Business Applications

    Service Adaptations:

    • Concierge MVP: Manually deliver service first
    • Process Documentation: Map out service delivery
    • Quality Metrics: Satisfaction scores, completion rates
    • Scaling Challenges: Human resources constraints

    6. Integration with Other Frameworks

    Design Thinking Integration

    Double Diamond + Lean Startup:

    1. Discover (Design) + Problem Validation (Lean)
    2. Define (Design) + Solution Hypotheses (Lean)
    3. Develop (Design) + MVP Building (Lean)
    4. Deliver (Design) + Market Testing (Lean)

    Business Model Canvas Integration

    Testing Canvas Components:

    • Value Propositions: Landing page tests, interviews
    • Customer Segments: User research, segmentation analysis
    • Revenue Streams: Pricing experiments, payment tests
    • Channels: Channel effectiveness tests
    • Key Partnerships: Partnership pilot programs

    Agile Development Integration

    Sprint Planning with Experiments:

    • Story Points: Include experimentation effort
    • Definition of Done: Include learning objectives
    • Sprint Reviews: Present experiment results
    • Retrospectives: Discuss learning process improvements

    OKRs (Objectives and Key Results) Integration

    Learning-Focused OKRs:

    • Objective: Validate product-market fit
    • Key Results:
      • Complete 20 customer interviews
      • Achieve 15% conversion on the landing page from warm traffic (an Exponential Scout rule of thumb; set your own pass/fail line before the test)
      • Get 3 letters of intent from enterprise customers

    7. Success Metrics and KPIs

    Product-Market Fit Indicators

    Retention and repeat payment lead. Survey scores support them and never stand alone.

    Leading evidence:

    • Retention curves: flattening retention curves
    • Repeat payment: customers keep paying or buy again
    • Usage frequency: daily or weekly active use

    Supporting evidence only (Exponential Scout rules of thumb):

    • The 40% Rule (Sean Ellis Test): ask customers “How would you feel if you could no longer use this product?” 40% or more answering “Very disappointed” supports a fit claim; 25 to 40% suggests you are on the way; under 25% suggests not yet. A survey answer is a statement, not behavior.
    • NPS of 50 or more
    • Organic growth of 20% or more month over month without paid marketing

    Customer Evidence: Rules of Thumb

    Interviews:

    • Problem: 80% of interviewees confirm the problem exists
    • Solution interest: 60% say they would pay. This is an interest signal, not validation. Willingness to pay is shown only by payment; a pre-order or deposit counts, a survey answer does not.
    • Feature priority: clear consensus on the top 3 features

    Conversion (Exponential Scout rules of thumb, not published benchmarks):

    • Landing page: 2 to 5% of visitors sign up, from cold, targeted traffic (varies by industry)
    • Email signup: 15 to 25% of email signups start a trial
    • Free trial: 15 to 20% of trial users convert to paid
    • Early adopters: 100 engaged early users

    Set your own pass/fail line before the test.

    Learning Velocity Measurements

    Experiment Velocity:

    • Experiments per Week: Target 2-3 experiments per week
    • Time to Results: Average 1-2 weeks per experiment
    • Learning per Dollar: Insights gained per experiment budget

    Knowledge Accumulation:

    • Assumption Validation Rate: % of assumptions tested per month
    • Pivot Speed: Time from negative results to new direction
    • Market Understanding: Depth of customer insight documentation

    Customer Discovery and Lean Startup vs. Design

    Like Design’s ethnography, Lean Startup emphasizes talking to customers, often referenced as Customer Discovery. With Customer Discovery, you are conducting research to test your assumptions about the problem you believe to be solving for the customer and about the solution’s efficacy for solving the problem in the customer’s eyes. Unlike Design, in Lean you test assumptions about the entire business model, not just about the product or service.

    Advanced Customer Discovery Techniques

    Customer Discovery Interview Types:

    1. Problem Interviews: Validate the problem exists
    2. Solution Interviews: Test your proposed solution
    3. MVP Interviews: Get feedback on early product versions
    4. Pricing Interviews: Learn how customers think about price. Treat their answers as an interest signal; willingness to pay is shown only by payment.

    Customer Journey Mapping for Validation:

    • Map current customer behavior
    • Identify pain points and opportunities
    • Test solutions at each stage
    • Validate improved journey with customers

    Conclusion

    The Lean Startup methodology provides a systematic approach to reducing uncertainty and risk in new product development. By focusing on validated learning through rapid experimentation, companies can build products that customers actually want while conserving resources and time. The key is maintaining discipline in the experimentation process, measuring what matters, and making data-driven decisions about when to persevere, pivot, or stop.

    Success with Lean Startup requires commitment to the learning process, willingness to challenge assumptions, and the discipline to let data guide decisions even when they conflict with personal beliefs or preferences.

    en_USEnglish
    es_GTEspañol de Guatemala en_USEnglish