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.

25 September 20104 min read

Quick take

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

Related Services

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.

Before you start, be clear on candidate , how each RICE variable will be estimated, and what scoring scales you will use.

Ensure participants understand the criteria.

Run the method.

RICE scoring is systematic and collaborative.

Assign values for Reach, Impact, , and Effort. Calculate each score using: (Reach × Impact × Confidence) ÷ Effort. Rank by score and review results with the team.

Focus on making informed, comparable decisions.

Capture and make sense of it.

The value comes from transparency and .

After scoring: document rationale, share results with , use rankings to inform choices, and revisit scores as new appears.

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
Effort
Resources, time, and complexity required
Overall RICE score
Guides prioritisation objectively

Where it goes wrong

Most issues come from:

If scoring is arbitrary, will be flawed.

poor or biased estimates
inconsistent scoring across features
ignoring qualitative factors not captured in RICE
over-reliance on the formula without discussion
failing to update scores as data changes

What you get from it

Done properly, this method gives you:

objective, comparable prioritisation of features
evidence-based roadmap decisions
clear justification for choices
balanced allocation of effort versus value

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 effectively and guide decisions that maximise user and business value.

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

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 based on Reach, Impact, , and Effort.

When should you use RICE scoring?

When planning , , or resource allocation.

What can you score?

, improvements, or initiatives.

Why is it important?

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

Does RICE scoring improve UX?

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

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services. The work usually starts where things have become harder than they need to be: unclear journeys, inconsistent products, competing priorities, or teams trying to move forward without a clear direction. I help simplify the problem, shape the right next step, and turn complexity into something people can actually use.

Previous feedback

Will Parkhouse

Senior Content Designer

01/20