Inspired (Marty Cagan)
Problem
Products fail when teams focus on delivering features instead of solving customer problems.
Action
Give a cross-functional team ownership of an important customer problem.
Outcome
The team creates products that deliver lasting value to customers and businesses.
Chapter: Lessons from Top Tech Companies - Behind Every Great Product
Problem
Technology has little value when it does not improve the customer experience.
Action
Apply technology to solve real customer problems more effectively.
Outcome
Customers receive clear and meaningful product benefits.
Chapter: Lessons from Top Tech Companies - Technology-Powered Products and Services
Problem
Growing before proving customer demand wastes time and resources.
Action
Confirm that customers consistently choose and value the product before expanding.
Outcome
The company scales on a stronger foundation.
Chapter: Lessons from Top Tech Companies - Startups: Getting to Product/Market Fit
Problem
Rapid growth often reduces team effectiveness.
Action
Expand the organization without taking ownership away from product teams.
Outcome
The company grows without losing execution quality.
Chapter: Lessons from Top Tech Companies - Growth-Stage Companies: Scaling to Success
Problem
Large organizations often stop improving successful products.
Action
Support ongoing product discovery across all product teams.
Outcome
The company continues delivering valuable innovations.
Chapter: Lessons from Top Tech Companies - Enterprise Companies: Consistent Product Innovation
Problem
Product efforts fail when major assumptions remain untested.
Action
Test customer value, usability, feasibility, and business viability before full development.
Outcome
The team avoids costly product failures.
Chapter: Lessons from Top Tech Companies - The Root Causes of Failed Product Efforts
Problem
Fast delivery cannot compensate for building the wrong product.
Action
Run continuous product discovery alongside iterative delivery.
Outcome
The team builds solutions that customers truly need.
Chapter: Lessons from Top Tech Companies - Beyond Lean and Agile
Problem
Teams lose focus when they confuse goals, problems, and features.
Action
Define the desired outcome and customer problem before choosing a solution.
Outcome
The team makes clearer product decisions.
Chapter: Lessons from Top Tech Companies - Key Concepts
Problem
Individual ownership reduces cross-disciplinary collaboration.
Action
Make the entire product team responsible for solving customer problems.
Outcome
The team works together to achieve better results.
Chapter: The Right People - Product Teams - Principles of Strong Product Teams
Problem
Product decisions become weak without deep customer knowledge.
Action
Study customer needs before deciding what to build.
Outcome
The team focuses on solving important problems.
Chapter: The Right People - Product Teams - The Product Manager
Problem
Useful features can still create a poor product experience.
Action
Design every important customer interaction as a single connected experience.
Outcome
Customers complete their goals more easily.
Chapter: The Right People - Product Teams - The Product Designer
Problem
Late engineering involvement limits solution quality.
Action
Engage engineers from the beginning of product discovery.
Outcome
The team develops stronger and more practical solutions.
Chapter: The Right People - Product Teams - The Engineers
Problem
Customers struggle to value products with unclear positioning.
Action
Define the target customer and clearly communicate the product's value.
Outcome
The right customers understand why the product matters.
Chapter: The Right People - Product Teams - Product Marketing Managers
Problem
Product teams cannot provide every type of expertise themselves.
Action
Bring specialist partners into product work without transferring ownership.
Outcome
The team gains expert support while remaining accountable.
Chapter: The Right People - Product Teams - The Supporting Roles
Problem
Product recommendations are weak without credible evidence.
Action
Support important decisions with customer insights and product evidence.
Outcome
Stakeholders trust the team's recommendations.
Chapter: The Right People - Product Teams - Profile: Jane Manning of Google
Problem
Command-driven leadership reduces team ownership.
Action
Provide direction while allowing teams to choose solutions.
Outcome
Teams become more capable and accountable.
Chapter: The Right People - People @ Scale - The Role of Leadership
Problem
Weak product management limits product success.
Action
Coach product managers through regular feedback and support.
Outcome
Product management capability improves across the organization.
Chapter: The Right People - People @ Scale - The Head of Product Role
Problem
Weak technical capability limits product innovation.
Action
Continuously develop engineering skills and technical practices.
Outcome
Teams deliver stronger technology solutions.
Chapter: The Right People - People @ Scale - The Head of Technology Role
Problem
Operational barriers slow product delivery.
Action
Identify and eliminate coordination problems that delay progress.
Outcome
Teams deliver value more reliably.
Chapter: The Right People - People @ Scale - The Delivery Manager Role
Problem
Frequent team changes reduce learning and accountability.
Action
Keep long-lived teams responsible for defined product areas.
Outcome
Teams build deeper expertise over time.
Chapter: The Right People - People @ Scale - Principles of Structuring Product Teams
Problem
Organizations resist change without visible success.
Action
Lead improvements that produce measurable product results.
Outcome
People gain confidence in better product practices.
Chapter: The Right People - People @ Scale - Profile: Lea Hickman of Adobe
Problem
Early feature commitments reduce product flexibility.
Action
Avoid committing to specific features before important risks are understood.
Outcome
The team adapts more effectively to new evidence.
Chapter: The Right Product - Product Roadmaps - The Problems with Product Roadmaps
Problem
Feature plans encourage output rather than results.
Action
Guide product teams with measurable business and customer outcomes.
Outcome
Teams focus on creating meaningful impact.
Chapter: The Right Product - Product Roadmaps - The Alternative to Roadmaps
Problem
Teams lose direction without a shared view of the future.
Action
Link product strategy to a clear long-term product vision.
Outcome
Daily decisions support long-term success.
Chapter: The Right Product - Product Vision - Product Vision and Product Strategy
Problem
People cannot align around an unclear destination.
Action
Create a clear picture of the future customer experience.
Outcome
Teams move toward the same long-term goal.
Chapter: The Right Product - Product Vision - Principles of Product Vision
Problem
Trying to pursue every opportunity weakens execution.
Action
Choose the markets and customer problems with the greatest potential.
Outcome
Resources create greater product impact.
Chapter: The Right Product - Product Vision - Principles of Product Strategy
Problem
Teams make inconsistent choices without shared guidance.
Action
Document product principles that guide common tradeoffs.
Outcome
Teams make more consistent decisions.
Chapter: The Right Product - Product Vision - Product Principles
Problem
Teams cannot judge success without clear measures.
Action
Define objectives with measurable key results.
Outcome
Progress becomes easier to evaluate.
Chapter: The Right Product - Product Objectives - The OKR Technique
Problem
Completing features does not guarantee success.
Action
Assign each product team measurable product outcomes.
Outcome
Teams focus on delivering customer and business value.
Chapter: The Right Product - Product Objectives - Product Team Objectives
Problem
Independent goals create conflicting priorities.
Action
Connect team objectives to the company's shared objectives.
Outcome
The organization moves in one direction.
Chapter: The Right Product - Product @ Scale - Product Objectives @ Scale
Problem
People lose alignment without regular communication.
Action
Explain the product vision, strategy, evidence, and progress repeatedly.
Outcome
Stakeholders stay informed and aligned.
Chapter: The Right Product - Product @ Scale - Product Evangelism
Problem
Product strategy weakens when based on internal assumptions.
Action
Use customer and market evidence to guide strategic decisions.
Outcome
The product better matches real customer needs.
Chapter: The Right Product - Product @ Scale - Profile: Alex Pressland of the BBC
Problem
Building before learning creates unnecessary waste.
Action
Validate the most critical product assumptions before implementation.
Outcome
The team invests with greater confidence.
Chapter: The Right Process - Product Discovery - Principles of Product Discovery
Problem
Different uncertainties require different forms of evidence.
Action
Choose discovery techniques that answer the current product question.
Outcome
Learning becomes faster and more effective.
Chapter: The Right Process - Product Discovery - Discovery Techniques Overview
Problem
Teams waste effort by pursuing weak opportunities.
Action
Evaluate customer value and business potential before committing resources.
Outcome
The team focuses on stronger opportunities.
Chapter: The Right Process - Discovery Framing Techniques - Opportunity Assessment Technique
Problem
Teams often focus on product features rather than customer outcomes.
Action
Write the future customer experience from the customer's perspective.
Outcome
The intended product value becomes clearer.
Chapter: The Right Process - Discovery Framing Techniques - Customer Letter Technique
Problem
Hidden assumptions increase product risk.
Action
Capture the most important business assumptions on a startup canvas.
Outcome
The team knows what to validate first.
Chapter: The Right Process - Discovery Framing Techniques - Startup Canvas Technique
Problem
Discovery activities waste effort without a clear purpose.
Action
Define what the team must learn before planning discovery work.
Outcome
Every activity reduces meaningful uncertainty.
Chapter: The Right Process - Discovery Planning Techniques
Problem
Feature lists hide how customers accomplish their goals.
Action
Create a story map that follows the customer's workflow.
Outcome
The team understands the complete product experience.
Chapter: The Right Process - Discovery Planning Techniques - Story Map Technique
Problem
Discovery slows when customers are difficult to reach.
Action
Maintain an ongoing customer discovery program.
Outcome
The team learns from customers continuously.
Chapter: The Right Process - Discovery Planning Techniques - Customer Discovery Program Technique
Problem
Planning weakens when market knowledge arrives too late.
Action
Use market insights throughout product discovery.
Outcome
The team makes stronger product decisions.
Chapter: The Right Process - Discovery Planning Techniques - Profile: Martina Lauchengco of Microsoft
Problem
Hypothetical answers provide unreliable evidence.
Action
Discuss specific situations customers have already experienced.
Outcome
The team gains more accurate customer insights.
Chapter: The Right Process - Discovery Ideation Techniques - Customer Interviews
Problem
Automation can hide whether customers truly value a service.
Action
Provide the service manually during early validation.
Outcome
The team learns customer value with less risk.
Chapter: The Right Process - Discovery Ideation Techniques - Concierge Test Technique
Problem
Customer workarounds reveal unmet needs.
Action
Observe how customers adapt existing products to solve problems.
Outcome
The team discovers valuable product opportunities.
Chapter: The Right Process - Discovery Ideation Techniques - The Power of Customer Misbehavior
Problem
Routine work leaves little space for new ideas.
Action
Reserve dedicated time for rapid product experiments.
Outcome
Teams discover more promising solutions.
Chapter: The Right Process - Discovery Ideation Techniques - Hack Days
Problem
Large prototypes waste time and effort.
Action
Create only the prototype needed to answer the current question.
Outcome
The team learns faster with less work.
Chapter: The Right Process - Discovery Prototyping Techniques - Principles of Prototypes
Problem
Technical uncertainty can block product success.
Action
Prototype the most difficult engineering challenge before full development.
Outcome
The team understands technical feasibility early.
Chapter: The Right Process - Discovery Prototyping Techniques - Feasibility Prototype Technique
Problem
Usability problems become expensive after development.
Action
Test interactive prototypes with representative users.
Outcome
The customer experience improves before implementation.
Chapter: The Right Process - Discovery Prototyping Techniques - User Prototype Technique
Problem
Artificial test conditions reduce the quality of learning.
Action
Evaluate prototypes with live data whenever practical.
Outcome
The results better reflect real product use.
Chapter: The Right Process - Discovery Prototyping Techniques - Live-Data Prototype Technique
Problem
One prototype cannot answer every important question.
Action
Use different prototype approaches to test different risks.
Outcome
The team gains broader product evidence.
Chapter: The Right Process - Discovery Prototyping Techniques - Hybrid Prototype Technique
Problem
Teams overlook usability problems without direct observation.
Action
Watch representative users complete realistic tasks.
Outcome
The team identifies important usability improvements.
Chapter: The Right Process - Discovery Testing Techniques - Testing Usability
Problem
Interest alone does not prove customer value.
Action
Test whether customers willingly choose the proposed solution.
Outcome
The team confirms meaningful customer value.
Chapter: The Right Process - Discovery Testing Techniques - Testing Value
Problem
Customer opinions do not reliably predict demand.
Action
Measure observable customer actions rather than stated intentions.
Outcome
The team estimates market demand more accurately.
Chapter: The Right Process - Discovery Testing Techniques - Demand Testing Techniques
Problem
Behavior alone does not explain customer decisions.
Action
Discuss customer reactions immediately after qualitative testing.
Outcome
The team understands what drives customer choices.
Chapter: The Right Process - Discovery Testing Techniques - Qualitative Value Testing Techniques
Problem
Small studies provide limited confidence.
Action
Measure customer behavior across larger groups.
Outcome
The team gathers stronger evidence of the product's value.
Chapter: The Right Process - Discovery Testing Techniques - Quantitative Value Testing Techniques
Problem
Technical surprises delay product delivery.
Action
Evaluate technical feasibility before committing to implementation.
Outcome
Development becomes more predictable.
Chapter: The Right Process - Discovery Testing Techniques - Testing Feasibility
Problem
Customer value alone cannot guarantee product success.
Action
Verify that the solution fits business constraints before development.
Outcome
The product supports long-term business success.
Chapter: The Right Process - Discovery Testing Techniques - Testing Business Viability
Problem
Data alone cannot make every product decision.
Action
Combine experiment results with experienced product judgment.
Outcome
The team makes more reliable decisions.
Chapter: The Right Process - Discovery Testing Techniques - Profile: Kate Arnold of Netflix
Problem
Long discovery cycles delay learning.
Action
Run focused discovery sprints to address important product questions.
Outcome
The team reduces uncertainty quickly.
Chapter: The Right Process - Transformation Techniques - Discovery Sprint Technique
Problem
Large organizational change is difficult without proof.
Action
Introduce new product practices through a single capable product team.
Outcome
The organization gains practical evidence for broader adoption.
Chapter: The Right Process - Transformation Techniques - Pilot Team Technique
Problem
Feature roadmaps limit adaptation to new learning.
Action
Gradually replace feature commitments with outcome-focused planning.
Outcome
Teams respond more effectively to evidence.
Chapter: The Right Process - Transformation Techniques - Weaning an Organization Off Roadmaps
Problem
Late communication creates unnecessary resistance.
Action
Keep stakeholders informed throughout product discovery.
Outcome
Support for product decisions increases.
Chapter: The Right Process - Process @ Scale - Managing Stakeholders
Problem
Learning loses value when it stays within one team.
Action
Communicate important product discoveries across the organization.
Outcome
Teams improve faster together.
Chapter: The Right Process - Process @ Scale - Communicating Product Learnings
Problem
Product quality declines without experienced oversight.
Action
Review important product decisions with experienced leaders.
Outcome
The organization maintains consistently high product quality.
Chapter: The Right Process - Process @ Scale - Profile: Camille Hearst of Apple
Problem
Feature-driven teams create less customer value.
Action
Give product teams authority to discover the best solutions.
Outcome
Teams deliver products with greater impact.
Chapter: The Right Culture - Good Product Team/Bad Product Team
Problem
Innovation slows when experimentation becomes difficult.
Action
Create an environment where teams can safely test new ideas.
Outcome
More valuable product innovations emerge.
Chapter: The Right Culture - Top Reasons for Loss of Innovation
Problem
Complex coordination reduces product velocity.
Action
Reduce unnecessary approvals and dependencies.
Outcome
Teams deliver value more quickly.
Chapter: The Right Culture - Top Reasons for Loss of Velocity
Problem
Strong product practices cannot survive without supportive daily behaviors.
Action
Reward learning, ownership, collaboration, and customer focus consistently.
Outcome
The organization sustains long-term product excellence.
Chapter: The Right Culture - Establishing a Strong Product Culture