Generated banner for Prioritization Frameworks
Generated logo for Prioritization Frameworks

Prioritization Frameworks

Pawel HurynCommunityCreated by Pawel Huryn

  • Skill
  • Guidelines
  • Business and productivity
  • MIT
  • No issues found

From the author

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.
— the description by Pawel Huryn

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured reference for product managers and teams to evaluate and prioritize initiatives, customer problems, and tasks. It covers nine distinct frameworks, including RICE, ICE, Kano, and the Opportunity Score, offering formulas, strategic context, and guidance on when to apply each method. By focusing on the distinction between prioritizing problems versus solutions, it helps teams move away from feature-factory mentalities toward data-informed decision-making.

What it does

  • Explains the core formulas for RICE, ICE, and Opportunity Score frameworks.
  • Provides a comparative overview of nine common prioritization models.
  • Offers guidance on selecting the right framework based on team size and project needs.
  • Distinguishes between prioritizing customer problems and prioritizing feature solutions.
  • Includes links to external templates for immediate application in spreadsheets and slides.

When to use it

  • When you need to decide which product initiatives to tackle next.
  • When comparing the utility of different frameworks like RICE versus ICE.
  • When you need to justify prioritization decisions to stakeholders.
  • When you are looking for a structured way to measure customer needs versus satisfaction.

Advantages

  • Centralizes multiple industry-standard frameworks in one reference guide.
  • Provides clear, actionable formulas for quantitative prioritization.
  • Helps teams avoid common pitfalls by emphasizing problem-based prioritization.
  • Includes ready-to-use templates for quick implementation.

Usage examples

“Which prioritization framework should I use for a large team managing many features?”
The skill suggests the RICE framework, noting that it is specifically useful for larger teams that require more granularity by incorporating Reach and Effort.
“How do I calculate the Opportunity Score for a customer problem?”
The skill provides the formula: Opportunity Score = Importance * (1 - Satisfaction), where both variables are normalized to a 0-1 scale.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/phuryn/prioritization-frameworks/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip prioritization-frameworks.zip -d .agents/skills

Documentation by Pawel Huryn

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

Files

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Pawel Huryn
Publisher
Pawel Huryn (Community)
Source
phuryn/pm-skills · pm-execution/skills/prioritization-frameworks · commit 2a12295
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Pawel Huryn or Pawel Huryn.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download prioritization-frameworks.zip