prioritization-frameworks
このスキルは、RICE、ICE、Kanoなど9つの製品優先順位付けフレームワークに関する包括的なガイドを提供し、公式、使用シナリオ、テンプレートを含みます。これにより、プロダクトマネージャーは最適な優先順位付け方法を選択し、製品機能やプロジェクトを効果的に評価およびランク付けできます。結果として、リソース配分が最適化され、チームが最も価値のある作業に集中できるようになります。
npx skills add https://github.com/phuryn/pm-skills --skill prioritization-frameworksBefore / After 効果比較
1 组このスキルがない場合、ユーザーは製品開発において、優先順位が混乱し、意思決定に時間がかかり、主観的になるという問題に直面することがよくありました。チームメンバーはどの機能が最も重要であるかについて合意がなく、リソースが分散され、多くの価値の低い機能が開発され、価値の高いプロジェクトのリリースが遅れていました。
この Skill は、構造化された優先順位付けフレームワークを提供し、ユーザーが製品機能を体系的に評価し、ランク付けするのに役立ちます。これにより、意思決定プロセスがより客観的かつ効率的になり、チームは迅速に合意に達し、最も影響力のあるプロジェクトに集中できるようになり、製品の成功率とリソース利用効率が大幅に向上します。
Prioritization Frameworks Reference
A reference guide to help you select and apply the right prioritization framework for your context.
Core Principle
Never allow customers to design solutions. Prioritize problems (opportunities), not features.
Opportunity Score (Dan Olsen, The Lean Product Playbook)
The recommended framework for prioritizing customer problems.
Survey customers on Importance and Satisfaction for each need (normalize to 0–1 scale).
Three related formulas:
- Current value = Importance × Satisfaction
- Opportunity Score = Importance × (1 − Satisfaction)
- Customer value created = Importance × (S2 − S1), where S1 = satisfaction before, S2 = satisfaction after
High Importance + low Satisfaction = highest Opportunity Score = best opportunities. Plot on an Importance vs Satisfaction chart — upper-left quadrant is the sweet spot. Prioritizes customer problems, not solutions.
ICE Framework
Useful for prioritizing initiatives and ideas. Considers not only value but also risk and economic factors.
- I (Impact) = Opportunity Score × Number of Customers affected
- C (Confidence) = How confident are we? (1-10). Accounts for risk.
- E (Ease) = How easy is it to implement? (1-10). Accounts for economic factors.
Score = I × C × E. Higher = prioritize first.
RICE Framework
Splits ICE's Impact into two separate factors. Useful for larger teams that need more granularity.
- R (Reach) = Number of customers affected
- I (Impact) = Opportunity Score (value per customer)
- C (Confidence) = How confident are we? (0-100%)
- E (Effort) = How much effort to implement? (person-months)
Score = (R × I × C) / E
9 Frameworks Overview
| Framework | Best For | Key Insight |
|---|---|---|
| Eisenhower Matrix | Personal tasks | Urgent vs Important — for individual PM task management |
| Impact vs Effort | Tasks/initiatives | Simple 2×2 — quick triage, not rigorous for strategic decisions |
| Risk vs Reward | Initiatives | Like Impact vs Effort but accounts for uncertainty |
| Opportunity Score | Customer problems | Recommended. Importance × (1 − Satisfaction). Normalize to 0–1. |
| Kano Model | Understanding expectations | Must-be, Performance, Attractive, Indifferent, Reverse. For understanding, not prioritizing. |
| Weighted Decision Matrix | Multi-factor decisions | Assign weights to criteria, score each option. Useful for stakeholder buy-in. |
| ICE | Ideas/initiatives | Impact × Confidence × Ease. Recommended for quick prioritization. |
| RICE | Ideas at scale | (Reach × Impact × Confidence) / Effort. Adds Reach to ICE. |
| MoSCoW | Requirements | Must/Should/Could/Won't. Caution: project management origin. |
Templates
- Opportunity Score intro (PDF)
- Importance vs Satisfaction Template — Dan Olsen (Google Slides)
- ICE Template (Google Sheets)
- RICE Template (Google Sheets)
Further Reading
ユーザーレビュー (0)
レビューを書く
レビューなし
統計データ
ユーザー評価
この Skill を評価