What is the RICE scoring model

RICE stands for:

• Reach (R): The number of people impacted by the project or feature over a specific time period.
• Impact (I): The expected magnitude of change or benefit the project will bring, often measured in metrics like increased revenue, engagement, or customer satisfaction.
• Confidence (C): The level of certainty in your estimates for reach and impact, typically expressed as a percentage (0-100%).
• Effort (E): The amount of time and resources required to implement the project or feature, often measured in person/months or weeks.

Think of it like this:

Reach: How many people will use this new feature?
Impact: How much will it improve things (e.g., more sales,  loyal users)?
Confidence: How sure are you that your idea will work?
Effort: How much time and money will it take to build?

What are the benefits of the RICE method?

Copy link

It provides undeniable benefits:

• RICE makes prioritization more objective and transparent, reducing guesswork.
• It provides better team alignment. Everyone speaks the same language when discussing priorities.
• RICE focuses on big wins, since it pushes to work on projects/features with the widest reach and impact.
• Learning from results. The framework will track progress and see if your initial estimates were accurate.

How to use the RICE framework?

Copy link

Let’s start with the RICE score formula:

RICE Score = (Reach × Impact × Confidence) ÷ Effort

Each variable has a specific unit and a common scale. Applying them consistently across projects is what makes RICE scores comparable.

Reach. The number of people affected by the feature or project within a defined time window, usually one quarter. Use a raw count rather than a scale. If a feature reaches an estimated 3,000 users per quarter, Reach is 3,000. Reach should reflect real users touched, not total user base.

Impact. The expected magnitude of change per user reached. Intercom, which introduced RICE, uses a specific scale: 3 for massive impact, 2 for high, 1 for medium, 0.5 for low, and 0.25 for minimal. This non-linear scale reflects the reality that massive-impact projects genuinely deliver several times the value of low-impact ones. Impact is qualitative and subjective; the scale keeps it consistent across projects.

Confidence. How certain the team is about the Reach and Impact estimates, expressed as a percentage between 0 and 100. Common anchors: 100% for well-supported by data, 80% for strong evidence, 50% for informed guess, 20% or lower for pure hunch. Confidence penalizes optimistic estimates without strong evidence.

Effort. The total person-months required to complete the project, including engineering, design, QA, and product management. Use a consistent unit across all projects being scored, so effort estimates are comparable.

How to read the result. RICE scores are useful comparatively, not in absolute terms. A score of 40 is neither good nor bad on its own; it is meaningful only relative to other projects being scored in the same session. Rank the projects from highest to lowest and use the ordering as an input to the prioritization decision, not the decision itself.

Common mistakes.

• Using a linear 1-5 scale for Impact loses the non-linear signal that separates massive from medium projects
• Estimating Reach as a scale (1-5) rather than a raw count makes the multiplication meaningless
• Setting Confidence higher than the evidence supports, which inflates scores of ambitious projects that have not been validated
• Mixing effort units (weeks for some projects, months for others) so scores are not comparable
• Treating the score as the final answer, rather than an input to a broader prioritization conversation

RICE prioritization example

Copy link

Consider a product team choosing among four features for the next quarter. The team scores each feature on the four RICE variables and calculates a score.

Calculations use the formula RICE = (R × I × C) ÷ E, with Confidence as a decimal (0.8, 0.5, 1.0, 0.8).

What the ranking says. The onboarding flow redesign ranks first: it reaches many users, delivers high impact per user, has strong evidence behind the estimates, and takes moderate effort. The AI-powered smart search would deliver the largest raw impact (12,000 users × massive impact) but the low confidence (50% — the team is guessing whether users will adopt it) and higher effort push it down. The Slack integration ranks third despite its small reach because it is a cheap, high-confidence win. The analytics dashboard ranks last: modest reach, medium impact, and higher effort than the alternatives.

What the ranking does not say. The RICE ranking assumes each feature is independent. If the AI-powered search would be a strategic differentiator that changes the product's positioning, or if the onboarding redesign is a prerequisite for a marketing campaign already planned, those factors sit outside the RICE model. The team should read the ranking as one input among several, alongside strategic alignment, dependencies, and team morale factors that RICE cannot capture.

A common pattern in RICE outputs. High-confidence, low-effort projects tend to score well, which biases prioritization toward quick wins. This is often the right call, but occasionally a lower-scoring, higher-risk project is worth doing because it opens up options the safer projects cannot. RICE surfaces the trade-off; the team makes the call.

RICE vs MoSCoW and Kano

Copy link

RICE isn't the only chef in town; there are several popular alternatives. Each answers a different question, and mature product teams often combine two or three to get a complete picture.

MoSCoW method. Classifies features into four categories: must-have, should-have, could-have, and won't-have (this time). MoSCoW answers "what do we absolutely need to ship?" rather than "what delivers the most value?" It is fast, easy to communicate, and works well for release planning and scope negotiations. It does not distinguish between two must-haves of very different value, or between two should-haves of very different cost. Best used when the question is scope, not ranking.

Kano model. Categorizes features by how users perceive them: basic (expected, invisible when present, painful when absent), performance (linear satisfaction with more of it), excitement (delight users when present, do not disappoint when absent), and indifferent. Kano answers "which features will actually move customer satisfaction?" It is powerful for surfacing invisible basics and identifying delighters, but it requires customer research (usually a Kano survey) to run properly. Best used at the discovery stage, before scoring efforts start.

Value/Effort matrix. Plots features on a two-axis grid (value vs effort) and identifies quick wins (high value, low effort), major projects (high value, high effort), fill-ins (low value, low effort), and time sinks (low value, high effort). Answers "which projects give the best return per unit of effort?" It is fast, visual, and easy to run in a meeting. It compresses value into a single dimension, which loses the Reach × Impact × Confidence breakdown that RICE captures.

How they compare:

Using them together. A common pattern is to start with Kano during discovery to understand what users care about, use RICE to score and rank candidate features, and use MoSCoW at release-planning time to decide which of the top RICE-ranked features must ship in the next release versus the one after. The Value/Effort matrix works well as a quick visual complement to RICE when the team wants to see quick wins at a glance.

When RICE is not the right tool. Very early-stage products where user reach cannot be estimated, exploratory research projects where impact is unknown by design, or decisions where strategic alignment overrides ROI. In those cases, other frameworks (or simple stakeholder judgment) work better than forcing artificial RICE numbers.