RICE vs WSJF: Which Prioritization Framework to Use

What this episode covers

RICE vs WSJF: Which Prioritization Framework to UseBoth RICE and WSJF reduce a backlog to a single number, and both divide value by a size term so small bets float up. The difference is what sits in the numerator. RICE multiplies Reach times Impact times Confidence. WSJF uses Cost of Delay. RICE asks how much total user value does this create. WSJF asks how much value do we lose by shipping it late. That is the entire comparison, and it decides which framework fits your team.The RICE formula is Reach times Impact times Confidence, divided by Effort. It optimizes for total user impact per unit of effort. It has no time-criticality term. It comes from product management, originally published at Intercom in 2016.The WSJF formula is Cost of Delay divided by Job Size. It optimizes for economic throughput when delay is costly. Time criticality is built in, because it is part of Cost of Delay. WSJF is native to the Scaled Agile Framework, or SAFe. Cost of Delay is a composite of three relative scores: User-Business Value, Time Criticality, and Risk Reduction or Opportunity Enablement. Inputs are typically scored on a relative Fibonacci scale of 1, 2, 3, 5, 8, 13.What RICE is best for. You have an established product with real usage data, so Reach by feature, by segment, by geography is knowable rather than a guess. You are ranking an open backlog where the dominant question is which of these creates the most user value for the work involved, and few items have hard deadlines. You need a defensible quarterly prioritization to show stakeholders, and the Effort denominator forces honest cost accounting. RICE's strength is converting a political this-feels-important conversation into comparable numbers. Its blind spot is timing. RICE has no clean way to say this is worth half as much if we ship it in the third quarter instead of the first.What WSJF is best for. Delay erodes the value of the work, such as regulatory deadlines, competitive responses, seasonal launches, or contractual dates. You are running a multi-team program, the SAFe context WSJF was built for, and need a shared throughput-maximizing sequence across dependencies. The backlog is full of items where finishing small things quickly frees capacity for the bigger bets. WSJF's killer feature is making time-criticality explicit. Its blind spot is the reliability of estimates. Relative scoring across many teams drifts, and Job Size guesses are weakest at the start of complex work.The Cost-of-Delay Test. The cleanest way to choose between RICE and WSJF is not to compare their formulas. It is to ask one question about your backlog, not your process. Does the value of a typical item decay with time?Run each candidate item through three yes-or-no checks. First, deadline pressure. Is there a hard external date, such as a regulation, contract, market window, or season, after which this is worth materially less? Second, competitive decay. Does a rival shipping first erode what this is worth to us? Third, compounding loss. Does every week of delay actively cost us, through churn, lost revenue, or accruing risk, not just postpone a gain?If the answers across your backlog are mostly no to all three, use RICE. Value is time-invariant, and impact-per-effort is the right optimization. If they are mostly yes to one or more, use WSJF, because Cost of Delay is real and RICE cannot see it. If the backlog is split, with some items decaying but most not, use RICE backlog-wide and apply WSJF only to the decaying subset. Don't distort the whole ranking for a few time-bombs.

PodParley-generated summary based on available episode metadata and transcript content.