The Opportunity Solution Tree in Practice

August 11, 2026

An opportunity solution tree (OST) is a visual aid that helps product teams, often a "product trio," connect a desired business outcome to the customer needs and opportunities that drive it, and the solutions and experiments designed to address them. Introduced by Teresa Torres, this framework provides a structured approach to product discovery, moving beyond simple feature lists to map out the complexity of the opportunity space. It serves as a practical tool for product managers to visualize their thinking, make informed decisions, and ensure solutions directly ladder up to strategic objectives.

What is an Opportunity Solution Tree (OST)?

An Opportunity Solution Tree (OST) is a visual framework designed to map the product discovery process, connecting a singular desired outcome to the customer opportunities that drive it, the potential solutions addressing those opportunities, and the experiments to test those solutions. This structured approach, championed by Teresa Torres, helps product managers move beyond simply listing features by clearly articulating the "why" behind product development. It functions as a dynamic visual aid, ensuring that product teams, often a "product trio," maintain focus on overarching objectives and customer needs.

The OST typically consists of four distinct layers:

Layer	Purpose
Outcome	The desired business objective or customer result (e.g., "Increase user engagement by 15%").
Opportunity	The customer needs, pain points, or desires that, if addressed, contribute to achieving the outcome.
Solution	Specific features, products, or services designed to address a particular opportunity.
Experiment	Tests or prototypes to validate assumptions about a solution's effectiveness in addressing an opportunity.

This hierarchical structure forces clarity, ensuring that every proposed solution or experiment directly ladders up to a defined opportunity and, ultimately, the strategic outcome. It helps product managers avoid common pitfalls like debating features without agreeing on the underlying problem or jumping straight to solutions without a clear connection to customer needs.

The Four Layers of an OST

An Opportunity Solution Tree (OST) is precisely structured with four distinct layers, each serving a critical function in connecting product discovery to desired outcomes. The top layer is the Outcome, representing the single, measurable business objective or customer result the team aims to achieve. This is the "why" behind all subsequent work, for example, "Increase user engagement by 15%." Directly beneath this are Opportunities, which are the customer needs, pain points, or desires that, if addressed, will contribute to achieving the specified outcome. This layer is crucial for grounding discussions in evidence, drawing from customer interviews, usage data, and support tickets to identify areas like "Remote workers struggle with productivity due to distractions."

The third layer comprises Solutions, which are the specific features, products, or services designed to address a particular opportunity. For instance, if the opportunity is "Remote workers struggle with productivity," a solution might be a "Focus Mode" feature within a collaboration tool. Finally, the bottom layer consists of Experiments/Assumption Tests. These are the tests or prototypes run to validate assumptions about a solution's effectiveness in addressing an opportunity. This could involve A/B testing different UI elements for the "Focus Mode" or conducting usability studies to see if it genuinely reduces distractions. This structured approach, as emphasized by Teresa Torres, prevents teams from jumping directly to solutions without a clear connection to customer needs or the overarching outcome.

Building and Implementing Your First OST

Constructing your first Opportunity Solution Tree (OST) begins with a clear, measurable Outcome at its root. This objective should be a single, focused aim, such as "Increase user engagement by 15%." Once the outcome is established, the product trio identifies Opportunities—customer needs, pain points, or desires that, if addressed, will contribute to achieving that outcome. This phase heavily relies on continuous discovery practices, utilizing customer interviews, usage data, and support tickets to gather evidence. For example, if the outcome is increased engagement, an opportunity might be "Remote workers struggle with productivity due to distractions." Avoid stating opportunities as disguised features, like "Add tooltips to onboarding."

Next, brainstorm potential Solutions for each identified opportunity. These are specific features or services designed to alleviate the pain point. For the "remote workers struggle with productivity" opportunity, a solution could be a "Focus Mode" feature within a collaboration tool. Finally, design Experiments to validate assumptions about these solutions. This could involve A/B testing different UI elements for the "Focus Mode" or conducting usability studies to determine if it genuinely reduces distractions. Tools like Miro offer templates for visualizing this tree structure, helping product managers connect customer needs directly to potential solutions and ensure every effort ladders up to the strategic outcome. This structured approach helps teams make conscious choices and avoids debating features without understanding the underlying problem.

Strategic Applications and Benefits of OSTs

Opportunity Solution Trees (OSTs) serve as a powerful visual aid for strategic product conversations, moving discussions beyond abstract ideas or premature solutioning. They are instrumental in product strategy debates, PI-level prioritization, discovery workshops, and leadership alignment sessions. By mapping out the journey from a desired outcome to tested solutions, OSTs ensure that every effort connects back to a measurable business objective. For instance, instead of debating features, teams can debate opportunities, and rather than defending specific solutions, they can explore various options to address a customer pain point.

