JobCannon
Tutte le competenze

Opportunity Solution Trees

⬢ LIVELLO 2Competenze trasversali
Medio
Impatto sullo stipendio
2 mesi
Tempo di apprendimento
Medio
Difficoltà
12
Carriere
In sintesi

Opportunity Solution Trees (OST) is a framework developed by Melissa Perri for breaking down big opportunities into actionable problems and solutions. Outcome (customer goal) → Opportunities (ways to reach goal) → Solutions (how you build it). Learning curve: 2-3 weeks to understand, 4-6 weeks for mastery. Product teams using OST deliver 40% faster, waste 50% less effort on wrong features. Salary: product managers using OST earn 15-20% premium (get promoted faster, deliver better results).

Cos'è Opportunity Solution Trees

Opportunity Solution Trees (OST) is a strategic framework for breaking down big customer outcomes into prioritized opportunities and solutions. Developed by Melissa Perri, it prevents "building random features" and aligns product development with customer goals. Structure: Outcome (what customer wants) → Opportunities (different ways to achieve) → Solutions (features you could build). Tree prioritizes which opportunities to explore, preventing waste on low-impact features.

🔧 STRUMENTI ED ECOSISTEMA
OST frameworkOutcome mappingProblem prioritizationUser researchExperimentation trackingRoadmap planningOpportunity scoringSolution testing

📋 Prima di iniziare

Product Strategy

💰 Stipendio per regione

RegioneLivello baseMidLivello esperto
USA$70k$120k$180k
UK£44k£74k£112k
EU€47k€80k€125k
CANADAC$67kC$115kC$175k

❓ Domande frequenti

How is OST different from a traditional product roadmap?
Traditional roadmap = list of features (implement X by Y date). OST = outcome-driven. Start with customer outcome, explore multiple solutions, test ideas cheaply. OST = avoid building wrong features.
Can I use OST for an existing product?
Yes. OST helps prioritize what to build next. Map current features to outcomes. Identify outcomes with no solutions (gaps). Spot outcomes with multiple solutions (pick best).
How do I define a good outcome?
Outcomes are customer goals, not features. Good: 'Reduce onboarding time by 50%'. Bad: 'Build feature X'. Good outcome = measurable, customer-focused, outcome-oriented.
How many levels should OST have?
Typically 3: Outcome (root goal) → Opportunities (ways to reach outcome) → Solutions (how you build). Can be deeper (more levels) for complex problems, but gets unwieldy.
How do I prioritize which solutions to build?
Score by: impact (how much moves outcome needle?), effort (build time), confidence (how sure you are). High impact + low effort = priority.

Non sei sicuro che questa competenza faccia per te?

Fai il Career Match — ti suggeriremo i percorsi giusti.

Trova le competenze adatte a te →

Trova il tuo percorso di carriera ideale

Abbinamento basato sulle competenze per 2521 carriere. Gratis, ~3 minuti.

Fai il Career Match — gratis →