Opportunity Solution Tree

Opportunity Solution Tree helps you see where the team jumped from the goal right away to their favorite solution. The tree is useful as a living map of choice: the outcome must be measurable, opportunities must be confirmed by needs, and experiments must reduce specific uncertainty to expensive realization.

What is Opportunity Solution Tree?

Definition

Opportunity Solution Tree is a simple visual tool that helps structure problem-finding work to features and solutions. The author of the concept is Teresa Torres. The tree divides the path into three parts: goals, opportunities, solutions, and experiments.

Let’s do it.

You want to increase retention. Instead of digging in features, you draw a tree. At the top, the goal is to retain 30 days. Then there is a branch of user problems: it is difficult to register, little use without a subscription, incomprehensible onboarding. To every problem come ideas of solutions. Next, you plan checks for the most interesting.

How Opportunity Solution Tree Works in Discovery

Procedures for action

1. First, you can define the product goal.
2. You talk to users, you observe, you collect feedback, you look for real problems and situations.
3. Fixing the opportunities found: what interferes, where the frustration, what they would like.
4. For each opportunity, you come up with several different solutions without relying on one idea.
5. Think about quick experiments or MVPs to test the main assumption: will the solution work?

Discovery is often tempted to jump to an idea – but the tree slows down the leap. You always come back to the real problem.

An example from the life of a product

A startup makes a service for the growth of English. The goal of the business level is to increase NPS among new users for the quarter. Through interviews and analytics, you can see that many people lose interest because of monotonous tasks. Problem: boredom. Solutions are hung on the tree - gamification, new types of tasks, competitive elements. The prototype on a small sample quickly shows - gamification with simple badges immediately gives a return on engagement. The rest of the ideas go into the backlog.

When the tree is particularly useful

Moments of growth and uncertainty

You work with a new segment, change your strategy, enter a new market – there is a high risk of doing features for the sake of features. The tree helps you not get lost.

Anti-patterns

1. There is no purpose, no reason to make a tree.
2. Only one or two opportunities means that I didn’t look at the problems well.
3. Decisions duplicate each other – creativity is at zero, you need to assemble a team and go beyond your opinion.

How to Make the Most of Opportunity Solution Tree

Bring in the whole team.

Brainstorm together, bring in designers, analysts and even support people. Everyone brings their own vision of problems.

Don’t be afraid to change a tree

There was new data — reworked branches. This is not a bureaucracy, but a working tool.

Keep the tree alive

Use it on weekly syncs, show it to stakeholders to explain priorities. Some teams integrate the East into Confluence, Miro or FigJam as a live Discovery map.

Useful materials and references

• Product Talk: Opportunity Solution Trees
• Mind the Product: How to use Opportunity Solution Trees to build better products
• Teresa Torres: Continuous Discovery Habits

FAQ

**What is the difference between OST and regular Mindmapping? OST always associates solutions with clearly articulated problems and business goals, as opposed to idea feeds.

OST only works for product teams? Suitable for marketing, service teams, startups of any scale.

**How do you know if you have a strong opportunity? There are clear patterns in user feedback, the metric shows a negative trend, the team believes in it.

*When is the tree not needed? If the task is just to refine the feature on a bug report or there is a clear market and clear recipes.

How to work with a tree when you have little time? Use quick User Interview, short calls and support materials – already a cape of 3-5 branches helps you to choose a vector.

What if there are many ideas and few experiments? Prioritize through ICE, RICE, or another simple framework and start validating not the ones that the team likes, but the ones that really fit the metric.