RICE Prioritisation Matrix
When you juggle ten or so projects in parallel every day, the question "what is the actual priority?" comes up constantly. The RICE method answers it with clear logic: Reach, Impact, Confidence, Effort. This tool calculates the score and ranks your backlog automatically.
📊
RICE Score = (Reach × Impact × Confidence%) / Effort. Features are automatically sorted by descending score. No data is stored.
How to use this tool
- 1Add your features or user stories
- 2Rate each item on the 4 RICE dimensions
- 3The score is calculated automatically
- 4Sort your backlog by score, highest first
Why it matters
The RICE method moves teams away from gut-feel prioritisation by imposing a shared reasoning structure. Each dimension has a specific role: Reach quantifies people affected, Impact measures expected effect, Confidence caps optimism bias, Effort brings in real cost. The final score divides weighted impact by effort, which mechanically favours small, high-leverage actions.
Frequently asked questions
How does RICE prioritisation work?
RICE score = (Reach x Impact x Confidence) / Effort. Reach: number of users affected per period. Impact: score from 0.25 to 3 based on effect on the goal. Confidence: percentage certainty in your estimates. Effort: number of person-weeks required.
What is the difference between RICE and ICE scoring?
ICE (Impact, Confidence, Ease) is simpler but less precise: it does not account for the number of users affected. RICE is preferable when features target segments of very different sizes.
Is RICE suitable for all types of backlog?
RICE works well for product backlogs and growth projects. It is less appropriate for critical bugs (which have absolute priority) or regulatory requirements that must be addressed regardless of score.