mcpField
P
prioritization-frameworks

prioritization-frameworks

github.com/phurynProductivity27.5k10.0k installsUpdated 2w ago
Repository

About prioritization-frameworks

prioritization-frameworks is a reference for product teams choosing and applying prioritization methods. It covers approaches such as Opportunity Score, ICE, and RICE, and emphasizes prioritizing customer problems rather than feature solutions.

Key features

  1. 01Compares nine prioritization frameworks
  2. 02Explains the Opportunity Score formula
  3. 03Provides ICE and RICE scoring formulas
  4. 04Distinguishes problem and solution prioritization
  5. 05Describes suitable contexts for each method

Use cases

  1. 01Rank problems by customer importance and satisfaction
  2. 02Compare product ideas or initiatives
  3. 03Build scoring criteria for multi-factor decisions

Install

Copy the command and run it in a terminal.

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

After installing, type/prioritization-frameworksin Claude Code to confirm it loaded.

Details

From the project README

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
FrameworkBest ForKey Insight
Eisenhower MatrixPersonal tasksUrgent vs Important — for individual PM task management
Impact vs EffortTasks/initiativesSimple 2×2 — quick triage, not rigorous for strategic decisions
Risk vs RewardInitiativesLike Impact vs Effort but accounts for uncertainty
Opportunity ScoreCustomer problemsRecommended. Importance × (1 − Satisfaction). Normalize to 0–1.
Kano ModelUnderstanding expectationsMust-be, Performance, Attractive, Indifferent, Reverse. For understanding, not prioritizing.
Weighted Decision MatrixMulti-factor decisionsAssign weights to criteria, score each option. Useful for stakeholder buy-in.
ICEIdeas/initiativesImpact × Confidence × Ease. Recommended for quick prioritization.
RICEIdeas at scale(Reach × Impact × Confidence) / Effort. Adds Reach to ICE.
MoSCoWRequirementsMust/Should/Could/Won't. Caution: project management origin.
Templates

Further Reading

Comments

Markdown supported