RICE Prioritization
We needed a way to compare very different types of projects and make our best case for why they deserved to be prioritized — a consistent, shared language for decisions.
RICE is a quantitative prioritization framework that assigns a numerical score to each product initiative using the formula: (Reach × Impact × Confidence) ÷ Effort. Developed by Sean McBride at Intercom, it replaces gut feel and political influence with structured, repeatable estimation. It's built for product managers and teams who need a defensible way to rank their backlog without defaulting to whoever argues loudest.
“I have about 8 features we're debating for next quarter. We keep going in circles and everyone has a different favorite.”
Score every idea by reach, impact, confidence, and effort — then let the math decide
RICE uses a single formula to score any product initiative: (Reach × Impact × Confidence) ÷ Effort. Reach is the number of users or events affected per time period, measured in real units (e.g., customers per quarter). Impact uses McBride's fixed 5-point multiplier scale — 3 for massive, 2 for high, 1 for medium, 0.5 for low, 0.25 for minimal — to capture per-person value rather than total volume. Confidence is expressed as a percentage (100%, 80%, or 50%) that functions as an uncertainty penalty, directly discounting scores when estimates lack supporting data. Effort is total person-months required across all contributors. The output is a ranked table where every initiative has a comparable, defensible score — exposing counter-intuitive rankings that gut feel and the HiPPO effect (Highest Paid Person's Opinion) would have buried.
Product backlogs fill with ideas that feel equally urgent, and prioritization defaults to whoever argues loudest or holds the most seniority — the HiPPO (Highest Paid Person's Opinion) problem. Most teams either skip scoring entirely or use vague 1-5 ratings that mean different things to different people in different meetings. RICE was designed specifically to remove these distortions by encoding reach, depth of impact, and honest uncertainty into a single comparable number that any team member can inspect and challenge.
Score your entire backlog in under an hour and walk into your next planning meeting with a ranked list backed by explicit, auditable math — not gut feel or organizational gravity.
- A list of features, projects, or initiatives you want to prioritize
- Rough estimates of user reach and team effort for each item
- Any signals about potential impact — user research, support tickets, analytics, stakeholder input
- A time horizon for Reach estimates (e.g., per quarter or per month)
- A RICE score for each initiative using the exact (Reach × Impact × Confidence) ÷ Effort formula with McBride's fixed scales
- A ranked priority table with all four component scores visible side-by-side for every item
- Flagged confidence assumptions — places where estimates are speculative and should be downgraded before presenting to stakeholders
- Interpretive notes on surprising inversions: items that felt like obvious priorities but rank low due to high effort or honest confidence levels
Watch the methodology work.
Three specimens from a single real session: the same situation, unaided and calibrated, the full transcript, and the skill answering live in the channel where the work happens.
“You have 8 features on the Q3 roadmap debate list. Three engineers insist the API redesign is critical infrastructure. Your VP wants Salesforce integration because an enterprise prospect mentioned it twice. Two PMs are split between a performance overhaul and a redesigned onboarding flow. Every planning meeting ends with a list of 'high priority' items that hasn't changed in three weeks. The feature that wins is the one whose champion showed up most prepared to argue.”
“Every feature has a RICE score: accounts per quarter, McBride's fixed impact multiplier, an honest confidence percentage that reflects actual evidence, and real effort estimates from the team. Salesforce integration scores 75 — not 150 — once the sales team's speculative confidence is corrected from 100% to 50%. CSV export scores 80 and claims the #1 slot. Your VP sees the math, understands exactly which assumption drove the ranking, and the conversation shifts to 'what would it take to get higher confidence on Salesforce' rather than 'why isn't Salesforce first.' The planning meeting takes 45 minutes.”
The same skill, where the work happens.
No new app to learn. The methodology runs over the WhatsApp Business API, so the answer lands as a reply in the thread you’re already in — same rigour, zero context-switch.
What it does, specifically.
Each capability is a distinct move drawn straight from the source methodology — not a generic assistant guessing.
RICE Score Calculator
Guides you through estimating each of the four RICE components for a single initiative, applying McBride's fixed scales and returning the calculated score. Prompts you with concrete examples when estimates feel uncertain and catches the most common errors — especially forgetting to time-bound Reach and defaulting to 100% Confidence without supporting data.
Backlog Scoring Session
Takes a full list of initiatives and systematically scores each one using RICE, maintaining definitional consistency across the entire set. Prevents the calibration drift that happens when the same word means something different by item 10 vs. item 1, and flags whenever an estimate seems inconsistent with how you scored a comparable item.
Confidence Calibration Check
Identifies when a Confidence estimate is inflated relative to the available evidence. Asks what data, user research, or precedent supports the estimate and suggests downgrading to 80% or 50% when estimates rest on assumption rather than evidence — preventing overconfidence from distorting the final ranking.
Reach Time-Bounding Coach
Helps you define and consistently apply a Reach time period and unit of measurement across all items in your backlog. Distinguishes between B2C contexts (users per quarter), B2B contexts (accounts per quarter), and event-based products (sessions per month), preventing the most common RICE calibration error: using different time windows or mixed units across items.
Ranked Priority Table Generator
Outputs a formatted table of all scored initiatives sorted by RICE score, with every component value visible in separate columns. Surfaces inversion cases — items that felt like obvious top priorities but rank low due to high effort or honest confidence levels — and explains what's driving the counter-intuitive ranking in plain language.
Graded before it shipped.
Every skill is scored against independent scenarios for methodology fidelity before it goes live — not vibes, a rubric.
RICE Scored Backlog Table
A formatted table with columns for initiative name, Reach, Impact multiplier, Confidence percentage, Effort (person-months), calculated RICE score, and rank. Each row shows the full score breakdown so any team member can inspect exactly what's driving priority — and challenge individual estimates rather than the overall conclusion.
Confidence Audit Report
A flagged list of items where Confidence estimates were downgraded during scoring, showing the original estimate, the revised estimate, and the evidence gap that triggered the change. Designed to share with stakeholders who ask why certain seemingly-important items were de-prioritized.
Reach Calibration Baseline
A one-page specification of your Reach parameters: the time period, the unit of measurement (users, accounts, events), and how to count users across different product surfaces — so every future scoring session uses the same calibration and scores remain comparable quarter over quarter.
Grounded in the original work.
Every answer traces back to a real source and the practitioner who wrote it — not a secondhand summary. Here is the source of record.
Sean McBride
Sean McBride created the RICE framework while working as a product manager at Intercom, publishing the methodology in a 2016 blog post that became one of the most widely cited prioritization references in product management. The framework has since been incorporated into PM bootcamps, training programs, and curricula worldwide, and is referenced in hundreds of product management courses and books.
RICE: Simple Prioritization for Product Managers (Intercom Blog, 2016)
Product manager at Intercom; creator of the RICE scoring framework, widely cited in PM literature and training programs globally.
Be first to run it.
RICE Prioritization is being built right now. Leave your email and we’ll tell you the moment it goes live.