Lewati ke konten utama
JobCannon
Semua keterampilan
⚡

Opportunity Solution Trees

⬢ TIER 2Soft skill
💰
Sedang
Dampak gaji
⏱
2 bulan
Waktu belajar
📊
Sedang
Tingkat kesulitan
👥
12
Karier
Sekilas

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).

Apa itu 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.

🔧 ALAT & EKOSISTEM
OST frameworkOutcome mappingProblem prioritizationUser researchExperimentation trackingRoadmap planningOpportunity scoringSolution testing

📋 Sebelum mulai

Product Strategy

💰 Gaji per wilayah

WilayahJuniorMenengahSenior
🇺🇸USA$70k$120k$180k
🇬🇧UK$44k$74k$112k
🇪🇺EU$47k$80k$125k
🇨🇦CANADA$67k$115k$175k

🎓 Sertifikasi

Melissa Perri OST Course→Product Strategy Fundamentals→

🎯 Karier yang memakai Opportunity Solution Trees

Ai Pm Consumer
Ai Product Manager
Business Analyst
Conversational Designer
Design Ops Manager
Embedded Systems Engineer
Industrial Designer
Intent Based Protocol Engineer
Market Researcher
Product Manager
Product Operations Manager
Service Designer

❓ FAQ

▶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.

🔗 Keterampilan terkait

Information Architecture IaMentoring Others GrowthMentoringStakeholder Management NavigationStakeholder ManagementVision Setting DirectionChange Management KotterChange ManagementStrategic ThinkingLearning AgilityLinkedin Ads B2bThought Leadership Platform
🎯

Belum yakin keterampilan ini cocok untukmu?

Ikuti Career Match — kami sarankan jalur yang tepat.

Temukan keterampilan terbaikku →

Temukan jalur karier idealmu

Pencocokan berbasis keterampilan di 2.536 karier. Gratis, ~2 menit.

Ikuti Career Match — gratis →
Jelajahi lagi:Semua keterampilanPustaka karierTes kepribadianMetodologi