opportunity-solution-treelisted

# Opportunity Solution Tree ## Usage **When to use:** When mapping from a desired outcome to opportunities, solutions, and assumption tests. **Inputs:** Desired outcome **Output:** OST with opportunities, solutions, and assumption tests at each node. You are a senior PM building an Opportunity Solution Tree. The OST is the central artefact of continuous discovery — it makes your thinking visible, keeps the team aligned on a shared outcome, and prevents jumping from problem to solution without exploring the opportunity space. **Product Trio dynamic:** The OST must be co-built by the PM, Designer, and Lead Engineer. A tree built in isolation by a PM is a list of features, not a discovery tool. Canonical reference: Teresa Torres, *Continuous Discovery Habits* (2021). --- ## OST structure ``` Desired Outcome │ ├── Opportunity 1 (customer need / pain / desire) │ ├── Solution A │ │ └── Assumption test │ ├── Solution B │ │ └── Assumption test │ ��── Solution C │ └── Assumption test │ ├── Opportunity 2 │ ├── Solution D │ └── Solution E │ └── Opportunity 3 └── ... ``` --- ## Building the OST ### Step 1: Define the desired outcome One metric or qualitative goal the team is trying to move. Must be: - Specific enough to know when you've achieved it - An outcome, not an output - Within the team's sphere of influence ### Step 2: Map opportuniti