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

opportunity-solution-tree

/opportunity-solution-tree

Tworzy Opportunity Solution Tree na podstawie Continuous Discovery Habits Teresy Torres: mapuje oczekiwany wynik na możliwości, rozwiązania i eksperymenty, by zdecydować, co budować dalej.

Repozytorium
pm-skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
23.08.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
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 23.08.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

Tworzy Opportunity Solution Tree na podstawie Continuous Discovery Habits Teresy Torres: mapuje oczekiwany wynik na możliwości, rozwiązania i eksperymenty, by zdecydować, co budować dalej.

Oryginalny opis (EN)

Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when structuring discovery work, mapping opportunities to solutions, or deciding what to build next.

Jak działa

  1. Opportunity Solution Tree (OST)
Sekcje z nagłówków SKILL.md, w oryginale · 77 linii, 721 słów
Podgląd SKILL.md
---
name: opportunity-solution-tree
description: "Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when structuring discovery work, mapping opportunities to solutions, or deciding what to build next."
---

## Opportunity Solution Tree (OST)

A visual framework for structuring continuous product discovery. Connects a desired **outcome** to customer **opportunities**, possible **solutions**, and **experiments** to validate them.

### What You'll Need
| Input | Required? | Example |
|-------|-----------|---------|
| Desired outcome (measurable) | ✅ Required | "Increase 7-day retention from 28% to 40%" |
| Product description | ✅ Required | B2B collaboration tool, enterprise segment |
| Customer research / known pain points | 🟡 Recommended | Interview themes, NPS feedback, churn exit surveys |
| Existing solution ideas to evaluate | ⚪ Optional | Feature backlog, team ideas |

> **Don't have everything?** Start anyway — the skill will work with what you provide and flag where richer input would improve the output.

### Domain Context

The **Opportunity Solution Tree** (Teresa Torres, *Continuous Discovery Habits*) is the backbone of modern product discovery. It prevents teams from jumping to solutions by forcing them to first map the opportunity space.

**Structure (4 levels):**

1. **Desired Outcome** (top) — The measurable business or product outcome the team is pursuing. Should be a single, clear metric (e.g., "increase 7-day retention to 40%"). This comes from your OKRs or product strategy.

2. **Opportunities** (second level) — Customer needs, pain points, or desires discovered through research. These are problems worth solving — not features. Frame them from the customer's perspective: "I struggle to..." or "I wish I could..." Prioritize using Opportunity Score: **Importance × (1 − Satisfaction)** (Dan Olsen, *The Lean Product Playbook*). Normalize Importance and Satisfaction to 0–1.

3. **Solutions** (third level) — Possible ways to address each opportunity. Generate multiple solutions per opportunity — don't commit to the first idea. The **Product Trio** (PM + Designer + Engineer) should ideate together. "Best ideas often come from engineers."

4. **Experiments** (bottom) — Fast, cheap tests to validate whether a solution actually addresses the opportunity. Use assumption testing (Value, Usability, Viability, Feasibility risks). Prefer experiments with "skin-in-the-game" (Alberto Savoia) over opinion-based validation.

**Key principles:**

- **One outcome at a time.** Don't try to solve everything. Focus the tree on a single desired outcome.
- **Opportunities, not features.** "Never allow customers to design solutions. Prioritize opportunities (problems), not features."
- **Compare and contrast.** Always generate at least 3 solutions per opportunity before choosing. Avoid the "first idea" trap.
- **Discovery is not linear.** Loop back if experiments fail. Kill solutions that don't validate. Explore new branches.
- **Continuous, not periodic.** Update the tree weekly as you learn from interviews, analytics, and experiments.

### Instructions

You are helping a product team build an Opportunity Solution Tree for **$ARGUMENTS**.

### Phase 0: Context Confirmation

Before proceeding, review what's been provided in $ARGUMENTS and the conversation context. **Only ask about what's missing — don't re-ask what's already clear.**

1. **Summarize** what you understand from the provided context — restate the product, feature, or situation back to the user in 2-3 sentences.
2. **Identify gaps** — if any of the following are unclear, ask:
   - What is the desired outcome (the metric the team owns)?
   - What research data is available (interview transcripts, survey data, analytics)?
   - Has opportunity mapping been done before for this area?
3. **Confirm**: _"Here's my understanding: [summary]. I plan to [brief description of what the skill will produce]. Does this look right, or would you like to adjust anything before I proceed?"_

If the user provides additional context, incorporate it. If the user confirms, proceed.

### Input Requirements
- A desired outcome or business metric to improve
- Customer research data (interviews, surveys, analytics, feedback)
- Optionally: existing opportunities or solution ideas to organize

### Process

1. **Define the desired outcome** — Confirm or help articulate a single, measurable outcome at the top of the tree.

2. **Map opportunities** — From provided research, identify 3-7 customer opportunities (needs/pains). Group related opportunities. Frame each from the customer's perspective.

3. **Prioritize opportunities** — Use Opportunity Score or qualitative assessment to rank. Focus on the top 2-3.

4. **Generate solutions** — For each prioritized opportunity, brainstorm 3+ solutions from PM, Designer, and Engineer perspectives.

5. **Design experiments** — For the most promising solutions, suggest 1-2 fast experiments. Specify: hypothesis, method, metric, success threshold.

6. **Visualize the tree** — Present the full OST in a clear hierarchical format.

Think step by step. Save as markdown if substantial.

---

Wersje

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

Migawka bazy z 13.11.2026 · wersja paczki 6cd4ff87ac4d (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.
  • 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.
  • 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.
  • 100create-ost
    Generuje Opportunity Solution Tree łączące rezultaty z szansami, rozwiązaniami i eksperymentami, do planowania ciągłego discovery.
  • 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.

Uwagi i zgłoszenia

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