prioritization-frameworks
此技能提供9种产品优先级框架的参考指南，包括RICE、ICE、Kano等，附带公式、使用指导和模板。它能帮助产品经理选择最适合的优先级方法，有效评估和排序产品功能或项目，从而优化资源分配，确保团队聚焦于最有价值的工作。
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 评分