JobCannon
ټول مهارتونه

Opportunity Solution Trees

⬢ درجه 2نرم مهارتونه
منځنی
د معاش اغېز
2 میاشتې
د زده کړې وخت
منځنی
سختوالی
12
مسلکونه
په یوه نظر

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

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.

🔧 وسیلې او ایکوسیستم
OST frameworkOutcome mappingProblem prioritizationUser researchExperimentation trackingRoadmap planningOpportunity scoringSolution testing

📋 مخکې له دې چې تاسو پیل کړئ

Product Strategy

💰 د سیمې له مخې معاش

سیمهجونیرمنځنیسېنیر
USA$70k$120k$180k
UK£44k£74k£112k
EU€47k€80k€125k
CANADAC$67kC$115kC$175k

❓ ډېرې پوښتل شوې پوښتنې

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.

ډاډه نه یاست چې دا مهارت ستاسو لپاره دی؟

د کاري مسلک سمون ازموینه واخلئ — موږ به تاسو ته سمې لارې وړاندیز کړو.

زما لپاره غوره مهارتونه ومومئ →

خپل غوره مسلکي لاره ومومئ

د ۲٬۵۲۱ مسلکونو په اوږدو کې د مهارت پر بنسټ سمون. وړیا.

د کاري مسلک سمون ازموینه واخلئ — وړیا →