Product backlogs are where good ideas go to die. Random feature requests pile up with no clear connection to strategy, and teams argue endlessly about what to build next. Opportunity solution trees solve this by creating a visual hierarchy that connects business outcomes to customer opportunities to potential solutions.
What is an Opportunity Solution Tree?
An opportunity solution tree is a visual framework developed by Teresa Torres that maps the relationship between:
Outcome (top) - The business result you're trying to achieve
↓
Opportunities (middle) - Customer problems, pain points, and unmet needs
↓
Solutions (bottom) - Ideas for addressing those opportunities
This structure ensures every solution traces back to a customer opportunity, which connects to a measurable business outcome. No orphaned features, no building things just because they sound cool.
The Three Levels Explained
Level 1: Outcome
Your outcome is the business metric you're trying to move. It should be:
Specific and measurable:
- ✅ "Increase trial-to-paid conversion from 12% to 18% in Q2"
- ✅ "Reduce churn in first 90 days by 25%"
- ❌ "Improve the product"
- ❌ "Make customers happier"
Within your control:
Your team's work should directly influence this metric. "Increase revenue by $10M" is too broad if you're one of 10 product teams.
Time-bound:
Outcomes should be achievable within a quarter or two, not multi-year aspirations.
Aligned with company strategy:
Your outcome should clearly support broader company OKRs or goals.
Most teams work on one primary outcome at a time. Multiple outcomes create confusion and dilute focus.
Level 2: Opportunities
Opportunities are customer problems, pain points, and unmet needs that, if addressed, could drive your outcome.
Characteristics of good opportunities:
- Customer-centric: Framed from the customer's perspective ("Users don't understand pricing" not "We need better pricing")
- Problem-focused: Describe what's wrong, not how to fix it
- Evidence-based: Supported by customer interviews, usage data, or support feedback
- Specific enough to test: You can validate whether this is a real problem
Example opportunities for "Increase trial-to-paid conversion":
- Trial users don't experience "aha moment" before trial ends
- Pricing and plan options create decision paralysis
- Users can't easily get approval from decision-makers
- Setup process takes longer than users have time for
- Users don't understand whether the product fits their specific use case
Opportunities are organized hierarchically. A high-level opportunity like "Trial users don't experience value quickly enough" might have sub-opportunities:
- They don't know what to do first
- Data import is confusing and time-consuming
- They can't easily share with teammates to try together
- Empty state doesn't guide them toward value
This decomposition reveals which specific problems to tackle.
Level 3: Solutions
Solutions are specific ideas for addressing opportunities. The key: generate multiple solution ideas per opportunity before choosing.
For opportunity "Users don't know what to do first":
Solution ideas:
- Interactive onboarding wizard
- Role-based setup templates
- AI-powered setup assistant
- Short video tutorial on first login
- Progress checklist with recommended steps
- Smart defaults that work for 80% of users
By exploring the solution space, you avoid anchoring to your first idea and discover better alternatives.
Building Your Opportunity Solution Tree
Step 1: Define Your Outcome
Start with a clear business outcome your team owns. Get stakeholder alignment on this before going deeper—if leadership doesn't support the outcome, the rest of the tree is wasted effort.
Document:
- Current state: "Trial-to-paid conversion is 12%"
- Target state: "Trial-to-paid conversion of 18%"
- Timeline: "By end of Q2"
- Why it matters: Connection to company goals
Step 2: Discover Opportunities Through Customer Research
You don't invent opportunities—you discover them through continuous discovery habits:
Sources:
- Customer interviews - Ask about struggles and pain points
- Support tickets - Patterns in help requests
- Usage analytics - Where do users get stuck or abandon workflows?
- Sales feedback - Why do prospects hesitate or not buy?
- Churn analysis - What problems caused customers to leave?
- Competitive analysis - What do competitors solve that you don't?
Capture these as customer problem statements and add them to your tree.
Step 3: Structure Opportunities Hierarchically
Group related opportunities under parent themes. This reveals patterns and helps prioritize:
Parent: Onboarding friction
- Sub: Complex setup requirements
- Sub: No guidance on where to start
- Sub: Can't easily import existing data
Parent: Unclear value proposition
- Sub: Features seem overwhelming
- Sub: Use cases aren't obvious
- Sub: Results aren't visible in trial period
This grouping shows which problem areas have the most customer pain.
Step 4: Prioritize Opportunities
Not all opportunities deserve equal attention. Score them using:
Impact on outcome: If we solved this, how much would it move our metric?
Frequency: How many customers experience this?
Severity: How painful is it when it occurs?
Use frameworks like RICE scoring or impact-effort matrices to compare opportunities objectively.
Focus on one or two high-priority opportunities at a time. Spread too thin, you solve nothing well.
Step 5: Generate Multiple Solutions
For your top-priority opportunities, brainstorm 3-5 solution ideas. Use discovery sprints or team ideation sessions.
Questions to spark ideas:
- How do other products solve similar problems?
- What would the simplest possible solution look like?
- What would the most delightful solution be?
- How could we solve this without building anything?
- What if we had unlimited resources? What if we had zero resources?
Diverge before converging. Don't commit to one solution until you've explored alternatives.
Step 6: Test Assumptions for Top Solutions
Before building, validate your assumptions using assumption testing and prototype testing:
For the solution idea:
- Will customers understand it?
- Does it actually solve the problem?
- Will they use it?
- Can we build it within constraints?
For the underlying opportunity:
- Is this really a problem?
- How often does it occur?
- Would solving it impact our outcome?
Update your tree based on learnings. Some opportunities prove less important than expected. New ones emerge.
Using the Tree for Prioritization and Roadmapping
Your opportunity solution tree becomes the foundation for roadmap prioritization:
Prioritize opportunities first:
Which customer problems, if solved, would most impact our outcome?
Then prioritize solutions within those opportunities:
Which solution approach has the best balance of impact, confidence, and feasibility?
This two-level prioritization prevents the common mistake of optimizing solutions for low-impact opportunities.
Connecting to Sprint Planning
Translate tree decisions into sprint work:
High-level opportunity: "Users don't experience value before trial ends"
Prioritized solution: "Implement smart setup wizard with recommended path"
Sprint work: User stories, design tasks, engineering tickets
Link tickets back to the opportunity and outcome they support. This traces every line of code to customer value.
Making the Tree Collaborative and Visible
Tools for Building Trees
Visual collaboration tools:
- Miro or FigJam - Flexible, great for workshops
- Lucidchart - More structured, polished output
- Notion or Confluence - Text-based with linking
- ProductBoard or Pelin.ai - Purpose-built product tools
Use whatever your team already collaborates in. Adoption matters more than features.
Keep It Living, Not Static
Update your tree weekly based on new insights:
- Add opportunities from that week's customer interviews
- Mark solutions as validated, invalidated, or in-testing
- Adjust scores as you learn more
- Archive solved opportunities
A static tree becomes outdated and ignored. Treat it as living documentation.
Involve the Whole Team
Build and maintain the tree together:
- Weekly review - PM, designer, engineers discuss new opportunities and solutions
- Quarterly planning - Use the tree to guide roadmap decisions
- Stakeholder reviews - Show the tree to explain prioritization rationale
When the whole discovery team contributes, everyone understands the strategy.
Common Opportunity Solution Tree Mistakes
Mistake 1: Starting with Solutions
If your tree is full of "Add feature X" and "Build integration Y," you're organizing a backlog, not mapping opportunities.
Fix: For each item, ask: "What customer problem would that solve?" Keep asking until you reach the underlying opportunity.
Mistake 2: Opportunities That Are Really Solutions
"Need better onboarding" is a solution category, not an opportunity.
"Users don't know where to start" is an opportunity.
Fix: Frame opportunities as customer problems: "Customer can't do X" or "Users struggle with Y"
Mistake 3: No Evidence Behind Opportunities
Conference room brainstorming creates hypothetical problems, not real ones.
Fix: Every opportunity should link to supporting evidence—customer quotes, usage data, support tickets.
Mistake 4: Too Many Outcomes
Trying to optimize for acquisition, activation, retention, and revenue simultaneously spreads focus too thin.
Fix: Pick one outcome per tree. Create separate trees if you're truly working on multiple unrelated outcomes.
Mistake 5: Never Saying No
Every idea makes it onto the tree, which becomes a dumping ground for feature requests.
Fix: Set thresholds. Only opportunities scoring above X make the tree. Only solutions validated through testing get built.
Mistake 6: Build-First Mindset
Jumping from opportunity to building without testing solution ideas.
Fix: Mandate prototype testing or assumption testing before any solution moves to development.
Advanced Opportunity Solution Tree Techniques
Opportunity Scoring
Apply quantitative weights to opportunities:
- Customer impact: 1-10 scale
- Frequency: % of users affected
- Strategic value: Alignment with company priorities
Visualize with branch thickness or color intensity to show which opportunities matter most.
Solution Confidence Tracking
Tag each solution with confidence level:
- 🔴 Hypothesis (not tested)
- 🟡 Partially validated (some evidence)
- 🟢 Validated (strong evidence)
Only build 🟢 solutions. 🔴 and 🟡 need more discovery work.
Cross-Tree Connections
Sometimes one solution addresses multiple opportunities, or an opportunity impacts multiple outcomes.
Use linking or color-coding to show these connections. A solution that solves problems across multiple branches is extra valuable.
Historical Tracking
Document what you've tried and learned:
- ✅ Solved - Opportunity addressed, outcome improved
- ❌ Invalidated - Proved not a real problem
- 🚫 Deprioritized - Real problem, but not tackling now
This prevents revisiting settled questions and shows progress over time.
Integrating with Other Prioritization Methods
Opportunity solution trees work alongside:
- RICE or ICE scoring - Score opportunities and solutions numerically
- Weighted scoring models - Add factors like technical debt or strategic fit
- Impact-effort matrix - Visualize quick wins vs. big bets
- Stakeholder alignment - Use tree to explain and defend priorities
The tree provides structure; other frameworks add rigor to decision-making within that structure.
When Opportunity Solution Trees Work Best
Ideal for:
- Teams practicing continuous discovery
- Product work with measurable outcomes
- Environments with competing priorities
- Organizations valuing transparency in decision-making
Less useful for:
- Maintenance and bug fixes (just fix them)
- Obvious features with no ambiguity
- Platform or infrastructure work without direct customer touchpoints
Use the right tool for the context. Trees excel at strategic product work, not every category of work.
Build your opportunity solution tree from real customer data. Pelin.ai automatically surfaces opportunity themes from customer conversations across Intercom, Zendesk, Slack, and support channels. Request a free trial and connect every solution to real customer needs.