Product Discovery

What Is Product Discovery?

Product Discovery is a structured approach to identifying and validating the highest-value product opportunities before committing significant delivery resources. This technique focuses on reducing risk and uncertainty by systematically exploring user problems, mapping critical assumptions, and testing both problem and solution fit early in the product development process. The Claude Code skill "Product Discovery" operationalizes this methodology, enabling product teams to facilitate Opportunity Solution Trees, map and prioritize assumptions, plan and execute discovery sprints, and rigorously validate concepts with user evidence.

Why Use Product Discovery?

Building software involves significant investment and risk. Most product failures result not from engineering issues, but from building products that customers do not want or need. Product Discovery addresses this by ensuring teams solve the right problem, for the right users, with the right solution—before scaling up development.

Key benefits of Product Discovery include:

• Risk Reduction: By validating opportunities and solutions early, teams avoid costly mistakes.
• User-Centricity: Discovery ensures real user needs drive product decisions, not internal assumptions.
• Faster Learning: Iterative sprints and rapid prototyping generate actionable insights quickly.
• Alignment: Clear mapping of outcomes, opportunities, and experiments aligns stakeholders on evidence-based priorities.

By systematically mapping assumptions and continuously testing them, Product Discovery helps teams focus resources on initiatives with the highest potential impact.

How to Get Started

Implementing Product Discovery with the Claude Code skill involves the following core workflow:

1. Define Desired

Outcome

Start by selecting a single, measurable outcome you want to improve (e.g., increase activation rate, reduce churn). Establish a baseline and set a clear target horizon.

2. Build Opportunity Solution

Tree (OST)

The Opportunity Solution Tree (OST) is a visual framework to connect outcomes to opportunities and solution ideas:

• Outcome → Opportunities → Solution Ideas → Experiments

Opportunities should be grounded in user evidence, not opinions. The OST helps visualize the rationale for pursuing specific solutions.

3. Map

Assumptions

Identify the critical assumptions underlying each solution idea. Categorize them by:

• Desirability: Do users want this?
• Viability: Will it work for the business?
• Feasibility: Can we build it?
• Usability: Can users use it effectively?

Score each assumption by risk and certainty.

Practical code example:
Use the provided assumption mapping script to score and organize your assumptions:

python3 scripts/assumption_mapper.py assumptions.csv

This script helps structure, prioritize, and document key risks for each solution.

4. Validate the

Problem

Conduct user interviews, surveys, and behavioral analysis to confirm that the problem is real, frequent, and severe enough to warrant a solution. Reject weak or low-value opportunities early to focus efforts on the most critical areas.

5. Validate the

Solution

Before committing to full development, use prototypes and experiments to test your solution ideas:

• Concept Tests: Gauge initial user interest.
• Usability Tests: Ensure users can interact with prototypes as intended.
• Value Tests: Validate willingness to pay or adopt.

Measure actual behavior, not just stated preferences, to ensure evidence-driven decisions.

6. Plan Discovery

Sprint

Structure discovery work into 1-2 week sprints, each with explicit hypotheses and daily evidence reviews. Capture learnings, adjust assumptions, and iterate rapidly.

Key Features

The Claude Code Product Discovery skill offers several features to streamline and scale structured product discovery:

• Opportunity Solution Tree Facilitation: Visually map outcomes to opportunities and solutions.
• Assumption Mapping & Risk Scoring: Identify, categorize, and score critical risks using automated scripts.
• Interview & Evidence Templates: Standardize problem validation and synthesis.
• Rapid Prototyping Support: Integrate lightweight prototyping for solution validation.
• Discovery Sprint Planning: Plan, execute, and document iterative discovery cycles.

These capabilities help teams maintain a disciplined, evidence-driven process from idea to validated concept.

Best Practices

To maximize the value of Product Discovery:

• Ground Everything in User Evidence: Avoid internal biases by prioritizing direct user input.
• Prioritize by Risk: Focus validation on the riskiest assumptions first—often desirability and value.
• Iterate Rapidly: Use short sprints and frequent feedback cycles to learn quickly and adapt.
• Measure Behavior, Not Opinion: Rely on what users do, not just what they say.
• Document Learnings Transparently: Share evidence, assumptions, and decisions openly to align the team.

Important Notes

• Product Discovery should precede, not replace, delivery. Use it to inform what is built, not how it is built.
• Not all ideas merit full validation; apply a lightweight approach for low-risk or well-understood domains.
• The assumption mapping script (assumption_mapper.py) requires a properly formatted CSV file (see repository documentation for schema).
• Product Discovery is ongoing: revisit assumptions and evidence as the market and user needs evolve.
• For full documentation and usage examples, refer to the official GitHub repository.

By institutionalizing Product Discovery, product teams can consistently identify, validate, and deliver solutions that truly matter to users and drive business outcomes.