Opportunity solution tree
Connects a desired outcome to the customer opportunities that could produce it, and then to specific solutions. Stops teams jumping straight from a goal to a feature list.
The printable canvas and the handoff into Claude Code are part of a paid plan. See what a plan includes. It needs the Claude desktop app on this machine, and your team and the prompt library already installed in that project — we cannot see your disk, so open it there.
What it is
Teresa Torres's structure for product discovery: a desired outcome at the top, branching into customer opportunities, each branching into candidate solutions and then experiments. It exists to make the reasoning from goal to feature visible and challengeable.
- Outcome
- One measurable business result the team is responsible for moving. Singular by design.
- Opportunities
- Customer needs, pain points and desires that, if addressed, would move the outcome. Drawn from research, not from ideation.
- Solutions
- Candidate ways to address a chosen opportunity. Several per opportunity, because the first idea is rarely the best one.
- Experiments
- How you would test whether a solution actually delivers, before building it fully.
- The chosen branch
- Which opportunity the team is working now. The tree's purpose is to make that a visible choice with visible alternatives rather than an implicit one.
How you run it
- Start with one outcomeA single measurable business result. Multiple outcomes produce a thicket rather than a tree, and nothing gets prioritised.
- Map opportunities from research, not imaginationOpportunities are customer needs, pains and desires that you have actually heard. Inventing them makes the whole structure decorative.
- Group and structure themOpportunities nest — broad ones contain narrower ones. Structuring reveals which are genuinely distinct and which are restatements.
- Choose one opportunity to targetThis is the actual decision. Working several branches at once is how discovery becomes a backlog.
- Generate several solutions per opportunityAt least three. The first solution to any opportunity is rarely the best, and comparing three forces the reasoning into the open.
The prompt
Run this tool in your own Claude
The short prompt starts your partner against the library on your disk. The long one carries everything with it and needs nothing installed.
Your playbook
It lands in the earliest stage this tool suits. Move it on the Playbook page.
You’ll need
- One measurable outcome, not several
- Real customer research — this needs evidenced opportunities
- A team that will actually work the tree over time
You’ll end up with
- A tree from outcome through opportunities to solutions
- The opportunity chosen for this cycle, with a reason
- Experiments defined against the chosen branch