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$70,000$120,000$180,000
UK£44,000£74,000£112,000
EU€47,000€80,000€125,000
CANADACA$67,000CA$115,000CA$175,000

❓ 常見問題

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.

不確定這項技能適不適合你？

做一下職業匹配，我們會推薦合適的方向。

找到最適合我的技能 →

找到理想的職業方向

在 2,521 個職業中進行技能匹配。免費。

免費做職業匹配 →