RICE Scoring
RICE scoring is a prioritization method that ranks product ideas using four factors: Reach, Impact, Confidence and Effort. The score is (Reach × Impact × Confidence) ÷ Effort, an estimate of the total impact delivered per unit of team time. Sean McBride introduced RICE at Intercom to make comparisons between very different ideas more consistent and less dependent on gut feel.
How RICE Scoring Works
Each idea is estimated on four factors, using the scales Intercom described:
- Reach: how many people or events the idea will affect in a set period, for example "customers per quarter" or "sign-ups per month." It uses real numbers, not a rating.
- Impact: how much the idea will affect each person reached. Intercom uses a fixed scale: 3 for massive, 2 for high, 1 for medium, 0.5 for low and 0.25 for minimal.
- Confidence: how much the team trusts its own estimates, as a percentage: 100% for high, 80% for medium and 50% for low. Anything lower is effectively a guess.
- Effort: the total time required from everyone involved, in person-months, using whole numbers (or 0.5 for very small work).
The three benefit factors are multiplied together and divided by effort. Because Reach and Effort use real units, a RICE score reads as "impact per person-month," which makes very different ideas comparable on one scale.
Why RICE Scoring Matters
RICE forces a team to make its assumptions explicit. Instead of arguing about whether an idea is "big," people have to state how many users it reaches, how strongly it affects them and how sure they are. Disagreements then become specific and testable.
The Confidence factor is especially useful. It discounts exciting ideas that rest on thin evidence, which protects the roadmap from pet projects. Separating Reach from Impact also stops a feature that helps a handful of users enormously from being confused with one that helps many users a little.
McBride was clear that RICE should not be applied as a hard rule. Dependencies, strategic bets and commitments can justify working out of score order, and the score makes those exceptions visible rather than hiding them. RICE is most reliable when paired with a second method that catches its blind spots, such as urgency, which RICE does not measure. Making scores consistent across large backlogs and many contributors is a challenge of its own, covered in RICE prioritization at scale.
RICE Scoring Example
A product team compares three ideas for the next quarter:
| Idea | Reach (users/quarter) | Impact | Confidence | Effort (person-months) | RICE score |
|---|---|---|---|---|---|
| Bulk edit for records | 2,000 | 1 | 80% | 2 | 800 |
| Guided setup for new admins | 500 | 3 | 50% | 1 | 750 |
| Faster search | 6,000 | 0.5 | 100% | 4 | 750 |
Bulk edit leads narrowly. The near-tie with the other two tells the team its estimates matter more than the ranking, so it runs a short test to raise confidence in the guided setup before committing.
RICE vs. Other Scoring Methods
ICE scoring is a faster cousin that drops Reach and rates everything on a relative 1 to 10 scale. Weighted scoring lets a team choose its own criteria and weights instead of using a fixed formula. Both belong to the broader set of prioritization frameworks.