Kith Spark
Sign in

Template

RICE Prioritization Template

A RICE scoring sheet adapted to weight reach by revenue, not just raw user counts.

In short

A RICE prioritization template for scoring product initiatives by reach, impact, confidence, and effort. This version adds a revenue weighting step so reach reflects account value, not just headcount, which helps teams justify why a request from a few large accounts can outrank a louder request from many small ones.

RICE scores an initiative as reach times impact times confidence, divided by effort. It is a useful tie-breaker because it forces every factor into the open instead of letting the loudest voice win.

Plain RICE treats every user as equal, which hides revenue concentration. This template adds a deal-weighting step so a request backed by a few high-value accounts can be compared fairly against a request backed by many small ones.

Template

RICE PRIORITIZATION

Initiative: ____
Linked requests: ____

REACH
How many users or accounts are affected per quarter? ____
Revenue weighting: total deal value or ARR behind the request: ____
Weighted reach (people x value factor, or use the calculator): ____

IMPACT (per affected user)
3 = massive, 2 = high, 1 = medium, 0.5 = low, 0.25 = minimal
Impact: ____    Why: ____

CONFIDENCE
100% = strong evidence, 80% = some, 50% = a guess
Confidence: ____%    Evidence: ____

EFFORT
Person-months across product, design, and engineering: ____

SCORE
(Reach x Impact x Confidence) / Effort = ____

NOTES
Anything the number does not capture (strategic bet, dependency): ____

How to use it

  1. 1Score a set of competing initiatives in one sitting so the numbers stay comparable.
  2. 2Fill the revenue weighting line from linked deal value rather than estimating from memory.
  3. 3Be honest about confidence. A low score here flags where you need more evidence, not less ambition.
  4. 4Use the score to rank, then read the Notes line before committing. The number is an input, not a verdict.
  5. 5Re-score when new feedback or deal data arrives so the ranking reflects current demand.

Frequently asked questions

Why weight reach by revenue?

Raw upvotes overrepresent large, vocal segments and underrepresent small accounts that pay a lot. Weighting reach by deal value lets you compare a high-revenue request against a high-volume one on the same scale and defend the call.

Is a higher RICE score always the thing to build?

No. RICE ranks comparable, well-understood work. Strategic bets, compliance requirements, and platform investments often justify overriding the score. Use the Notes line to record when and why you override it.

Related

Run this live in Kithspark

Templates get you started. Kithspark runs the whole loop, from the first request to the shipped release, with every contributor kept in the loop.

Sign in