prioritization-frameworks

Compares and applies nine product prioritization frameworks including RICE, ICE, Kano, and Opportunity Score.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/stefanomartiradonna/claude-skills --skill prioritization-frameworks-stefanomartiradonna
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prioritization-frameworks
Source: https://github.com/stefanomartiradonna/claude-skills/tree/main/pm-execution-prioritization-frameworks
Command: npx skills add https://github.com/stefanomartiradonna/claude-skills --skill prioritization-frameworks-stefanomartiradonna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product managers often struggle to choose the right prioritization method or apply frameworks like RICE and ICE inconsistently, leading to feature-driven roadmaps instead of problem-driven ones. This reference guide provides formulas, when-to-use guidance, and templates for nine prioritization frameworks so teams prioritize customer problems rather than solutions. ## Core Features & Use Cases - Nine Frameworks Compared: Covers Opportunity Score, ICE, RICE, Kano, MoSCoW, Eisenhower Matrix, Impact vs Effort, Risk vs Reward, and Weighted Decision Matrix with best-fit scenarios for each. - Formulas and Scoring Guidance: Provides exact formulas such as Opportunity Score = Importance × (1 − Satisfaction) and RICE = (Reach × Impact × Confidence) / Effort, with normalization instructions. - Ready-to-Use Templates: Links to Google Sheets templates for ICE and RICE scoring and a Google Slides template for Importance vs Satisfaction surveys. - Use Case: A PM debating RICE vs ICE for a quarterly roadmap can consult the comparison table, learn that RICE adds Reach for larger teams needing granularity, and open the linked spreadsheet template to score initiatives immediately. ## Quick Start Ask which prioritization framework fits your situation, for example whether to use RICE or ICE for scoring a backlog of feature ideas.

Frequently Asked Questions about prioritization-frameworks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between RICE and ICE for prioritization?▼

RICE splits ICE's Impact into Reach and Impact, scoring (Reach × Impact × Confidence) / Effort, which suits larger teams needing more granularity. ICE uses Impact × Confidence × Ease and works better for quick prioritization of ideas and initiatives.

What is the Opportunity Score formula in product management?▼

Opportunity Score = Importance × (1 − Satisfaction), from Dan Olsen's The Lean Product Playbook. Survey customers on importance and satisfaction normalized to 0–1; high importance with low satisfaction marks the best opportunities.

When should I use the Kano model for prioritization?▼

Use Kano to understand customer expectations, not to prioritize. It classifies needs as Must-be, Performance, Attractive, Indifferent, or Reverse, helping you understand how features affect satisfaction before applying a scoring framework.

What are the limitations of the MoSCoW method?▼

MoSCoW sorts requirements into Must, Should, Could, and Won't categories but originates from project management rather than product discovery. It lacks quantitative scoring, so it works poorly for comparing customer value across many opportunities.

How do I prioritize customer problems instead of features?▼

Survey customers on the importance and satisfaction of each need, then compute Opportunity Score as Importance × (1 − Satisfaction). Plot results on an Importance vs Satisfaction chart; the upper-left quadrant contains the highest-value problems to solve.