prioritization-frameworks

Name: prioritization-frameworks
Availability: InStock
Author: ankaboot

Compares nine product prioritization frameworks with formulas, selection guidance, and templates.

2|Updated Jul 25, 2026

Search Tags:#product management #roadmap #prioritization #rice #ice #kano #opportunity score

Ready to run

npx skills add https://github.com/ankaboot-source/boucle --skill prioritization-frameworks-ankaboot-source

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prioritization-frameworks
Source: https://github.com/ankaboot-source/boucle/tree/main/.jcode/skills/prioritization-frameworks
Command: npx skills add https://github.com/ankaboot-source/boucle --skill prioritization-frameworks-ankaboot-source

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams struggle to choose and correctly apply the right prioritization method, often defaulting to gut feel or feature requests instead of structured scoring of customer problems and initiatives. ## 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 when-to-use guidance. - Formulas Included: Provides exact scoring formulas such as Opportunity Score = Importance × (1 − Satisfaction) and RICE = (Reach × Impact × Confidence) / Effort. - Templates and References: Links to Google Sheets and Slides templates for Opportunity Score, ICE, and RICE, plus further reading on product discovery. - Use Case: When deciding between two roadmap initiatives, apply ICE scoring (Impact × Confidence × Ease) to rank them, or survey customers on importance and satisfaction to compute Opportunity Scores. ## Quick Start Ask which prioritization framework fits your situation and how to score your backlog items with it.

Frequently Asked Questions about prioritization-frameworks

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

FAQPage Schema

How do I prioritize product features with RICE or ICE?▼

ICE scores initiatives as Impact × Confidence × Ease, while RICE uses (Reach × Impact × Confidence) / Effort for more granularity. Higher scores indicate items to prioritize first, with RICE better suited to larger teams needing reach data.

What is the Opportunity Score formula in product management?▼

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

RICE vs ICE: which prioritization framework should I use?▼

Use ICE for quick prioritization of ideas and initiatives with three simple factors. Choose RICE when you need to separate Reach from Impact and account for effort in person-months, typically for larger teams.

When should I use the Kano model for prioritization?▼

The Kano model is for understanding customer expectations, not prioritizing. It classifies needs as Must-be, Performance, Attractive, Indifferent, or Reverse, helping you interpret 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 better for scope agreement than rigorous prioritization.