The Lean Product Playbook (Dan Olsen)
Problem
A product cannot succeed if it does not deliver sufficient value to its target customers.
Action
Confirm that target customers consistently want, use, and prefer the product before expanding.
Outcome
Growth is supported by real customer demand.
Chapter: Core Concepts - Achieving Product-Market Fit with the Lean Product Process - What Is Product-Market Fit?
Problem
Weak product foundations reduce customer value.
Action
Define customers, needs, value proposition, features, and user experience in a logical order.
Outcome
The product delivers clear and consistent value.
Chapter: Core Concepts - Achieving Product-Market Fit with the Lean Product Process - The Product-Market Fit Pyramid
Problem
Established competitors are difficult to beat without a meaningful advantage.
Action
Deliver a better solution for an important customer problem than competing products.
Outcome
Customers have a compelling reason to switch.
Chapter: Core Concepts - Achieving Product-Market Fit with the Lean Product Process - Quicken: from #47 to #1
Problem
Unstructured product decisions increase waste and uncertainty.
Action
Complete each step of the lean product process before moving to the next.
Outcome
The team reduces product risk through continuous learning.
Chapter: Core Concepts - Achieving Product-Market Fit with the Lean Product Process - The Lean Product Process
Problem
Building a solution too early creates unnecessary waste.
Action
Identify the customer's problem before deciding how to solve it.
Outcome
The product addresses a real customer need.
Chapter: Core Concepts - Problem Space versus Solution Space - The Space Pen
Problem
Product categories can hide the real market opportunity.
Action
Group customers by the important problems they are trying to solve.
Outcome
The market becomes easier to understand and serve.
Chapter: Core Concepts - Problem Space versus Solution Space - Problems Define Markets
Problem
Jumping to solutions limits better ideas.
Action
Define what customers want before deciding how to deliver it.
Outcome
The team explores stronger solution options.
Chapter: Core Concepts - Problem Space versus Solution Space - The What and the How
Problem
Internal assumptions often produce products customers do not value.
Action
Base product decisions on validated customer needs instead of internal opinions.
Outcome
The product becomes more relevant to the market.
Chapter: Core Concepts - Problem Space versus Solution Space - Outside-In Product Development
Problem
Requested features may not solve the underlying need.
Action
Ask customers about their goals, problems, and experiences rather than their preferred features.
Outcome
The team discovers more valuable product opportunities.
Chapter: Core Concepts - Problem Space versus Solution Space - Should You Listen to Customers?
Problem
Interesting features do not always solve meaningful problems.
Action
Judge every feature by the customer problem it solves and the benefit it provides.
Outcome
Development stays focused on valuable improvements.
Chapter: Core Concepts - Problem Space versus Solution Space - A Tale of Two Apple Features
Problem
Customers may struggle to describe unmet needs directly.
Action
Show possible solutions and observe customer reactions.
Outcome
Hidden customer needs become easier to identify.
Chapter: Core Concepts - Problem Space versus Solution Space - Using the Solution Space to Discover the Problem Space
Problem
Trying to serve everyone weakens product focus.
Action
Choose a specific customer group with the strongest unmet need.
Outcome
The product better fits its intended audience.
Chapter: The Lean Product Process - Determine Your Target Customer (Step 1) - Fishing for Customers
Problem
Broad markets hide important differences in customer needs.
Action
Create market segments based on shared needs and behaviors.
Outcome
The team can target customers more effectively.
Chapter: The Lean Product Process - Determine Your Target Customer (Step 1) - How to Segment Your Target Market
Problem
The product user and the buyer may have different priorities.
Action
Identify the needs of both users and buyers before making product decisions.
Outcome
The product better supports adoption and purchase.
Chapter: The Lean Product Process - Determine Your Target Customer (Step 1) - Users versus Buyers
Problem
Different customers accept innovation at different speeds.
Action
Focus first on the customer group most willing to adopt a new product.
Outcome
Early adoption becomes more likely.
Chapter: The Lean Product Process - Determine Your Target Customer (Step 1) - Technology Adoption Life Cycle
Problem
Assumptions about customers lead to poor product decisions.
Action
Create personas using evidence gathered from real customers.
Outcome
The team shares a realistic view of the target customer.
Chapter: The Lean Product Process - Determine Your Target Customer (Step 1) - Personas
Problem
Solution-focused language limits creative thinking.
Action
Express customer needs without mentioning products or features.
Outcome
The team identifies more solution possibilities.
Chapter: The Lean Product Process - Identify Underserved Customer Needs (Step 2) - A Customer Need by Any Other Name
Problem
Tasks alone do not explain what customers truly value.
Action
Identify the result customers want from each important task.
Outcome
The product delivers more meaningful benefits.
Chapter: The Lean Product Process - Identify Underserved Customer Needs (Step 2) - Customer Needs Example: TurboTax
Problem
Hypothetical answers often differ from actual behavior.
Action
Ask customers to describe recent situations they have experienced.
Outcome
Customer research becomes more reliable.
Chapter: The Lean Product Process - Identify Underserved Customer Needs (Step 2) - Customer Discovery Interviews
Problem
Features can lose their purpose during development.
Action
Trace each feature back to the benefit it creates for customers.
Outcome
Development stays focused on customer value.
Chapter: The Lean Product Process - Identify Underserved Customer Needs (Step 2) - Customer Benefit Ladders
Problem
Customers reject products that fail to satisfy basic expectations.
Action
Prioritize fundamental customer needs before adding advanced benefits.
Outcome
The product earns customer trust.
Chapter: The Lean Product Process - Identify Underserved Customer Needs (Step 2) - Hierarchies of Needs
Problem
Resources cannot address every customer need equally.
Action
Focus on needs that are highly important but poorly satisfied.
Outcome
Development creates greater customer value.
Chapter: The Lean Product Process - Identify Underserved Customer Needs (Step 2) - The Importance versus Satisfaction Framework
Problem
One evaluation method provides only a partial view.
Action
Assess customer needs using complementary frameworks before setting priorities.
Outcome
Product decisions become more balanced.
Chapter: The Lean Product Process - Identify Underserved Customer Needs (Step 2) - Related Frameworks
Problem
Large research findings are difficult to interpret.
Action
Display customer needs and opportunities in a clear visual format.
Outcome
Priorities become easier to identify.
Chapter: The Lean Product Process - Identify Underserved Customer Needs (Step 2) - Visualizing Customer Value
Problem
Different features influence customer satisfaction in different ways.
Action
Classify features by their impact on customer satisfaction before prioritizing them.
Outcome
The product delivers stronger overall satisfaction.
Chapter: The Lean Product Process - Identify Underserved Customer Needs (Step 2) - The Kano Model
Problem
Research creates little value without action.
Action
Use customer insights to rank development priorities.
Outcome
The product roadmap becomes more focused.
Chapter: The Lean Product Process - Identify Underserved Customer Needs (Step 2) - Putting the Frameworks to Use
Problem
Too many priorities weaken product strategy.
Action
Reject work that does not strengthen the value proposition.
Outcome
The product maintains a clear strategic direction.
Chapter: The Lean Product Process - Define Your Value Proposition (Step 3) - Strategy Means Saying "No"
Problem
Customers need a clear reason to choose one product over another.
Action
Identify the benefits your product delivers that competing alternatives do not.
Outcome
The product stands out in the market.
Chapter: The Lean Product Process - Define Your Value Proposition (Step 3) - Value Propositions for Search Engines
Problem
Marketing cannot compensate for weak customer value.
Action
Test customer interest before increasing marketing efforts.
Outcome
Resources support stronger product opportunities.
Chapter: The Lean Product Process - Define Your Value Proposition (Step 3) - Not So Cuil
Problem
An unclear value proposition weakens product decisions.
Action
Define how the product solves important customer problems better than alternatives.
Outcome
The team builds toward a shared product vision.
Chapter: The Lean Product Process - Define Your Value Proposition (Step 3) - Building Your Product Value Proposition
Problem
Current market conditions continue to change.
Action
Consider future customer expectations when defining product strategy.
Outcome
The product remains competitive over time.
Chapter: The Lean Product Process - Define Your Value Proposition (Step 3) - Skating to Where the Puck Will Be
Problem
Extra features weaken product clarity.
Action
Include only features that strengthen the primary customer benefit.
Outcome
Customers understand the product more easily.
Chapter: The Lean Product Process - Define Your Value Proposition (Step 3) - The Flip Video Camera
Problem
Future predictions may prove incorrect.
Action
Validate the assumptions behind the value proposition before making major investments.
Outcome
Strategic decisions become more reliable.
Chapter: The Lean Product Process - Define Your Value Proposition (Step 3) - Predicting the Future with Value Propositions
Problem
Feature lists often ignore customer value.
Action
Describe each feature from the user's perspective and include the expected benefit.
Outcome
Development remains focused on customer outcomes.
Chapter: The Lean Product Process - Specify Your Minimum Viable Product (MVP) Feature Set (Step 4) - User Stories: Features with Benefits
Problem
Large features delay learning and delivery.
Action
Split features into small, independent user stories.
Outcome
The team delivers and learns more frequently.
Chapter: The Lean Product Process - Specify Your Minimum Viable Product (MVP) Feature Set (Step 4) - Breaking Features Down
Problem
Large batches increase development risk.
Action
Complete and validate small increments of work.
Outcome
The team adapts more quickly.
Chapter: The Lean Product Process - Specify Your Minimum Viable Product (MVP) Feature Set (Step 4) - Smaller Batch Sizes Are Better
Problem
Precise time estimates are often unreliable.
Action
Estimate work by comparing the relative size of user stories.
Outcome
Planning becomes more consistent.
Chapter: The Lean Product Process - Specify Your Minimum Viable Product (MVP) Feature Set (Step 4) - Scoping with Story Points
Problem
Not every feature deserves the same investment.
Action
Compare expected customer value with implementation effort before prioritizing work.
Outcome
Development creates a greater impact.
Chapter: The Lean Product Process - Specify Your Minimum Viable Product (MVP) Feature Set (Step 4) - Using Return on Investment to Prioritize
Problem
An oversized MVP delays customer learning.
Action
Include only the features needed to validate the value proposition.
Outcome
The team learns sooner with less investment.
Chapter: The Lean Product Process - Specify Your Minimum Viable Product (MVP) Feature Set (Step 4) - Deciding on Your MVP Candidate
Problem
Complex MVPs slow learning.
Action
Create the simplest product that can validate the most important assumptions.
Outcome
Evidence guides future product investment.
Chapter: The Lean Product Process - Create Your MVP Prototype (Step 5) - What Is (and Isn't) an MVP?
Problem
Different uncertainties require different evidence.
Action
Choose the MVP test that directly validates the key assumption.
Outcome
Learning becomes more effective.
Chapter: The Lean Product Process - Create Your MVP Prototype (Step 5) - MVP Tests
Problem
Using the wrong test limits useful learning.
Action
Choose the testing approach that best answers the product question.
Outcome
The team gathers stronger evidence.
Chapter: The Lean Product Process - Create Your MVP Prototype (Step 5) - The Matrix of MVP Tests
Problem
Customers may misunderstand the product's value.
Action
Evaluate different marketing messages with target customers.
Outcome
Product communication becomes more effective.
Chapter: The Lean Product Process - Create Your MVP Prototype (Step 5) - Qualitative Marketing MVP Tests
Problem
Customer opinions do not always predict behavior.
Action
Run measurable marketing experiments before full product development.
Outcome
Market demand is validated with evidence.
Chapter: The Lean Product Process - Create Your MVP Prototype (Step 5) - Quantitative Marketing MVP Tests
Problem
Discussion alone cannot reveal usability problems.
Action
Watch customers complete realistic tasks with a prototype.
Outcome
The team identifies practical improvements.
Chapter: The Lean Product Process - Create Your MVP Prototype (Step 5) - Qualitative Product MVP Tests
Problem
Small observations cannot represent overall customer behavior.
Action
Collect usage data from a larger group of target customers.
Outcome
Product decisions rely on stronger evidence.
Chapter: The Lean Product Process - Create Your MVP Prototype (Step 5) - Quantitative Product MVP Tests
Problem
Poor user experience reduces product value.
Action
Design every part of the experience to help customers achieve their goals.
Outcome
Customers gain more value from the product.
Chapter: The Lean Product Process - Apply the Principles of Great UX Design - What Makes a Great UX?
Problem
Visual polish cannot overcome weak product structure.
Action
Design the product model and interactions before refining visual details.
Outcome
The experience becomes easier to understand and use.
Chapter: The Lean Product Process - Apply the Principles of Great UX Design - The UX Design Iceberg
Problem
Confusing product concepts increase customer errors.
Action
Organize product concepts into a simple mental model.
Outcome
Customers understand how the product works more quickly.
Chapter: The Lean Product Process - Apply the Principles of Great UX Design - Conceptual Design
Problem
A poor information structure makes features difficult to find.
Action
Arrange information according to customer expectations and common tasks.
Outcome
Customers navigate the product more efficiently.
Chapter: The Lean Product Process - Apply the Principles of Great UX Design - Information Architecture
Problem
Complicated interactions make important tasks harder to complete.
Action
Design each interaction to match how customers naturally expect the product to work.
Outcome
Customers complete tasks more easily.
Chapter: The Lean Product Process - Apply the Principles of Great UX Design - Interaction Design
Problem
Poor visual organization hides important information.
Action
Arrange visual elements to emphasize the most important actions and content.
Outcome
Customers understand the interface more quickly.
Chapter: The Lean Product Process - Apply the Principles of Great UX Design - Visual Design
Problem
Inconsistent design patterns confuse customers.
Action
Use simple and consistent design patterns throughout the product.
Outcome
Customers learn the interface more easily.
Chapter: The Lean Product Process - Apply the Principles of Great UX Design - Design Principles
Problem
Confusing words create unnecessary customer mistakes.
Action
Use simple language that clearly explains actions and outcomes.
Outcome
Customers complete tasks with greater confidence.
Chapter: The Lean Product Process - Apply the Principles of Great UX Design - Copy Is Also Part of UX Design
Problem
Working separately weakens the customer experience.
Action
Collaborate closely across product, design, and engineering during development.
Outcome
The product delivers a stronger user experience.
Chapter: The Lean Product Process - Apply the Principles of Great UX Design - The A-Team
Problem
Internal opinions cannot prove a design works well.
Action
Observe representative customers using the product before finalizing the design.
Outcome
The experience better matches customer expectations.
Chapter: The Lean Product Process - Apply the Principles of Great UX Design - UX Is in the Eye of the Beholder
Problem
Too little testing can lead to overlooking common customer problems.
Action
Continue testing with target customers until the same issues appear repeatedly.
Outcome
The team gains more reliable usability findings.
Chapter: The Lean Product Process - Test Your MVP with Customers (Step 6) - How Many Customers Should I Test With?
Problem
Different testing methods answer different questions.
Action
Choose in-person, remote, or unmoderated testing based on the information you need.
Outcome
Customer research produces more useful evidence.
Chapter: The Lean Product Process - Test Your MVP with Customers (Step 6) - In-Person, Remote, and Unmoderated User Testing
Problem
Feedback from the wrong audience leads to poor product decisions.
Action
Recruit participants who closely match the target customer profile.
Outcome
Research better reflects the intended market.
Chapter: The Lean Product Process - Test Your MVP with Customers (Step 6) - How to Recruit Customers in Your Target Market
Problem
Late customer feedback makes improvements more expensive.
Action
Schedule customer testing at multiple stages of product development.
Outcome
Problems are discovered and corrected earlier.
Chapter: The Lean Product Process - Test Your MVP with Customers (Step 6) - User Testing at Intuit
Problem
Limited budgets can delay valuable customer learning.
Action
Run simple usability tests with inexpensive resources.
Outcome
The team continues learning without major cost.
Chapter: The Lean Product Process - Test Your MVP with Customers (Step 6) - Ramen User Testing
Problem
Unstructured testing produces inconsistent results.
Action
Guide every participant through the same core tasks and questions.
Outcome
Customer feedback becomes easier to compare.
Chapter: The Lean Product Process - Test Your MVP with Customers (Step 6) - How to Structure the User Test
Problem
Leading questions distort customer feedback.
Action
Use unbiased questions that encourage honest responses.
Outcome
The team receives more trustworthy insights.
Chapter: The Lean Product Process - Test Your MVP with Customers (Step 6) - How to Ask Good Questions
Problem
Closed questions reveal limited customer insight.
Action
Ask open questions that encourage customers to explain their experiences.
Outcome
The team better understands customer thinking.
Chapter: The Lean Product Process - Test Your MVP with Customers (Step 6) - Ask Open versus Closed Questions
Problem
Surface feedback can hide important customer problems.
Action
Encourage customers to describe specific frustrations in detail.
Outcome
The team uncovers higher-value improvement opportunities.
Chapter: The Lean Product Process - Test Your MVP with Customers (Step 6) - I Feel Your Pain
Problem
Important insights may appear only at the end of a conversation.
Action
Invite customers to share any additional thoughts before the session ends.
Outcome
The team collects more complete feedback.
Chapter: The Lean Product Process - Test Your MVP with Customers (Step 6) - Wrapping Up the User Test
Problem
Individual comments can hide the most important patterns.
Action
Group similar observations after each round of testing.
Outcome
Improvement priorities become clearer.
Chapter: The Lean Product Process - Test Your MVP with Customers (Step 6) - How to Capture and Synthesize User Feedback
Problem
Customers may reject a product for different reasons.
Action
Evaluate ease of use separately from whether the product solves an important need.
Outcome
The team identifies the correct improvement.
Chapter: The Lean Product Process - Test Your MVP with Customers (Step 6) - Usability versus Product-Market Fit
Problem
One development cycle cannot remove all uncertainty.
Action
Build, measure customer response, and apply the learning before repeating the cycle.
Outcome
The product steadily improves.
Chapter: The Lean Product Process - Iterate and Pivot to Improve Product-Market Fit - The Build-Measure-Learn Loop
Problem
Untested assumptions increase product risk.
Action
Define hypotheses and validate them through structured experiments.
Outcome
Product decisions rely on evidence instead of guesses.
Chapter: The Lean Product Process - Iterate and Pivot to Improve Product-Market Fit - The Hypothesize-Design-Test-Learn Loop
Problem
One round of customer testing rarely reveals every important issue.
Action
Revise the product and test each new version with target customers.
Outcome
The product moves closer to product-market fit.
Chapter: The Lean Product Process - Iterate and Pivot to Improve Product-Market Fit - Iterative User Testing
Problem
Continuing a weak strategy wastes valuable resources.
Action
Change direction when customer evidence consistently contradicts key assumptions.
Outcome
The team invests in stronger opportunities.
Chapter: The Lean Product Process - Iterate and Pivot to Improve Product-Market Fit - Persevere or Pivot?
Problem
Large releases delay learning and customer value.
Action
Build and release small working increments frequently.
Outcome
Customers benefit sooner, and the team learns faster.
Chapter: Building and Optimizing Your Product - Build Your Product Using Agile Development - Agile Development
Problem
Long planning cycles reduce adaptability.
Action
Organize development into short sprints with clear goals and regular reviews.
Outcome
The team responds to change more quickly.
Chapter: Building and Optimizing Your Product - Build Your Product Using Agile Development - Scrum
Problem
Too many active tasks slow delivery.
Action
Visualize workflow and restrict unfinished work.
Outcome
Work moves through the system more efficiently.
Chapter: Building and Optimizing Your Product - Build Your Product Using Agile Development - Kanban
Problem
No single agile method works best in every situation.
Action
Select the agile process that matches your team and product.
Outcome
Development becomes more effective.
Chapter: Building and Optimizing Your Product - Build Your Product Using Agile Development - Picking the Right Agile Methodology
Problem
Development processes become less effective without regular improvement.
Action
Review how the team works and refine the process regularly.
Outcome
Team performance improves over time.
Chapter: Building and Optimizing Your Product - Build Your Product Using Agile Development - Succeeding with Agile
Problem
Finding defects late increases development cost.
Action
Verify product quality continuously throughout development.
Outcome
Customers receive more reliable software.
Chapter: Building and Optimizing Your Product - Build Your Product Using Agile Development - Quality Assurance
Problem
Unclear expected behavior reduces software quality.
Action
Create automated tests before implementing new functionality.
Outcome
The codebase becomes more reliable.
Chapter: Building and Optimizing Your Product - Build Your Product Using Agile Development - Test-Driven Development
Problem
Large code merges create avoidable technical problems.
Action
Merge and verify small code changes frequently.
Outcome
Development remains stable.
Chapter: Building and Optimizing Your Product - Build Your Product Using Agile Development - Continuous Integration
Problem
Slow-release processes delay customer value.
Action
Automate deployment for approved product changes.
Outcome
Customers receive improvements sooner.
Chapter: Building and Optimizing Your Product - Build Your Product Using Agile Development - Continuous Deployment
Problem
Metrics alone cannot explain customer behavior.
Action
Use analytics together with direct customer research.
Outcome
The team gains a more complete understanding.
Chapter: Building and Optimizing Your Product - Measure Your Key Metrics - Analytics versus Other Learning Methods
Problem
Relying solely on numbers or intuition weakens decision-making.
Action
Use quantitative evidence together with thoughtful interpretation.
Outcome
Product decisions become more reliable.
Chapter: Building and Optimizing Your Product - Measure Your Key Metrics - Oprah versus Spock
Problem
Behavioral data cannot explain customer motivation.
Action
Conduct regular interviews with representative customers.
Outcome
The team better understands customer needs.
Chapter: Building and Optimizing Your Product - Measure Your Key Metrics - User Interviews
Problem
Analytics cannot reveal every usability problem.
Action
Watch customers perform realistic tasks with the product.
Outcome
The team identifies practical usability improvements.
Chapter: Building and Optimizing Your Product - Measure Your Key Metrics - Usability Testing
Problem
Unstructured opinions are difficult to compare.
Action
Use focused surveys with clear questions.
Outcome
Customer feedback becomes easier to analyze.
Chapter: Building and Optimizing Your Product - Measure Your Key Metrics - Surveys
Problem
Assumptions about product improvements are often wrong.
Action
Compare product alternatives through A/B testing.
Outcome
The team adopts evidence-based changes.
Chapter: Building and Optimizing Your Product - Measure Your Key Metrics - Analytics and A/B Testing
Problem
Disconnected metrics make it difficult to evaluate progress.
Action
Track product performance using a structured analytics framework.
Outcome
Progress becomes easier to measure consistently.
Chapter: Building and Optimizing Your Product - Measure Your Key Metrics - Analytics Frameworks
Problem
Too many success metrics divide attention.
Action
Choose one primary metric that best reflects current product success.
Outcome
The team aligns its improvement efforts.
Chapter: Building and Optimizing Your Product - Measure Your Key Metrics - Identify the Metric That Matters Most
Problem
Customer growth creates limited value when customers do not return.
Action
Measure retention and improve the product to encourage repeat use.
Outcome
Long-term customer value increases.
Chapter: Building and Optimizing Your Product - Measure Your Key Metrics - Retention Rate
Problem
Business results depend on several connected factors.
Action
Track the key operational metrics that influence financial outcomes.
Outcome
The business becomes easier to improve.
Chapter: Building and Optimizing Your Product - Measure Your Key Metrics - The Equation of Your Business
Problem
Revenue growth alone does not create a healthy business.
Action
Improve both revenue and operating efficiency over time.
Outcome
The business achieves sustainable profitability.
Chapter: Building and Optimizing Your Product - Measure Your Key Metrics - Achieving Profitability