Opportunity Solution Tree

Overview

An Opportunity Solution Tree is a visual framework that maps the path from a strategic outcome down through the customer opportunities that could achieve it, and then through the potential solutions that might address those opportunities. Developed by Teresa Torres, the framework starts with a business outcome (like "increase customer retention by 20%") at the root, branches into customer opportunities or jobs-to-be-done that customers are trying to accomplish (like "help customers reach advanced features faster"), and further branches into potential solutions that teams could build to address those opportunities. The Opportunity Solution Tree makes discovery and prioritization visible, helping teams explore multiple solution paths and make explicit trade-off decisions about which opportunities to pursue first.

Why is Opportunity Solution Tree Valuable?

The Opportunity Solution Tree prevents teams from jumping too quickly to solutions by forcing structured thinking about the relationship between business outcomes, customer opportunities, and potential solutions. By visualizing multiple solution paths to the same outcome, teams discover alternatives they might otherwise miss and make conscious trade-offs rather than defaulting to the first idea that comes to mind. The framework also improves communication—stakeholders with different solution ideas can see that multiple paths might reach the same outcome, shifting debates from "my solution is better" to "which outcome should we prioritize and which opportunity gets us there most efficiently." By making discovery systematic and visible, teams reduce the risk of pursuing the wrong solution to the right opportunity.

When Should an Opportunity Solution Tree Be Built?

Build an Opportunity Solution Tree when determining strategic direction or breaking down large, ambiguous goals into testable pathways. Use it in these scenarios:

• Strategic planning and outcome setting where teams need to align on what business outcomes matter and what customer needs must be addressed to achieve them

• Opportunity prioritization decisions where multiple potential solutions compete for resources and teams need a clear framework for comparing them

• Large feature or product initiatives where the solution isn't obvious and exploring multiple solution paths is valuable before committing engineering effort

• Cross-functional alignment when product, engineering, and business stakeholders have different views on priorities; the tree creates a shared model for discussing trade-offs

What Are the Drawbacks of Opportunity Solution Tree?

Building a comprehensive Opportunity Solution Tree requires time and good facilitation; poorly facilitated sessions create busywork without clarity. The framework also requires discipline to avoid conflating opportunities (what customers want to achieve) with solutions (how the product helps them); teams that blur this distinction end up with a confusing tree that looks like it solved the problem without actually clarifying thinking. Additionally, the Opportunity Solution Tree works best when you understand customer opportunities deeply; starting with half-baked customer research leads to incomplete or inaccurate opportunity mapping that misguides subsequent prioritization.

How to Create and Use an Opportunity Solution Tree Effectively

Building a useful Opportunity Solution Tree requires methodical process and honest conversation about trade-offs. Follow these practices:

• Start with a clear business outcome that's ambitious but measurable—this becomes the root of the tree and everything else flows from it; vague outcomes like "improve engagement" lead to vague opportunity mapping

• Identify customer opportunities and jobs-to-be-done that when addressed would move the needle on the business outcome; this is the critical thinking work where customer research deeply informs prioritization rather than opinions

• Generate multiple potential solutions for each opportunity without immediately evaluating them; breadth of solution options at this stage prevents anchoring on the first idea

• Evaluate solutions against criteria like customer value, business value, and implementation complexity to understand trade-offs and make deliberate prioritization choices

• Use the tree as an ongoing reference to evaluate new ideas (do they address an opportunity on the tree?), to revisit assumptions when experiments produce unexpected results, and to remind stakeholders why certain opportunities were prioritized

An effective Opportunity Solution Tree becomes a living document that guides product strategy and helps teams navigate inevitable constraints and trade-offs.