Every product team has more ideas than capacity. Without a shared way to compare them, prioritisation defaults to whoever argues loudest or whichever stakeholder is most senior. RICE - Reach, Impact, Confidence, Effort - is one of the simplest ways to bring structure to that conversation.
The four ingredients
- Reach: how many users will this affect in a given period? Use real numbers where you can - 'about 1,200 users hit this screen each month' - not gut feel.
- Impact: how much will it move the needle for each user? A simple scale works: 3 for massive, 2 for high, 1 for medium, 0.5 for low, 0.25 for minimal.
- Confidence: how sure are you about your reach and impact estimates? 100% for strong data, 80% for some evidence, 50% for informed guesswork. Below 50%, you need discovery, not scoring.
- Effort: how much team time will it take, in person-months? Include design and testing, not just engineering.
The score is (Reach × Impact × Confidence) ÷ Effort. A feature reaching 1,200 users with high impact (2), 80% confidence, and one person-month of effort scores 1,920. A flashy idea reaching 200 users with medium impact, 50% confidence, and three months of effort scores 17. The comparison does the arguing for you.
Where RICE earns its keep
The real value of RICE is not the number - it is what producing the number forces you to do. You cannot score reach without looking at analytics. You cannot score confidence without being honest about how much evidence you have. And when a stakeholder pushes their pet feature, 'let's score it together' converts a political conversation into an evidence conversation.
Where it misleads
- False precision. A RICE score of 1,920 versus 1,850 means nothing - the inputs are estimates. Use scores to sort ideas into rough tiers, not to split hairs.
- Strategy blindness. RICE optimises for measurable near-term value. Foundational work - platform investment, technical debt, a strategic bet on a new market - will often score badly and still be the right call. Score within a strategy, not instead of one.
- Garbage in, garbage out. If every idea gets 'high impact, 100% confidence', the exercise is theatre. Calibrate as a team and challenge each other's inputs.
- Effort optimism. Teams routinely halve real effort. Involve the engineers who will build it before you trust the denominator.
Making it work in practice
Run RICE as a team exercise, not a PM spreadsheet produced in isolation - the debate over each input is where the alignment happens. Rescore quarterly, because reach and confidence change as you learn. And keep a 'we chose not to score this' lane for strategic work, so the framework serves your judgement rather than replacing it.
Used this way, RICE will not make decisions for you. It will do something more useful: make your reasoning visible, comparable, and challengeable - which is exactly what good prioritisation looks like.