opportunity-solution-tree
/opportunity-solution-tree
Łączy każdą funkcję z backlogu z mierzalnym wynikiem biznesowym według drzewa szans i rozwiązań Teresy Torres, od wyników przez szanse i rozwiązania do eksperymentów.
- Autor
- drvoss ↗
- Repozytorium
- everything-copilot-cli ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 25.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 25.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Łączy każdą funkcję z backlogu z mierzalnym wynikiem biznesowym według drzewa szans i rozwiązań Teresy Torres, od wyników przez szanse i rozwiązania do eksperymentów.
Oryginalny opis (EN)
Use when you need to ensure every feature in the backlog connects to a measurable business outcome — applies Teresa Torres' OST framework to map outcomes → opportunities → solutions → experiments.
Jak działa
- The Framework
- Workflow
- SQL Tracking
- Example: SaaS Conversion OST
- Tips
Podgląd SKILL.md
---
name: opportunity-solution-tree
description: Use when you need to ensure every feature in the backlog connects to a measurable business outcome — applies Teresa Torres' OST framework to map outcomes → opportunities → solutions → experiments.
metadata:
category: product
---
# Opportunity Solution Tree (OST)
Teresa Torres' **Opportunity Solution Tree** prevents building features that don't
matter. It ensures every solution you build is connected to a real user pain
and a business outcome you care about.
## The Framework
```text
Desired Outcome
└── Opportunity 1 (user pain / unmet need)
│ ├── Solution A
│ │ ├── Experiment 1
│ │ └── Experiment 2
│ └── Solution B
└── Opportunity 2
└── Solution C
```
**Outcome**: A measurable business goal (OKR-level: "Increase trial-to-paid conversion by 15%")
**Opportunity**: A user pain, unmet need, or desire (discovered through research)
**Solution**: A product change that might address the opportunity
**Experiment**: The smallest thing you can build to test if the solution works
## Workflow
### Step 1: Define the Desired Outcome
```text
> I'm building the OST for: [product/feature area]
>
> Help me define 1 crisp desired outcome. It should be:
> - Measurable (has a metric)
> - Achievable within the quarter
> - Aligned with business goals
>
> Context: Our goal is [business context]. Key metric: [current baseline].
```
Keep one outcome metric, then decompose it into two to four leading input metrics the team can move
weekly. The outcome is usually lagging; for each input, state the causal contribution you expect
and how the team can influence it. This preserves one outcome at a time while allowing several
diagnostic and actionable inputs beneath it.
### Step 2: Map the Opportunity Space
```text
> Now let's map the opportunity space for this outcome.
>
> Based on [user research / support tickets / interview data / NPS feedback]:
> > [paste data here]
>
> Identify the top 5-7 user opportunities (pains, needs, desires) that, if addressed,
> would most directly improve [outcome metric].
>
> Format as a prioritized list with a one-sentence "when I [situation], I struggle to [pain]" statement for each.
```
### Step 3: Generate Solutions
For each top opportunity:
```text
> For the opportunity: "[opportunity statement]"
>
> Generate 5-7 possible solutions. Include:
> - Conventional solutions (what everyone would build)
> - Lateral solutions (unexpected approaches)
> - Low-tech or process solutions (not just feature builds)
>
> For each, estimate: effort (S/M/L), confidence (Low/Med/High), impact potential (Low/Med/High)
```
### Step 4: Design Experiments
For your top-priority solution:
```text
> For solution: "[solution name]"
>
> Design 3 experiments to test the core assumption, ordered from least to most expensive:
> 1. A concierge experiment (manual, no code)
> 2. A fake door / prototype test
> 3. An MVP build
>
> For each experiment, define:
> - The hypothesis: "We believe [solution] will [expected outcome] because [reason]"
> - The success metric
> - The time box
```
### Step 5: Build the Tree Visualization
```text
> Generate a Markdown-formatted OST for:
>
> Outcome: [outcome]
> Opportunities: [list]
> Solutions per opportunity: [list]
> Experiments for priority solution: [list]
>
> Use nested Markdown lists with clear labels for each level.
> Add a "Current Focus" indicator on the solution we're pursuing.
```
## SQL Tracking
Use the session database to track OST items:
```sql
CREATE TABLE ost_items (
id TEXT PRIMARY KEY,
type TEXT, -- outcome | opportunity | solution | experiment
parent_id TEXT,
title TEXT,
status TEXT DEFAULT 'active',
metric TEXT,
notes TEXT
);
INSERT INTO ost_items VALUES
('O1', 'outcome', NULL, 'Increase trial-to-paid conversion 15%', 'active', 'trial_conversion_rate', ''),
('OP1', 'opportunity', 'O1', 'Onboarding takes too long to first value', 'active', NULL, ''),
('S1', 'solution', 'OP1', 'Progressive disclosure of features', 'active', NULL, ''),
('E1', 'experiment', 'S1', 'Show only 3 steps to first task', 'in_progress', 'time_to_first_task', '');
```
## Example: SaaS Conversion OST
```text
Outcome: Increase trial-to-paid conversion rate from 12% to 18%
Opportunity 1: Users don't reach the "aha moment" before trial ends
Solution A: Personalized onboarding based on role
Experiment 1: Wizard with role selection (concierge test, 1 week)
Experiment 2: Role-based dashboard (2-week MVP)
Solution B: Proactive success manager outreach at day 3
Opportunity 2: Users don't trust us with their real data during trial
Solution A: Pre-loaded demo data matching user's industry
Solution B: "Import 10 rows free" limited trial import
Opportunity 3: Trial users don't share product with team
Solution A: Collaborative invitation flow mid-trial
```
## Tips
- **One outcome at a time**: A single team can only optimize one metric at a time. Multiple outcomes = diffused focus.
- **Separate opportunity discovery from solution generation**: Don't jump to solutions before mapping pains.
- **Experiments > builds**: The goal is to learn cheaply. Most solutions shouldn't become builds.
- **Continuous tree**: OST is a living document. Update it weekly as you learn.
- **Start with existing data**: Support tickets, NPS verbatims, and session recordings are free opportunity maps.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · drvoss/everything-copilot-cli | 100 | MIT |
| avelikiy/great_cto | 100 | MIT |
| borghei/Claude-Skills | 100 | MIT |
| seyhunak/skilldeck | 100 | MIT |
| qa-aman/claude-skills | 100 | MIT |
| Sidsaladi9/persona-os | 100 | MIT |
| tarunccet/pm-skills | 100 | MIT |
| kaminoikari/product-playbook | 100 | MIT |
| getcrew44/crew44 | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 1f1a1ee6e48b (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100pm-opportunity-tree
Prowadzi przez budowę drzewa okazji i rozwiązań Teresy Torres: od celu przez obszar okazji i rozwiązania po eksperymenty. - 100product-discovery-assistant
Prowadzi strukturalne discovery produktu z użyciem Opportunity Solution Tree Teresy Torres: wyniki, szanse, rozwiązania i eksperymenty. - 90opportunity-solution-trees
Pomaga zespołom produktowym łączyć cele z szansami klientów i testować rozwiązania za pomocą drzew szans i rozwiązań Teresy Torres. - 100prd-v10-continuous-discovery-torres
Ustanawia cotygodniowy rytm rozmów z klientami i praktykę drzewa Opportunity Solution Tree według Continuous Discovery Habits Teresy Torres w PRD v1.0. - 90product-opportunity-tree
Mapuje mierzalny wynik produktowy na szanse klientów, opcje rozwiązań i testy założeń, budując drzewo szans i rozwiązań do planowania discovery. - 100create-ost
Generuje Opportunity Solution Tree łączące rezultaty z szansami, rozwiązaniami i eksperymentami, do planowania ciągłego discovery.