RICE Framework for Solution Prioritization in Shorter Loop

How to Score and Prioritize Solutions in Shorter Loop

When your strategy map is filled with solutions addressing different opportunities, the hardest question becomes: which solution should we build first? Shorter Loop uses the RICE framework to bring objectivity to this decision, replacing gut-feel prioritization with a repeatable, data-informed scoring system.

RICE scores appear on solution cards in the Strategy Map and Strategy Board, giving your team an at-a-glance comparison of every solution's expected return relative to its cost.

Why RICE Works

"The best product teams don't just pick the loudest idea in the room — they pick the one with the highest leverage."

Traditional prioritization often falls victim to recency bias, authority bias, or the loudest-voice-wins dynamic. RICE counters this by forcing teams to evaluate every solution across four consistent dimensions, producing a single comparable score.

The Formula

RICE Score = (Reach × Impact × Confidence) / Effort

Each component captures a different facet of the investment decision:

The Four Components

Step 1: Estimate Reach

Reach measures how many people or accounts this solution will affect within a defined time period (typically one quarter).

Use real data wherever possible — analytics, user counts, segment sizes

Be specific: "5,000 monthly active users on the dashboard" is better than "a lot of users"

Example	Reach Value
Internal admin tool used by 15 people	15
Feature affecting all free-tier users	50,000
Onboarding flow every new signup goes through	3,000/quarter

Step 2: Assess Impact

Impact estimates how much this solution will move the needle for each person it reaches. Shorter Loop uses a standardized scale:

Score	Meaning	Example
3	Massive impact	Eliminates a critical workflow blocker
2	High impact	Significantly improves a daily task
1	Medium impact	Noticeable improvement to experience
0.5	Low impact	Minor convenience improvement
0.25	Minimal impact	Barely perceptible change

When in doubt, be conservative. Most features land at 1 (medium) — reserve 2 and 3 for genuinely transformative changes.

Step 3: Set Confidence

Confidence reflects how much evidence backs your Reach and Impact estimates. Express it as a percentage:

Score	Meaning	When to use
100%	High confidence	Backed by data, user research, or past experiments
80%	Medium confidence	Some supporting data, reasonable assumptions
50%	Low confidence	Gut feel, limited data, new territory

Confidence acts as a built-in penalty for uncertainty. A high-impact idea with only 50% confidence scores half as much as one backed by real data — encouraging teams to validate before committing.

Step 4: Estimate Effort

Effort represents the total investment required, measured in person-months (one person working full-time for one month = 1).

Include design, engineering, QA, and any other functions involved

Round up to account for unknowns

A two-week project for one engineer = 0.5 person-months

A three-month project for a team of 4 = 12 person-months

Worked Examples

Example A: One-Click Export Feature

Component	Value	Reasoning
Reach	2,000	Monthly active users who view reports
Impact	1	Medium — saves time but not a blocker
Confidence	80%	Based on support tickets requesting this
Effort	1	One engineer, ~4 weeks

RICE Score = (2,000 × 1 × 0.8) / 1 = 1,600

Example B: AI-Powered Search Redesign

Component	Value	Reasoning
Reach	10,000	All users who use search weekly
Impact	2	High — current search is a top complaint
Confidence	50%	No prototype tested yet
Effort	6	2 engineers + 1 designer for 2 months

RICE Score = (10,000 × 2 × 0.5) / 6 = 1,667

Example C: Admin Audit Log

Component	Value	Reasoning
Reach	50	Only enterprise admins
Impact	2	High — compliance requirement
Confidence	100%	Contractual obligation from 3 accounts
Effort	2	One engineer, ~8 weeks

RICE Score = (50 × 2 × 1.0) / 2 = 50

Comparing the Results

Solution	RICE Score	Verdict
One-Click Export	1,600	High leverage — do this soon
AI Search Redesign	1,667	Highest score but low confidence — validate first
Admin Audit Log	50	Low score but may be required for compliance

RICE scores inform the conversation — they don't end it. A score of 50 doesn't mean "don't build it," it means the team should discuss whether business constraints (like compliance) override the score.

Using RICE Scores in Shorter Loop

Open a solution from the Strategy Board or Strategy Map

Fill in Reach, Impact, Confidence, and Effort in the solution detail view

The RICE Score is calculated automatically and displayed on the solution card

Use the Strategy Map to visually compare scores across solutions — higher scores surface to the top

Key Takeaway

RICE scoring doesn't promise perfect decisions — it promises consistent, comparable, and defensible ones. When every solution is evaluated on the same four dimensions, your team spends less time debating preferences and more time shipping the work that matters most.

RICE Framework for Solution Prioritization in Shorter Loop

How to Score and Prioritize Solutions in Shorter Loop#

Why RICE Works#

The Formula#

The Four Components#

Step 1: Estimate Reach#

Step 2: Assess Impact#

Step 3: Set Confidence#

Step 4: Estimate Effort#

Worked Examples#

Example A: One-Click Export Feature#

Example B: AI-Powered Search Redesign#

Example C: Admin Audit Log#

Comparing the Results#

Using RICE Scores in Shorter Loop#

Key Takeaway#