← ClaudeAtlas

opportunity-solution-treelisted

Builds a Teresa Torres-style opportunity solution tree that maps customer opportunities to a desired outcome, then to solutions and experiments. Use when the user asks to "build an opportunity solution tree", "map opportunities to our outcome", "OST for X", "structure our discovery", or "what should we focus discovery on". Keeps the team from jumping straight to solutions.
Sidsaladi9/persona-os · ★ 0 · AI & Automation · score 78
Install: claude install-skill Sidsaladi9/persona-os
# Opportunity Solution Tree A visual model from Teresa Torres' *Continuous Discovery Habits* that connects a single desired outcome to the customer opportunities (unmet needs, pains, desires) that could drive it, then to candidate solutions, then to the experiments that test the assumptions each solution rests on. The tree forces a clear line of sight from business outcome to customer problem, and keeps discovery focused on the opportunity space before the solution space. **Grounded in:** *Continuous Discovery Habits* — Teresa Torres: the opportunity solution tree (outcome → opportunities → solutions → experiments). **Go deeper (The Product Channel):** [Jobs-to-be-Done](https://sidsaladi.substack.com/p/week-28-uncover-your-customers-deepest) ## When to use this - You have an outcome to move but aren't sure which customer problem to attack first. - The team keeps debating features before agreeing on the problem. - You've done (or are about to do) customer interviews and need to structure what you heard. - You want to make prioritization defensible — show *why* this opportunity, not that one. - A stakeholder asks "what are we working on and why does it ladder up?" ## The structure - **OUTCOME** — one measurable business or product outcome at the root (e.g. "increase weekly active teams by 15%"). Not a feature, not a vanity metric. One tree, one outcome. - **OPPORTUNITIES** — customer needs, pain points, and desires surfaced from research, phrased as *problems* ("I can't tel