RICE Prioritization Framework

A quantitative approach to feature prioritization used by leading product teams worldwide

Reach × Impact × Confidence ÷ Effort | Popularized by Intercom

What is RICE?

RICE is a prioritization framework designed to help product teams make objective, data-driven decisions about which features and projects to work on. Developed and popularized by Intercom, it provides a systematic way to evaluate opportunities by scoring them across four key factors: Reach, Impact, Confidence, and Effort.

Unlike subjective prioritization methods that rely on gut feeling or opinion, RICE introduces quantifiable metrics that force teams to think critically about each dimension of a potential project. The result is a numerical score that allows for direct comparison between wildly different initiatives.

The RICE Formula

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

Higher scores indicate higher priority projects

Why RICE Works

RICE forces teams to explicitly consider both the upside (Reach × Impact × Confidence) and the cost (Effort) of every initiative. This balanced approach prevents teams from cherry-picking easy but low-impact work or pursuing high-impact projects that consume disproportionate resources.

The Four Components of RICE

Numerator Component

Reach

Definition: How many people will this impact within a given time period?

Measurement: Number of users/customers per quarter (or month)

Example: "This feature will reach 5,000 customers per quarter" = Reach score of 5,000

Common metrics: Transactions per quarter, users who see the feature, support tickets per month

Numerator Component

Impact

Definition: How much will this impact each person?

Measurement: Scored on a scale

  • 3 = Massive impact
  • 2 = High impact
  • 1 = Medium impact
  • 0.5 = Low impact
  • 0.25 = Minimal impact

Example: A critical bug fix might be 3.0; a minor UI improvement might be 0.5

Numerator Component

Confidence

Definition: How confident are you in your Reach and Impact estimates?

Measurement: Percentage

  • 100% = High confidence (strong data)
  • 80% = Medium confidence (some data)
  • 50% = Low confidence (hypothesis)

Purpose: Prevents "moonshot" projects with uncertain outcomes from dominating your roadmap. Use this to de-prioritize ideas that sound good but lack evidence.

Denominator Component

Effort

Definition: How much total work will this require from the entire team?

Measurement: Person-months (total time across all team members)

Example: If 2 engineers work for 3 weeks and 1 designer works for 2 weeks, that's approximately 2.5 person-months

Includes: Design, engineering, testing, project management, and any other team time required

Tip: Use minimum viable scope. Effort for the smallest useful version, not the dream version.

Worked Example: Prioritizing Features

Let's compare five different feature ideas for a SaaS product to see how RICE scoring works in practice:

Feature Reach
(users/qtr)		 Impact
(0.25-3)		 Confidence
(%)		 Effort
(person-mo)		 RICE Score Priority
Mobile app redesign 8,000 2.0 80% 6 2,133 3rd
Single sign-on (SSO) 3,500 3.0 100% 4 2,625 2nd
Onboarding tutorial 12,000 2.0 80% 3 6,400 1st
Advanced analytics dashboard 1,200 1.0 50% 5 120 5th
Bulk export feature 4,000 1.0 100% 2 2,000 4th

Analysis of Results

Winner: Onboarding tutorial (6,400) - Despite not having the highest individual scores, it combines high reach with solid impact and reasonable effort, making it the clear priority.

Runner-up: SSO (2,625) - Massive impact (3.0) and high confidence overcome the moderate reach. Critical for enterprise customers.

Deprioritized: Advanced analytics (120) - Low confidence and limited reach result in a poor score despite moderate effort. This might be worth revisiting once you have better data.

Interactive RICE Calculator

Calculate Your RICE Score

Enter your estimates for each component to see the calculated RICE score

How many users will this affect per quarter?
Minimal (0.25), Low (0.5), Medium (1), High (2), Massive (3)
How confident are you in your estimates? (0-100%)
Total team effort required in person-months

Your RICE Score:

—

Step-by-Step Implementation Process

1. List All Ideas Collect features, bugs, projects to evaluate 2. Estimate Reach Use analytics, user data, or informed estimates 3. Score Impact Use the 0.25-3 scale based on goals 4. Set Confidence Reflect uncertainty in Reach & Impact 5. Calculate Effort Sum person-months for entire team 6. Compute Scores (R × I × C) / E for each initiative 7. Rank & Prioritize Sort by score, build roadmap from top down 8. Review Regularly Update scores as new data emerges

Best Practices for Using RICE

  • Be consistent with time periods - Always use the same time frame for Reach (typically per quarter). Don't mix monthly and quarterly estimates.
  • Anchor Impact scores with examples - Create a reference guide with examples of 0.25, 0.5, 1, 2, and 3 impact scores specific to your product goals. This ensures everyone scores consistently.
  • Use Confidence to reflect uncertainty - If you're guessing at Reach or Impact, use 50% confidence. This naturally de-prioritizes risky bets without eliminating them.
  • Include all team effort - Don't just count engineering time. Include design, QA, product management, marketing, and any other resources the project requires.
  • Score as a team - Collaborative scoring sessions reduce individual bias and incorporate diverse perspectives. Aim for consensus, not perfection.
  • Start with minimum viable scope - Estimate Effort for the leanest version that delivers value. You can always expand later.
  • Don't over-optimize the formula - RICE provides directional guidance, not absolute truth. Scores within 20-30% of each other are effectively tied.
  • Re-score quarterly - As you ship features and gather data, your Confidence should increase and estimates should improve. Update scores regularly.
  • Consider strategic factors separately - RICE doesn't capture everything. Use it alongside strategic considerations like competitive positioning, technical debt, or contractual obligations.
  • Document your assumptions - Write down how you calculated Reach and why you chose specific Impact/Confidence scores. This creates accountability and learning opportunities.

Common Pitfalls to Avoid

Gaming the system: Teams sometimes inflate Reach or Impact to prioritize pet projects. Combat this with transparent scoring sessions and documented assumptions.

Paralysis by analysis: Don't spend hours debating whether Impact is 1.75 or 2.0. Make your best estimate and move on.

Ignoring qualitative factors: RICE is a tool, not a replacement for judgment. Strategic initiatives, compliance requirements, or technical debt may trump scores.

Advanced Considerations

When RICE Works Best

RICE is particularly effective for:

Adapting RICE for Different Contexts

B2B SaaS

Reach: Accounts affected, not individual users

Impact: Consider revenue impact, not just user value

Note: Weight enterprise customer requests by ARR

Consumer Apps

Reach: DAU/MAU affected

Impact: Tie to engagement, retention, or monetization metrics

Note: Consider viral/network effects in Impact scoring

Internal Tools

Reach: Team members or workflows affected

Impact: Time saved or efficiency gained

Note: Calculate ROI by comparing effort to time saved

Complementary Frameworks

RICE works well alongside other prioritization methods:

Use ICE (Impact, Confidence, Ease) for rapid hypothesis prioritization in growth experiments - it's simpler and faster for high-volume testing.

Use Kano Model to categorize features by user satisfaction impact before applying RICE - helps set appropriate Impact scores.

Use Value vs. Effort matrices for executive presentations - stakeholders understand 2x2 matrices more intuitively than RICE scores.

Measuring Success

Track these metrics to evaluate whether RICE is improving your prioritization:

Key Takeaways

RICE transforms subjective prioritization into an objective, repeatable process. By systematically evaluating Reach, Impact, Confidence, and Effort, product teams can make better decisions, align stakeholders, and focus resources on work that matters most.

Remember: RICE is a tool, not a dictator

Use it to inform decisions, spark productive conversations, and build consensus—but always leave room for strategic judgment and qualitative factors that numbers can't capture.