Skip to main content
Next Step PM
Back to the library

Discover · Core · Go further

Map opportunities with an opportunity solution tree

An opportunity solution tree links one outcome to the user needs that could drive it, the ideas that could meet each need and the tests that check each idea. It keeps the team focused on outcomes rather than a list of features.

About 4-8 hoursEvergreenLast reviewed 5 November 2026

Who this applies to

Skills it builds
Discovery and researchPrioritisation and roadmapping
PM types
All
Product types
All
Starting points
All
Ways of working
All
Experience
Intermediate (1 to 4 years)Experienced (5+ years)
Size of organisation
All

Steps, by experience

Beginner (under 1 year)

  1. Put your desired outcome at the top of a board.
  2. Under it, add the user needs, pain points and desires you found in research. These are opportunities. Write them from the user's point of view.
  3. Group related opportunities and break big ones into smaller, more specific ones.
  4. Pick one opportunity to focus on, based on size and evidence.
  5. Under it, list at least three different solution ideas.
  6. Under each idea, list the assumptions that must be true, and a quick test for the riskiest one.

Intermediate (1 to 4 years)

  1. Set the outcome at the top and map research-backed opportunities beneath it.
  2. Structure opportunities into a tree and choose a target opportunity.
  3. Generate at least three solutions for it and identify the riskiest assumptions.
  4. Keep the tree updated weekly as you learn.

Experienced (5+ years)

  1. Use the tree to make prioritisation visible to stakeholders and to defend outcome-led choices.
  2. Compare and contrast solutions rather than testing one idea at a time.
  3. Prune branches as evidence comes in and record why.
  4. Coach the team to use the tree in planning and review conversations.

Who can do this

Owner: Product manager

Can be delegated to

  • User Researcher: Supply the opportunities from research and check their wording
  • UX Designer: Generate solution ideas for the target opportunity

Reviewed by: Tech Lead

Tool examples

Miro
Use an opportunity solution tree template and colour-code opportunities by strength of evidence.
Mural
Build the tree live with the team and use voting to choose the target opportunity.
Notion
Keep each opportunity as a page with linked research notes, so the tree stays traceable.

Definition of done

  • Outcome, opportunities, solutions and assumption tests mapped on one tree
  • Target opportunity chosen with a reason
  • At least three solutions for the target opportunity

Common pitfalls

  • Writing solutions in the opportunity layer
  • Building the tree once and never updating it
  • Only listing one solution per opportunity

If you lead the team

What good looks like: Every idea links back to a user need and an outcome, so teams can explain why they're working on it.

Ask your PM

  • Which outcome does this idea serve, and which user need?
  • What other ideas did we consider for the same need?

Warning signs

  • Ideas go straight to the backlog without a link to an outcome.
  • Only one solution is ever considered per problem.

Do these first

Sources