Prioritization frameworks

Skill phuryn/pm-skills/pm-execution/skills/prioritization-frameworks

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.From its SKILL.md

Install

npx -y skills add phuryn/pm-skills --skill prioritization-frameworks

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

4.1 KB, ~1.0k tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most roadmap strategy skills give in ~1.0k tokens

Counted across 614 of the 719 authors here whose files we hold, read 2026-09-06

Check for product marketing context firstin 39 of 614, across 16 files
Use compact with a custom summaryin 32 of 614, across 16 files
Compact after planningin 30 of 614, across 16 files
Do not compact mid-implementationin 30 of 614, across 17 files
Structure launch marketing across three channel typesin 21 of 614, across 5 files
Read the compaction suggestionin 20 of 614, across 10 files
Write before compactingin 17 of 614, across 11 files
Write important context to files before compactingin 16 of 614, across 5 files
Recruit early users one-on-onein 16 of 614, across 3 files
Identify 3-5 core content pillarsin 15 of 614, across 9 files
Target a specific keyword or questionin 14 of 614, across 4 files
Stagger announcements to maintain momentumin 14 of 614, across 4 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.