Back to the Playbook
Strategy & DiscoverySD-08
How to map an opportunity solution tree
Keep the tree rooted in one outcome and evidence-backed opportunities; solutions remain alternatives until tested.
Product statusAvailable now
Input3 required inputsProduct outcome and the team’s remit · Customer research · Initiative focus and approved Product Brain guidance
SkillsMap an opportunity solution tree · Prepare task contextProduct Manager + Product Manager Agent
OutcomeOpportunity solution tree: outcome, evidenced opportunity branches, solution alternatives, assumptions and proposed tests.Artifact: Opportunity solution tree
Owner
Product Manager
Human + Agent
Participants · Agents
ResearcherDesignerEngineerProduct Manager Agent
Trigger
A product outcome and candidate opportunities or solutions exist.
Required context
Product BrainProduct outcome and the team’s remitCustomer evidenceCustomer researchProduct BrainInitiative focus and approved Product Brain guidance
Optional context
JiraExisting solution ideas and ticketsFilesTest records
Skills
Map an opportunity solution treePrepare task context
Suggested conversation arc
- 1Agree the outcome rootChoose one measurable outcome within the team’s remit and clarify the customer group; do not begin with a favoured feature as the root.Skills: Prepare task context
- 2Map evidenced opportunitiesCreate opportunity branches from customer needs and pain, attaching research evidence and explicit gaps. Keep solutions separate from opportunity statements.Skills: Map an opportunity solution tree
- 3Explore alternative solutionsChoose an opportunity to examine and compare several ways to address it, including key assumptions and constraints.
- 4Connect assumptions and testsExtend the tree with assumptions and proposed tests; record which evidence would prompt a branch revision without implying the tests have run.Skills: Map an opportunity solution tree
Output
Opportunity solution tree: outcome, evidenced opportunity branches, solution alternatives, assumptions and proposed tests.
Artifacts
Creates: Opportunity solution tree
What good looks like
- Opportunities are grounded in customer evidence.
- Solutions and tests remain separate from needs and outcomes.
- Imagined tests are never labelled as completed.
Quality gate
The Product Manager chooses the opportunity to pursue and the first assumptions to test.
Destination
Product BrainConfluence
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Choose the path that matches your role.
Set the Product AI direction with us, or test the shared Product Brain on real work with Jira and code.