One challenge I’ve seen in product teams is that the path from a business goal to a product decision can become surprisingly messy.

Leadership sets an outcome.

Customers raise problems.

Stakeholders suggest features.

Someone has an idea in a meeting.

Before long, the roadmap becomes a collection of solutions without a clear connection to the outcome we’re trying to achieve.

An Opportunity Solution Tree can help bring that thinking together.

What Is an Opportunity Solution Tree?

An Opportunity Solution Tree is a visual way to connect four things:

Outcome → Opportunities → Solutions → Experiments

The structure helps product teams move from a desired outcome to the customer problems that could influence it, then explore different ways to address those problems.

The important part is that solutions don’t sit at the top.

They come after opportunities have been understood.

Start With the Desired Outcome

At the top of the tree is the outcome you’re trying to influence.

For example:

Increase successful assessment completion.

This gives the team a clear direction.

Without an outcome, teams can generate dozens of ideas without knowing which ones matter.

The outcome also provides a way to evaluate opportunities and solutions later.

If an idea doesn’t have a plausible connection to the outcome, it deserves closer scrutiny.

Identify the Opportunities

Opportunities represent customer needs, problems, or unmet needs that could help influence the outcome.

For example, customers might struggle with:

• Understanding what they need to do next
• Completing a complicated workflow
• Recovering from errors
• Finding important information
• Getting help when they’re stuck

These are more useful than jumping straight to feature requests.

If a customer says, “We need a guided workflow,” the opportunity might actually be that users don’t know how to complete the process confidently.

That distinction matters.

Explore Multiple Solutions

Once you’ve identified an opportunity, explore different ways to address it.

Suppose the opportunity is:

Users struggle to understand what to do next.

Possible solutions could include:

• Better contextual guidance
• A redesigned workflow
• Progress indicators
• Improved defaults
• A guided experience
• In-product recommendations

This is where the tree prevents premature commitment.

Instead of saying, “Let’s build a guided tour,” you’re asking, “What are the different ways we could solve this problem?”

Use Experiments to Reduce Risk

The final layer is experimentation.

You don’t necessarily need to build every solution fully before learning whether it works.

You could prototype the workflow.

Run usability testing.

Conduct a small beta.

A/B test a change.

Use a concierge approach.

The experiment should help answer an important question about the solution.

This makes the tree less about documenting ideas and more about managing uncertainty.

Keep Multiple Paths Alive

One of the most useful aspects of an Opportunity Solution Tree is that it allows multiple possibilities to exist at the same time.

You don’t have to decide immediately which solution will win.

You can explore different solutions against the same opportunity and learn which one appears most promising.

This is particularly useful during discovery, when certainty is low.

Don’t Turn the Tree Into a Roadmap

An Opportunity Solution Tree isn’t a backlog.

Not every solution on the tree needs to be built.

Some will be tested and rejected.

Some will become less important as you learn more.

Some opportunities may turn out not to matter.

That’s a feature, not a problem.

The tree should evolve as your understanding changes.

Keep the Customer Problem Visible

One risk with product roadmaps is that teams can lose sight of why something is being built.

Six months later, everyone remembers the feature but forgets the problem.

An Opportunity Solution Tree keeps the connection visible.

Outcome → Customer opportunity → Solution → Evidence

That chain makes product decisions easier to explain and challenge.

Final Thought

The real value of an Opportunity Solution Tree isn’t the diagram itself.

It’s the thinking it encourages.

Start with the outcome.

Understand the customer opportunities connected to it.

Explore multiple solutions.

Test assumptions before making large commitments.

A roadmap tells you what you’re planning to build.

An Opportunity Solution Tree helps explain why those solutions are worth exploring in the first place.