Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.
A reference guide to help you select and apply the right prioritization framework for your context.
Never allow customers to design solutions. Prioritize problems (opportunities), not features.
The recommended framework for prioritizing customer problems.
Survey customers on Importance and Satisfaction for each need (normalize to 0–1 scale).
Three related formulas:
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.
Useful for prioritizing initiatives and ideas. Considers not only value but also risk and economic factors.
Score = I × C × E. Higher = prioritize first.
Splits ICE's Impact into two separate factors. Useful for larger teams that need more granularity.
Score = (R × I × C) / E
| 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. |