It’s easy to get caught in endless debates about what should go into the backlog. Everyone has opinions, but opinions don’t always help you choose between two equally valid ideas.
That’s where the RICE framework comes in. Created by Intercom, it gives you a structured, data-driven way to compare backlog items based on four factors: Reach, Impact, Confidence, and Effort.
What RICE Stands For
- Reach → How many people will this affect in a given time? (e.g. 500 users per month)
- Impact → How much difference will it make for each person? (scored as 3 = massive, 2 = high, 1 = medium, 0.5 = low, 0.25 = minimal)
- Confidence → How sure are we about our reach and impact estimates? (percentage: 100% = high, 80% = medium, 50% = low)
- Effort → How much time/resources will it take? Measured in “person-months” (or weeks/days in smaller teams).
The formula is simple:
RICE score = (Reach × Impact × Confidence) ÷ Effort
How to Apply RICE
1. Define the time frame.
Decide whether you’re thinking in terms of weeks, months, or quarters.
2. Estimate each factor.
- Reach → number of users or transactions affected.
- Impact → choose from the standard scale (3, 2, 1, 0.5, 0.25).
- Confidence → your certainty in those estimates.
- Effort → how long it will take the team.
3. Calculate the score.
Use the formula to compare items. The higher the score, the higher the priority.
4. Sort your backlog.
Rank items by score, then review with stakeholders.
Example: Voucher Feature vs Dark Mode
- Voucher Feature
- Reach = 200 stakeholders per year
- Impact = 2 (high)
- Confidence = 80%
- Effort = 2 weeks
- RICE score = (200 × 2 × 0.8) ÷ 2 = 160
- Dark Mode
- Reach = 10,000 users per year
- Impact = 0.5 (low)
- Confidence = 70%
- Effort = 6 weeks
- RICE score = (10,000 × 0.5 × 0.7) ÷ 6 ≈ 583
| Feature | Reach | Impact | Confidence | Effort | RICE Score |
|---|---|---|---|---|---|
| Voucher Feature | 200 | 2 | 80% | 2 | 160 |
| Dark Mode | 10,000 | 0.5 | 70% | 6 | 583 |
👉 Even though the voucher feature feels urgent internally, the numbers show dark mode might have a bigger user-facing impact. That’s the power of RICE: it challenges assumptions with numbers.
Pros and Cons
✅ Pros
- Quantitative — reduces arguments based on opinion.
- Confidence factor keeps estimates grounded.
- Works well for larger backlogs with many competing requests.
⚠️ Cons
- Still relies on subjective estimates.
- Can feel too heavy for small teams or simple projects.
- Easy to get lost in the math instead of the conversation.
When to Use RICE
RICE is especially useful when:
- You have lots of competing ideas and need a systematic way to compare them.
- Your stakeholders demand data-driven prioritisation.
- You want to highlight trade-offs between quick wins vs big-impact bets.
It’s less useful if your backlog is small, or if you don’t have enough data to make reasonable estimates.
RICE isn’t perfect, but it’s a strong framework for bringing structure to backlog debates. It forces you to think in terms of reach, impact, confidence, and effort — and the conversation you have while scoring is often as valuable as the score itself.
👉 Reflection: Try applying RICE to your top 5 backlog items. Does the ranking surprise you, or confirm what you already knew?
