Opportunity-Solution Tree

A visual map that connects a desired outcome to the work that might achieve it: the outcome sits at the top, branches into the customer opportunities (needs, pains, and desires) that could move it, each opportunity branches into candidate solutions, and each solution into the assumption tests that would validate it. It makes the path from goal to experiment explicit and keeps a team's many ideas organized under the outcome they serve.

Why it Matters

Teams jump from a goal straight to a favorite solution, with the reasoning left implicit and unexamined. Laying the structure out as a tree forces the opportunities into view before solutions, shows which need a given idea actually serves, and reveals when every idea is crowded under one opportunity while others go unaddressed. It turns discovery from a list of features into a navigable space of choices.

Signals

• A roadmap of solutions with no visible link to the outcome or the customer need each serves.
• Several competing ideas argued in the abstract, with no shared picture of how they relate.
• An outcome pursued through a single opportunity while others are never considered.

Benefits

A shared map of the discovery space, explicit reasoning from outcome to experiment, and a way to see gaps, compare opportunities, and decide where to focus rather than defending one idea.

Risks

A tree built once and left static instead of evolving with learning; mistaking a tidy diagram for real customer understanding; over-structuring exploratory work.

Tensions

The map imposes structure on messy, evolving understanding, so it must be revised constantly to stay honest; a beautiful tree can give false confidence that the thinking is done.

Examples

An outcome like reducing churn branching into distinct customer pains, each with two or three candidate solutions and the riskiest assumption under each laid out to test.