prioritization-frameworks

Use it when:: You're choosing how to prioritize, comparing RICE and ICE, or learning how a framework works.
Core rule:: Prioritize customer problems, not features, and never let customers design the solution.
Recommends:: Opportunity Score, importance × (1 − satisfaction), for customer problems, and ICE for quick prioritization of ideas.
You get:: Formulas for Opportunity Score, ICE and RICE, a table of all nine frameworks with what each suits, and links to templates.
Runs:: As a reference only: no steps and no file.

TL;DR

A reference card from the PM Skills marketplace's pm-execution plugin. It starts from one principle: rank problems (opportunities), not features. Opportunity Score, from Dan Olsen's The Lean Product Playbook, surveys customers on how important each need is and how satisfied they are, normalized to 0–1; importance × (1 − satisfaction) finds the biggest gaps, plotted on an importance versus satisfaction chart. ICE multiplies impact (Opportunity Score × customers affected) by confidence and ease, scored 1–10. RICE splits reach out of impact, takes confidence as a percentage and divides by effort in person-months, for larger teams. A table places all nine: the Eisenhower Matrix for personal tasks, Impact vs Effort for quick triage, Risk vs Reward when uncertainty matters, Opportunity Score for customer problems, Kano for understanding expectations rather than ranking, the Weighted Decision Matrix for stakeholder buy-in, ICE, RICE, and MoSCoW for requirements, with a caution about its project-management origin. It links Google Sheets and Slides templates for Opportunity Score, ICE and RICE.

Summarizes the skill at 2a12295. Its SKILL.md has changed by 33 words since.

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

skills.sh page Source on GitHub All skills from phuryn/pm-skills

Total Downloads: 10,100 on skills.sh, Nov 9, 2026
Repo stars: 27,784 phuryn/pm-skills
First seen: Mar 4, 2026 on skills.sh

Weekly Downloads

-16% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	107
Sep 28	93
Oct 5	84
Oct 12	81
Oct 19	78
Oct 26	130
Nov 2	104
Nov 9	90

Category	category:planning category:software-engineering Make the agent question you and write the plan down before it writes code. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type	type:guidelines Knowledge and rules the agent applies while it works: best practices, design principles, API references.
Effect	effect:none Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs	needs:none Instructions only. Works in any agent that supports skills.
Publisher	by:community Everyone else. Unverified vendor claims default to community.
Topics	planning

SKILL.md

From phuryn/pm-skills at 9af7bfd. Checked daily, last changed Nov 9, 2026.

Frontmatter

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.

When a group scores or ranks items together, collect the votes independently before the discussion, so the most senior opinion doesn't anchor everyone else (the live-polls skill covers dot voting and confidence votes).

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.