The benefits of integrating OSTs into product development are significant:

Structured Thinking: OSTs provide a clear framework, organizing ideas and prioritizing them effectively. This visualization of relationships among outcomes, opportunities, solutions, and experiments helps product teams maintain focus on overarching goals.
Alignment Across Teams: They ensure that all members, including product managers and the product trio, understand how their work contributes to broader business objectives. This fosters collaboration and helps prevent customer feedback from getting lost between discovery and planning phases.
Continuous Discovery: OSTs are central to continuous discovery practices, as championed by Teresa Torres. They encourage frequent customer engagement to validate ideas and iterate on solutions, ensuring teams focus on why they are building something, not just what. This focus on outcomes, rather than just output, is a key differentiator for high-velocity product teams.

Sustaining and Evolving Your Opportunity Solution Tree

To prevent an Opportunity Solution Tree (OST) from becoming stale, it's crucial to integrate it into a continuous discovery rhythm. A common pitfall is treating the OST as a static artifact rather than a living document. For instance, a 2026 survey of 300 product teams revealed that high-velocity teams distinguished themselves through continuous customer contact and explicit opportunity mapping, not just superior roadmapping tools. This highlights the need for regular engagement.

Strategies for maintaining relevance include:

Weekly Cadence: Establish a weekly review cadence where the product trio (Product Manager, Designer, Engineer) revisits the OST. This allows for continuous refinement of opportunities based on new customer insights, usage data, and market shifts.
Customer-Centric Updates: Actively feed the opportunity space with fresh insights. This means conducting ongoing customer interviews, analyzing support tickets, and observing user behavior. For example, if initial solutions for "remote workers struggle with productivity" aren't gaining traction, new interviews might uncover a deeper opportunity related to "lack of social connection" rather than just "distractions."
Outcome-Driven Adaptations: As the desired outcome evolves or is achieved, the entire OST must adapt. If the initial outcome of "increase user engagement by 15%" is met, the team should then pivot to a new, higher-level outcome, re-evaluating the entire tree from the root. This ensures that the team always focuses on why they are building, not just what.
Leverage AI for Insights: Modern tools can assist in processing large volumes of customer feedback to identify emerging opportunities or validate existing ones, ensuring the OST remains grounded in current customer needs.

By embedding the OST into a dynamic, continuous discovery process, product teams can ensure it remains a powerful visual aid for strategic decision-making and avoids becoming an outdated artifact.

Frequently Asked Questions

What is the purpose of an opportunity solution tree?

The purpose of an opportunity solution tree (OST) is to provide a structured framework for product teams to connect desired business outcomes with potential solutions and experiments, ensuring every effort contributes to a measurable objective. It helps organize ideas, prioritize effectively, and maintain focus on overarching goals.

What are the 4 layers of an opportunity solution tree?

The article describes the layers of an opportunity solution tree as outcomes, opportunities, solutions, and experiments, illustrating the journey from a desired business objective down to specific tests.

Who created the opportunity solution tree?

While the article mentions Teresa Torres as a champion of continuous discovery practices, which are closely linked to OSTs, it does not explicitly state that she created the opportunity solution tree.

How do you create an opportunity solution tree?

Creating an opportunity solution tree involves starting with a desired outcome and then identifying opportunities that could lead to that outcome, followed by exploring various solutions for those opportunities, and finally designing experiments to test those solutions. It's a continuous process that involves regular customer engagement and data analysis.

What is the difference between an opportunity and a solution in an OST?

In an OST, an opportunity represents a customer pain point or unmet need that, if addressed, could lead to the desired outcome, whereas a solution is a specific product feature or offering designed to address that identified opportunity.

How does an OST help with product prioritization?

An OST aids product prioritization by providing a clear visual framework that connects potential solutions directly to desired outcomes, allowing teams to debate opportunities rather than just features and explore various options to address customer pain points effectively.

Conclusion

The opportunity solution tree is more than just a diagram; it's a dynamic framework that empowers product teams to stay customer-centric and outcome-driven. By continuously refining and adapting your OST, you ensure your product development efforts are always aligned with genuine user needs and strategic business goals.

Sources & References

Want to actually learn Product Management?

Curo turns topics like this into a personalized, guided learning board - built around what you already know. Free to start.

Try Curo

Or jump straight in:

opportunity solution tree product discovery product strategy continuous discovery Teresa Torres