prioritization-frameworks

Product Prioritization Framework Reference Guide

Overview

A comprehensive reference guide to product prioritization frameworks, covering nine prioritization methods—including RICE, ICE, and Opportunity Score—with detailed formula explanations, comparisons of use cases, and practical templates to help product managers quickly select the right decision-making framework.

Applicable Scenarios

1. Choosing a Product Prioritization Method

When you are facing multiple product requests, features, or improvement opportunities and need to systematically determine their priority, this guide helps you understand the appropriate use cases for different frameworks. It is recommended to use Opportunity Score first to evaluate customer problems, and ICE or RICE to rank specific solutions, avoiding wasted resources on low-value features.

2. Comparing Framework Differences

When team members disagree about which prioritization method to use, this guide enables quick comparisons between common options such as RICE vs. ICE and Opportunity Score vs. the Kano Model. Each framework clearly identifies “what it is best suited for” and its “key insights,” helping you make a choice based on team size, decision complexity, and risk tolerance.

3. Learning the Principles of Prioritization

For product managers who want to develop a deeper understanding of product prioritization logic, this guide provides detailed explanations of core formulas—such as Opportunity Score = Importance × (1 − Satisfaction)—the design principles behind each framework, and ways to collect data through customer research. The accompanying Google Sheets and Slides templates can be applied directly to real-world work.

Core Features

1. Opportunity Score for Prioritizing Customer Problems

This is the core method for product prioritization: collect each customer need’s “importance” and “current satisfaction” through customer research, normalize both values to a 0–1 scale, and calculate the opportunity score as:

Opportunity Score = Importance × (1 − Satisfaction)

High importance combined with low satisfaction produces a high opportunity score, representing an unmet customer pain point. This method forces you to prioritize solving problems rather than starting with predetermined solutions, and serves as the foundation for all other frameworks, including ICE and RICE.

2. ICE and RICE Decision Scoring

ICE (Impact × Confidence × Ease) is suitable for quickly evaluating ideas and solutions by considering their potential impact, the team’s confidence, and implementation difficulty. RICE builds on this by breaking Impact into Reach—the number of users affected—and Impact—the value per user. Its formula is:

(Reach × Impact × Confidence) / Effort

RICE is suitable for larger teams that need more granular prioritization. Both methods are based on Opportunity Score data.

3. Comparison and Templates for Nine Frameworks

The guide provides a complete framework comparison table covering the Eisenhower Matrix for personal tasks, Impact vs. Effort for quick screening, Risk vs. Reward for uncertain scenarios, the Kano Model for understanding levels of customer needs, the Weighted Decision Matrix for multi-factor decisions, and MoSCoW for requirement categorization, among others. Each framework is labeled with “what it is best suited for” and its “key insights,” along with ready-to-use Google Sheets and Slides templates.

Frequently Asked Questions

Why Is Opportunity Score Recommended Over Other Frameworks?

Opportunity Score directly quantifies how well customer needs are being met. By combining “importance” and “satisfaction,” it helps identify unmet pain points. Its key advantage is that it forces you to understand the problem before designing a solution, helping you avoid the feature factory trap. Other frameworks, such as ICE and RICE, further consider factors like the number of users affected and implementation cost, but they are all built on Opportunity Score data.

Should I Choose RICE or ICE?

For small teams or situations requiring quick decisions, ICE (Impact × Confidence × Ease) is recommended. Its formula is simple and well suited to everyday prioritization. For larger teams or resource-constrained situations, RICE ((Reach × Impact × Confidence) / Effort) is recommended. It clearly distinguishes between the number of users affected and the value per user, while measuring investment in person-months, making it more suitable for cross-functional collaboration and resource planning. The two methods share the same fundamental logic, with RICE serving as a more granular version of ICE.

Is the MoSCoW Method Suitable for Prioritizing Product Features?

MoSCoW (Must/Should/Could/Won’t) originated in project management. It is suitable for categorizing requirements but not for ranking them. It is highly subjective, and different team members may have completely different definitions of what “must be done” and what “should be done.” If you need data-driven prioritization, the combination of Opportunity Score + ICE/RICE is recommended. If you simply need to categorize and communicate quickly, MoSCoW can serve as a supporting tool.

Which Prioritization Framework Should Large Teams Choose?

Large teams typically need to consider user scale, cross-functional collaboration, and transparency in resource allocation. Therefore, the RICE framework is recommended. Its formula—(Reach × Impact × Confidence) / Effort—clearly quantifies the number of users affected, value per user, team confidence, and required investment, making it easier for different stakeholders to reach consensus. Combined with customer research data from Opportunity Score, it can establish a consistent standard for product prioritization decisions.

How Do I Start Applying These Prioritization Frameworks?

It is recommended to start with Opportunity Score: collect data on the importance and satisfaction of customer needs through customer research, plot an importance–satisfaction quadrant chart, and identify the high-opportunity area in the upper-left quadrant. Then use ICE or RICE to score potential solutions and prioritize projects with the highest scores. This guide provides ready-made Google Sheets and Slides templates that can be used directly for data collection and team communication.

Is the Kano Model Used for Ranking or for Understanding Customer Needs?

The Kano Model is primarily used to understand customer expectations and levels of need rather than to rank items directly. It categorizes needs into five types—Must-be, Performance, Attractive, Indifferent, and Reverse—helping you identify which are essential baseline features and which are “delighter” features. When conducting Opportunity Score research, you can combine it with the Kano Model to deepen your understanding of customer needs, but final prioritization should still use a scoring framework such as ICE or RICE.