What it is
A prioritization formula that scores each item by Reach times Impact times Confidence, divided by Effort, producing a comparable number to rank a backlog.
When to use it
During Synthesize or Ideate, when you want a more structured, defensible ranking than a simple matrix.
Why (value)
Forces explicit estimates of each factor, including a confidence term that discounts guesses, making prioritization more transparent.
How to run it
- For each item, estimate reach, impact, and confidence.
- Estimate effort.
- Compute (Reach x Impact x Confidence) / Effort.
- Rank by score.
- Sanity-check the ranking against judgment.
Inputs and outputs
- Inputs: Candidate items and estimates for each factor.
- Outputs: A ranked, scored backlog.
Time and effort
Low. Mostly the estimation discussion.
Evidence and limitations
RICE scores are inference: precise-looking numbers built on rough estimates. The formula organizes judgment, it does not validate it; garbage in, garbage out. See Evidence and limitations.
Tips and pitfalls
- Use the confidence factor honestly.
- Do not confuse precision with accuracy.
- Keep estimation units consistent across items.
Variations
RICE, ICE (drops reach), and weighted-scoring variants.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Impact-effort prioritization — Plot options by impact and effort to spot the quick wins and avoid the money pits.
- MoSCoW prioritization — Sort requirements into Must, Should, Could, and Won't to agree on scope.
- UX metrics frameworks — Choose a coherent set of UX metrics tied to goals so you measure what actually matters.
