prioritization-frameworks

phuryn/pm-skills

Reference guide to 9 prioritization frameworks—RICE, ICE, Opportunity Score, Kano, MoSCoW, and more—with formulas and templates.

Source View on skills.sh

What is prioritization-frameworks?

A structured reference for selecting and applying prioritization frameworks to customer problems and initiatives. Use this when deciding which framework fits your context, comparing approaches like RICE vs ICE, or learning how different methods work.

Compare 9 prioritization frameworks (Opportunity Score, ICE, RICE, Kano, MoSCoW, Eisenhower Matrix, Impact vs Effort, Risk vs Reward, Weighted Decision Matrix)
Apply Opportunity Score formula: Importance × (1 − Satisfaction) to identify high-value customer problems
Calculate ICE scores (Impact × Confidence × Ease) for quick idea prioritization
Calculate RICE scores ((Reach × Impact × Confidence) / Effort) for larger-scale initiatives
Access templates for Opportunity Score, ICE, and RICE in Google Sheets and Slides

How to install prioritization-frameworks

npx skills add https://github.com/phuryn/pm-skills --skill prioritization-frameworks

Claude Code

Cursor

Windsurf

Cline

How to use prioritization-frameworks

1.Identify your context: are you prioritizing customer problems, ideas, or large-scale initiatives?
2.Select the appropriate framework from the 9 options based on the guidance table
3.For Opportunity Score: survey customers on Importance and Satisfaction (0–1 scale), then calculate Importance × (1 − Satisfaction)
4.For ICE: score Impact, Confidence (1–10), and Ease (1–10), then multiply
5.For RICE: gather Reach, Impact, Confidence (0–100%), and Effort (person-months), then calculate (R × I × C) / E
6.Use the provided templates (Google Sheets/Slides) to structure your analysis and share results

Use cases

Good for

Deciding whether to use RICE or ICE for your team's prioritization process
Identifying the highest-opportunity customer problems using Importance vs Satisfaction surveys
Scoring and ranking a backlog of feature ideas using ICE or RICE
Understanding when to apply Kano Model vs Opportunity Score for different decision types
Building stakeholder alignment using Weighted Decision Matrix

Who it's for

Product managers selecting a prioritization method
Teams prioritizing features or initiatives at any scale
Product leaders comparing frameworks for organizational fit
Anyone learning how different prioritization approaches work

prioritization-frameworks FAQ

What's the difference between RICE and ICE?

ICE (Impact × Confidence × Ease) is simpler and faster for quick prioritization. RICE splits Impact into Reach (number of customers) and Impact (value per customer), making it more granular for larger teams. Use ICE for speed; use RICE when you need more precision.

Should I prioritize features or problems?

Prioritize problems (opportunities), not features. Use Opportunity Score (Importance × (1 − Satisfaction)) to identify which customer problems matter most. This prevents building solutions customers didn't ask for.

When should I use Kano Model?

Kano Model is for understanding customer expectations (must-be, performance, attractive), not for prioritization. Use it to categorize needs, then apply Opportunity Score or RICE to prioritize which ones to solve.

Can I use these frameworks for personal task management?

Yes, but Eisenhower Matrix (Urgent vs Important) is better suited for personal tasks. Use RICE, ICE, or Opportunity Score for product/initiative prioritization across teams.

How do I normalize Importance and Satisfaction for Opportunity Score?

Survey customers and ask them to rate each need on a 0–1 scale (or 0–10, then divide by 10). Plot results on an Importance vs Satisfaction chart; upper-left quadrant (high importance, low satisfaction) shows the best opportunities.

Full instructions (SKILL.md)

Source of truth, from phuryn/pm-skills.

name: prioritization-frameworks description: "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."

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.