Use RICE when several initiatives compete for the same team and you can estimate their reach on the same time horizon. Calculate (Reach x Impact x Confidence) / Effort, rank the results, then review strategic constraints before committing.
- Use one reach unit and one time period for every item.
- Treat confidence as an explicit discount for weak evidence.
- Use the ranking to expose assumptions, not to override strategy or obligations.
The RICE formula
Reach estimates how many people or accounts will encounter the change in a fixed period. Impact estimates how much the change will move the chosen outcome for each person reached. Confidence discounts the estimate when evidence is weak. Effort is the total work across product, design, engineering, research, and launch support.
A common impact scale is 3 for massive, 2 for high, 1 for medium, 0.5 for low, and 0.25 for minimal. Confidence is usually written as a percentage. Effort must use the same unit for every item, such as person-months.
| Initiative | Reach | Impact | Confidence | Effort | Score |
|---|---|---|---|---|---|
| Onboarding checklist | 1,200 users | 2 | 80% | 3 person-months | 640 |
| CSV export | 800 users | 1 | 90% | 2 person-months | 360 |
| Enterprise SSO | 250 users | 3 | 80% | 4 person-months | 150 |
Worked example: Relay
Relay is a fictional collaboration product. Its team wants to improve activation this quarter while responding to enterprise requests. The onboarding checklist scores 1,200 x 2 x 0.8 / 3 = 640. CSV export scores 800 x 1 x 0.9 / 2 = 360. Enterprise SSO scores 250 x 3 x 0.8 / 4 = 150.
RICE puts the onboarding checklist first. That is a useful result because the team named activation as its current outcome. It does not prove SSO is unimportant. If SSO is required to renew a major contract, that obligation belongs in a separate gate before the optional initiatives are ranked.
When RICE works well
RICE is strongest for a portfolio of similarly sized product initiatives with measurable exposure. It is weaker for foundational work, risk reduction, compliance, or a mix of tiny experiments and multi-year bets. Those items often need explicit constraints or separate comparison groups.
- Good fit: quarterly roadmap candidates tied to one outcome.
- Poor fit: mandatory security, legal, or contractual work.
- Poor fit: items whose reach uses incompatible units, such as users for one item and revenue accounts for another.
Common mistakes
- Changing the reach period from one item to another.
- Using confidence as a political adjustment after seeing the ranking.
- Counting engineering time but omitting design, research, migration, and launch effort.
- Treating a high score as approval rather than an input to a decision.
Check your understanding
Two initiatives use identical inputs except confidence: A is 80% and B is 40%. How do their RICE scores compare?
A scores exactly twice as high as B. Confidence scales the numerator directly.
Sources
- Intercom: RICE prioritizationOriginal practical description of the RICE method and its four factors.