# Opportunity Solution Trees

> How an opportunity solution tree links one goal to user needs, ideas and small tests. Why it stops a team from chasing one idea.

**Course:** [Product Management](https://learn.benibix.com/learn/business-product-management)  
**Time:** 11 min

**After this lesson you can:**

- Draw the four rows of the tree
- Put a need in the right row
- Pick a small test for an idea

## How the tree links a goal to the ideas under it

An opportunity solution tree is a drawing with four rows. The goal sits at the top, such as more weekly users. Under it are the needs found in user talks, called opportunities. Under each need are ideas that might meet it. Under each idea are small tests. Every idea on the page shows which need it serves.

The goal row holds one number the team wants to move. It comes from the strategy, so the tree stays tied to the bigger plan. A team with three goals should draw three trees. A tree with three goals at the top turns into a tangle nobody can read.

The needs row holds problems in the user's own words. I forget to come back. I cannot find old notes. This is where most trees go wrong. People write features here, like add reminders. A feature belongs one row down, because there are always several ways to meet one need.

The ideas row holds the fixes. For I forget to come back, the ideas might be reminders or a weekly summary email. Putting two or three ideas under each need is the whole point. It stops the team falling in love with the first idea someone said in a meeting.

The tests row holds the cheapest way to check each idea. Send reminders to 100 people and count who returns. Show half your users a new screen and half the old one, and compare. That second test is an A/B test. A test that fails is good news, because it was cheap.

The tree also helps with the boss. When someone asks why the team is not building their idea, the product manager can point at the page. Here is the goal, here are the needs we found, and here is where your idea sits. It turns an argument about opinions into a talk about evidence.

![A tree with four labelled rows. The goal at the top reads more weekly users. Two needs hang under it: I forget to come back, and I can't find old notes. Under the first need are two ideas, reminders and weekly summary, and under the second is better search. A test hangs under reminders: send to 100 people.](https://learn.benibix.com/diagrams/opportunity-solution-tree.svg)

### Example: Emma tests reminders first

Emma's goal is more weekly users. Her tree shows two ideas for the need I forget to come back: reminders, at 1 week of work, and a weekly summary, at 4 weeks.

She tests reminders on 1,000 users. 12% of them come back that week, against 8% of a group with no reminder. Reminders ship, and the summary waits.

**Words in this lesson:** [Opportunity Solution Tree](https://learn.benibix.com/term/business/opportunity-solution-tree), [A/B Test](https://learn.benibix.com/term/marketing/ab-test), [Minimum Viable Product (MVP)](https://learn.benibix.com/term/business/minimum-viable-product)

**Question:** Which row of the tree does 'I forget to come back' go in?

**Answer:** The needs row. It is a problem in the user's own words, so it is a need, or opportunity. Reminders, an idea to meet it, would go in the row below.

---

Source: https://learn.benibix.com/learn/business-product-management/opportunity-solution-tree
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
