What does RICE stand for in product roadmapping?

RICE stands for Reach, Impact, Confidence, and Effort. Developed by the team at Intercom, it is a mathematical framework used to objectively prioritize feature ideas on a product roadmap.

Why does RICE use 'Reach' instead of just Impact?

Reach forces product managers to acknowledge how many actual users will interact with a feature. A feature with massive impact for only 10 users shouldn't necessarily override a feature with medium impact that touches 10,000 users. Reach ensures you optimize for the broader user base.

How do you calculate the Effort score in RICE?

Effort is calculated in 'person-months' (the work one team member can do in a month). If a feature takes 2 developers and 1 designer a full month to build, the Effort score is 3. The minimum effort score you can assign is 0.5.

Framework

RICE Scoring Framework: The Complete Prioritisation Guide

TL;DR: RICE (Reach × Impact × Confidence ÷ Effort) is a strict, mathematical scoring system developed by Intercom to objectively prioritize product features. By adding "Reach" to the prioritization equation, it prevents niche power-user requests from overshadowing high-visibility, base-level UX improvements.

Key Implementation Stats

Prioritizes base-level UX over niche features, ensuring roadmap alignment with the majority user base.
Confidence scores should be mercilessly strict: 100% (proven by data), 80% (strong hypothesis), 50% (gut feeling). Anything below 50% is a "moonshot".
Reduces roadmapping debates by >50% in cross-functional teams by moving arguments from "opinions" to "variables".

The RICE Methodology Explained

Unlike abstract scoring models that rely on gut feelings, RICE demands quantifiable inputs wherever possible. It requires Product Managers to pull actual data from their analytics tools (like Mixpanel or Amplitude) to justify their roadmap positioning.

The formula is: (Reach × Impact × Confidence) ÷ Effort = RICE Score

1. Reach

How many users will experience this feature in a given time period? Do not guess this number; pull it from your analytics. For an Indian EdTech platform, if you are building a new "Download PDF" button on the course page, and that page receives 50,000 views per month, your Reach is 50,000. It grounds the feature in reality.

2. Impact

If a user interacts with the feature, how much will it move your primary goal (e.g., conversion, retention)? Intercom standardizes this scale to prevent score inflation:

3: Massive impact
2: High impact
1: Medium impact
0.5: Low impact
0.25: Minimal impact

3. Confidence

If you have high Reach and high Impact, but zero evidence to back it up, your Confidence score acts as a necessary penalty. Be brutal with this grading:

100%: High confidence (Backed by a successful A/B test or massive survey data).
80%: Medium confidence (Backed by qualitative user interviews and strong hypotheses).
50%: Low confidence (An educated guess or an executive's pet project).

4. Effort

Effort is the denominator. How many "person-months" will this take to build? A person-month is the amount of work one team member can do in a month. If a feature takes two backend engineers and one UI designer 2 weeks (half a month) to build, the Effort is 1.5. Always estimate Effort in whole numbers, with a minimum floor of 0.5 (to prevent dividing by zero and artificially inflating scores).

When RICE Beats ICE (Indian SaaS Context)

For a scaling B2B SaaS startup in India (like a Freshworks, Chargebee, or Zoho ecosystem app), RICE is essential over simpler models like ICE. Why? Because Enterprise clients often shout the loudest.

Imagine a scenario where an Enterprise client paying ₹5 Lakhs/month demands a highly custom reporting feature. It will take 2 months to build (Effort: 2). The impact for them is massive (Impact: 3). You are 100% confident they want it.

Without RICE, this feature looks great. But with RICE, the Reach exposes the flaw: it only affects 10 enterprise users. Compare this to a 1-month feature (Effort: 1) that improves the self-serve onboarding flow for 10,000 SMB users (Reach: 10,000). RICE mathematically proves that the onboarding feature provides vastly more utility to the business as a whole, giving the PM the data they need to politely push back on the Enterprise sales team.

Spreadsheet Setup & Best Practices

You don't need expensive roadmapping software to start. Set up a Google Sheet with columns for Feature Name, Goal, Reach, Impact, Confidence, Effort, and Final Score. Create a macro to auto-calculate the final column.

Crucial Rule: Require links! If a PM inputs a 100% Confidence score, they must hyperlink the cell to the actual Amplitude chart or Maze user testing report that proves the assertion. If there is no link, the confidence score drops to 50% automatically.

Want to Apply RICE to Your Roadmap?

Let our advisory team audit your current feature backlog and re-score it using strict RICE principles. Stop building on gut instinct.

Hire us →