Gumshoe · Method reference

Opportunity solution trees

Connect a desired outcome to the opportunities that drive it and the solutions that address them.

Conceptual illustration of opportunity solution trees.
Effort
Medium
Participants
Not required
Remote friendly
Yes
Evidence / output
Direct user

What it is

A visual tree (after Teresa Torres) linking a target outcome at the top to user opportunities (needs, pains, desires) beneath, then to candidate solutions and the experiments that test them. It keeps discovery and delivery connected.

When to use it

During Synthesize and Ideate, in continuous discovery, when mapping how solutions ladder up to an outcome.

Why (value)

Prevents disconnected feature ideas by tracing every solution to a real opportunity and a measurable outcome, and makes prioritization explicit.

How to run it

  1. State the desired outcome at the top.
  2. Branch into distinct user opportunities drawn from research.
  3. Under each opportunity, brainstorm candidate solutions.
  4. Under solutions, list experiments to test them.
  5. Prioritize a branch and iterate as you learn.

Inputs and outputs

  • Inputs: A clear outcome and research-based opportunities.
  • Outputs: An opportunity solution tree guiding prioritized discovery.

Time and effort

Medium. Built and refined over a discovery cycle.

Evidence and limitations

The opportunities should be direct-user evidence from research; solutions and experiments are hypotheses until tested. Keep the layers honest about which is which. See Evidence and limitations.

Tips and pitfalls

  • Root opportunities in real research, not guesses.
  • Keep opportunities distinct, avoid overlap.
  • Explore one branch deeply rather than everything shallowly.

Variations

Continuous discovery trees, outcome-opportunity-solution maps.

Need help choosing and applying a method?

Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.

Discuss your project with Gumshoe Explore Gumshoe services

Sources and further reading

Explore related methods

  • Jobs-to-be-done framing — Frame what people are trying to accomplish, and why, rather than what features they ask for.
  • How-might-we framing — Reframe a problem as an open, optimistic question that invites many solutions.
  • Assumption mapping — Surface the beliefs a plan depends on and sort them by risk so you test the scariest ones first.

A general practice reference. This page does not establish that a method was used on a particular client project or that an outcome was measured.