Menu

Strategy

RICE Scoring

A practical product prioritisation method for comparing initiatives with a consistent, transparent scoring model.

How to apply RICE scoring to evaluate initiatives and prioritise roadmap items based on expected value relative to effort.

4 min read

What it is

RICE scoring is a UX and product method used to evaluate and rank or initiatives based on four criteria: Reach, Impact, , and Effort.

Each criterion is scored, and a formula calculates a total RICE score that guides .

The focus is on combining quantitative and qualitative factors to make objective decisions.

Key takeaway

The goal is to rank features based on value delivered versus effort required.

When to use it

Use this method when you need a transparent and -driven way to prioritise.

It is most useful when:

deciding between multiple competing features
creating a product roadmap
allocating limited development resources
balancing user value against effort and risk
needing to justify prioritisation to stakeholders

It is less useful when:

features are not comparable
estimates for reach, impact, or effort are unreliable
RICE scoring is often used alongside JTBD, Kano analysis, and feature prioritisation workshops.

How to run it

Set up properly

Be clear on the candidates, how each variable will be estimated, and what scales you are using. RICE is only as good as the estimates, and the estimates are usually guesses with decimal places.

Agree the scales in advance (what impact of 3 means, what effort is measured in) or the scores are not comparable between people.

Run the method

RICE scores initiatives on Reach, Impact, and Effort. Its usefulness is that Confidence is explicit, which forces a team to admit how much of the score is invention.

  1. Estimate Reach as the number of people affected in a defined period, using real where it exists.
  2. Estimate Impact on a consistent scale, agreed and written down before scoring begins.
  3. Estimate as a percentage, and be honest. Confidence is the variable that stops a speculative idea outscoring a certain one.
  4. Estimate Effort in person-months or a comparable unit, from the people who would actually do the work.
  5. Calculate as Reach × Impact × ÷ Effort, then rank and review the result as a group.

Interrogate the ranking rather than accepting it. Where the score contradicts strong intuition, one of the two is wrong and finding out which is the point of the exercise.

Capture and make sense of it

The value comes from making estimates explicit. After scoring, document:

  • The scores with the estimate behind each variable
  • Items where was low, which are candidates for first
  • Where the ranking surprised the team, and why
  • Estimates that should be revisited once evidence exists

Use this to compare unlike things consistently. Its real contribution is exposing which items are held up by alone.

Key takeaway

Use this to allocate resources to features that deliver the most value efficiently.

What to look for

Focus on:

Reach: how many users benefit from the feature
Impact: potential improvement in UX or business outcomes
Confidence: how certain your estimates are
Confidence: how much of the score is estimate rather than evidence
Overall RICE score: guides prioritisation objectively

Where it goes wrong

Most issues come from:

If scoring is arbitrary, will be flawed.

Estimating reach from optimism rather than from data
Scoring impact on scales different people interpret differently
Setting confidence high because low confidence feels like weakness
Accepting the ranking when it contradicts strong intuition, without asking why
Never revisiting scores once evidence arrives

What you get from it

Done properly, this method gives you:

Unlike things compared on a consistent basis
Confidence made explicit, so speculation cannot outrank certainty
The items held up by optimism alone, which need research first
A ranking that survives being questioned

Key takeaway

It helps teams focus on what delivers the most impact for users and business.

Get in touch

If this sounds like something you need, we can help you apply RICE scoring to prioritise features effectively and guide decisions that maximise user and business value.

No guesswork. No assumptions. Just structured, evidence-based prioritisation.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is RICE scoring in UX?

It is a method for prioritising features based on Reach, Impact, Confidence, and Effort.

When should you use RICE scoring?

When planning roadmaps, feature prioritisation, or resource allocation.

What can you score?

Anything competing for the same roadmap capacity: features, improvements, technical work, research. It works best when items are roughly comparable in kind; scoring a bug fix against a platform migration produces a number without producing a decision.

What does RICE add to a prioritisation conversation?

It helps make transparent, evidence-based decisions about what to build first.

Does RICE scoring improve UX?

Indirectly. By prioritising high-value features, it ensures the most impactful improvements are delivered to users.

Quick take

If you need a structured way to prioritise features, RICE scoring helps you weigh Reach, Impact, Confidence, and Effort.

Related Services

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer