Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Planowanie

opportunity-solution-tree

/opportunity-solution-tree

Buduje drzewo szans i rozwiązań wg Teresy Torres: od mierzalnego celu do szans, kilku rozwiązań i testów założeń.

Repozytorium
skilldeck ↗
Licencja
MIT
Ostatnia zmiana repozytorium
09.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 09.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Buduje drzewo szans i rozwiązań wg Teresy Torres: od mierzalnego celu do szans, kilku rozwiązań i testów założeń.

Oryginalny opis (EN)

Build and use an opportunity solution tree (as described by Teresa Torres) that links one measurable product outcome to customer opportunities from research, several candidate solutions per target opportunity, and assumption tests for each solution. Use when a team needs to move from a goal to what to explore next without jumping to a single favourite feature, or to make discovery reasoning visible to stakeholders.

Jak działa

  1. When to use
  2. Inputs
  3. Procedure
  4. Expected output
  5. Constraints and limitations
  6. Examples
Sekcje z nagłówków SKILL.md, w oryginale · 72 linii, 873 słów
Podgląd SKILL.md
---
name: opportunity-solution-tree
description: Build and use an opportunity solution tree (as described by Teresa Torres) that links one measurable product outcome to customer opportunities from research, several candidate solutions per target opportunity, and assumption tests for each solution. Use when a team needs to move from a goal to what to explore next without jumping to a single favourite feature, or to make discovery reasoning visible to stakeholders.
---

# Opportunity Solution Tree

The opportunity solution tree (OST), popularized by Teresa Torres in continuous discovery practice, is a visual structure with four levels: a desired **outcome** at the root, **opportunities** (customer needs, pain points, and desires discovered through research) beneath it, **solutions** that address a chosen opportunity, and **assumption tests** that evaluate those solutions. It keeps teams honest about why they are building something and makes it natural to compare options instead of committing to the first idea.

## When to use

- A team has been given an outcome (for example "increase weekly active teams") and needs to decide what to explore.
- Stakeholders bring feature requests and the team needs to place them in context.
- Discovery work feels scattered and needs a shared map.
- Choosing which opportunity to target next quarter.

Not for: delivery planning or effort estimation, ranking a backlog of already-defined features (use a scoring method such as `rice-prioritization`), or when no customer research exists — then the first step is research, and the tree remains a hypothesis sketch.

## Inputs

- One outcome, ideally a product outcome the team can influence (a behavior metric), with current value if known. Required.
- Research evidence: interview snapshots, synthesis, support data, analytics. Required for opportunities to be credible.
- Existing ideas or requests the team is considering. Optional.

## Procedure

1. **Set the outcome.** Choose one product outcome the team can directly influence, phrased as a metric with direction ("increase the share of new workspaces that create a second project within 14 days"). Push business outcomes (revenue) down to product outcomes (behavior that drives revenue). One tree per outcome.
2. **Collect opportunities from research.** Write opportunities as customer needs, pain points, or desires in the customer's words, not as solutions: "I don't know which template fits my project", not "add template recommendations". Each opportunity should cite its research source. Use JTBD outcomes from `jobs-to-be-done-analysis` if available.
3. **Structure the opportunity space.** Group opportunities into parent and child nodes: broad needs at the top, more specific ones beneath. A useful framing is to map them to stages of the customer's experience. Children should be distinct and, ideally, each solvable on its own. Re-check that every opportunity plausibly drives the outcome.
4. **Assess and choose a target opportunity.** Compare sibling opportunities by: how many customers are affected and how often (sizing), how much it matters to them, market factors (competitive gap or table stakes), and company factors (strategic fit, team strength). Pick the target among siblings rather than across the whole tree; specific child opportunities are easier to solve. Record why.
5. **Generate multiple solutions.** For the target opportunity, generate at least three distinctly different solutions. Diverge before converging; include a low-tech or non-software option. Avoid committing to the first idea.
6. **Identify assumptions for each solution.** Using story mapping or a walk-through of how the solution would work, list assumptions across desirability, viability, feasibility, usability, and ethics. Mark the riskiest.
7. **Design small assumption tests.** For the riskiest assumptions across the competing solutions, design quick tests (prototype tests, one-question surveys, data mining, small simulations) with a pre-stated success criterion. Compare solutions by test results, not by enthusiasm.
8. **Iterate the tree.** Update weekly as interviews add opportunities and tests retire solutions. Keep a dated change log so the reasoning stays visible.

## Expected output

```markdown
## Opportunity Solution Tree — <outcome> (baseline: <value>, <date>)

Outcome: <metric with direction>
├── Opportunity: <need in customer words> [evidence: P3, P8, tickets]
│   ├── Opportunity: <child need> [evidence ...]  <- TARGET (why: ...)
│   │   ├── Solution A: ...
│   │   │   └── Test: <assumption> — <method> — success if <criterion>
│   │   ├── Solution B: ...
│   │   │   └── Test: ...
│   │   └── Solution C: ...
│   │       └── Test: ...
│   └── Opportunity: ...
└── Opportunity: ...

### Target opportunity rationale
| Opportunity | Sizing | Customer importance | Market | Company fit | Decision |

### Change log
- <date>: ...
```

A Mermaid flowchart (`graph TD`) rendering is fine where supported.

## Constraints and limitations

- Opportunities must come from evidence; unevidenced ones are marked hypothesis.
- Never phrase opportunities as solutions; rewrite them.
- One outcome per tree. Several outcomes mean several trees.
- The tree guides discovery; it does not replace a roadmap or delivery plan.

## Examples

Outcome: increase the share of trial users who connect a data source in their first 3 days (baseline 31%).
Opportunities from 11 interviews: "I'm not sure my data is clean enough to connect" (P2, P5, P9); "I need IT approval to connect our warehouse" (P1, P4, P7, P10); "I want to see what the dashboards look like before connecting anything" (P3, P6).
Target: the IT-approval child opportunity — affects 4 of 11, blocks activation entirely, and competitors handle it poorly.
Solutions: A) a shareable security summary for IT; B) a read-only sample connection using a demo warehouse; C) an "invite your IT admin" flow with a pre-filled request.
Riskiest assumption for A: IT admins accept a vendor summary instead of a full questionnaire. Test: send the summary draft to 5 IT contacts from recent deals; success if 3 say it would be enough to approve a trial.
Pliki w paczce (2)
  • SKILL.md 6 KB
  • manifest.yaml 2 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · seyhunak/skilldeck100MIT
avelikiy/great_cto100MIT
drvoss/everything-copilot-cli100MIT
borghei/Claude-Skills100MIT
qa-aman/claude-skills100MIT
Sidsaladi9/persona-os100MIT
tarunccet/pm-skills100MIT
kaminoikari/product-playbook100MIT
getcrew44/crew44100MIT

Migawka bazy z 13.11.2026 · wersja paczki a72ebc3eab88 (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.
  • 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.
  • 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.
  • 100product-discovery-assistant
    Prowadzi strukturalne discovery produktu z użyciem Opportunity Solution Tree Teresy Torres: wyniki, szanse, rozwiązania i eksperymenty.
  • 100product-discovery
    Zamienia pożądany wynik i dane w drzewo rozwiązań, mapę założeń na czterech polach i trzy najtańsze eksperymenty do sprawdzenia w kolejności.
  • 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.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.