RICE vs WSJF
Pick Your Score.
Two of the most-used PM scoring frameworks, compared. With formulas, worked examples, and when each one wins.
Quarter: ______
Date: ______
TL;DR
Use RICE when you’re comparing many heterogeneous bets across a B2B SaaS portfolio over a quarter or longer — it forces explicit confidence and reach assumptions, which is what cross-product prioritization needs. Use WSJF when you’re sequencing work inside a single product or sprint cadence and the cost of delay genuinely varies (regulatory deadlines, dependency chains, time-bound revenue). RICE answers “what should we work on this quarter?”; WSJF answers “in what order do we ship the work we’ve already committed to?”
RICE Explained
- Reach — users or events touched per quarter. Use real numbers (e.g. 4,200 monthly active users hitting the search box).
- Impact — per-user effect on the goal. Score 3 (massive), 2 (high), 1 (medium), 0.5 (low), 0.25 (minimal).
- Confidence — how much you trust the other three numbers. 100% (data-backed), 80% (good evidence), 50% (gut). Below 50% means do discovery first.
- Effort — person-months. Ranges OK (1, 2, 4, 8) — precision is fake.
Worked example — Search redesign: Reach = 4,200 users/mo. Impact = 2 (high; search-to-action drop is 60% of activation churn). Confidence = 80% (we have the funnel data, less certain on the lift). Effort = 3 person-months. RICE = (4,200 × 2 × 0.8) ÷ 3 = 2,240.
WSJF Explained
- User-Business Value — revenue, retention, NPS, strategic fit. Relative weight, not dollars.
- Time Criticality — does the value decay if we ship later? A regulatory deadline is 20. A nice-to-have is 1.
- Risk Reduction / Opportunity Enablement — does this de-risk the rest of the roadmap or unlock something downstream?
- Job Size — relative effort, not story points. Same Fibonacci scale.
Worked example — Search redesign: Value = 13 (activation lift). Time Criticality = 5 (churn is bleeding now but not catastrophic). Risk/Opportunity = 8 (de-risks Q3 onboarding revamp). Cost of Delay = 26. Job Size = 5. WSJF = 26 ÷ 5 = 5.2. Compare against every other backlog item on the same scale.
Side-by-Side Comparison
| RICE | WSJF | |
|---|---|---|
| Optimizes for | Total impact per unit effort | Sequencing under capacity |
| Time horizon | Quarter to year | Sprint to quarter |
| Granularity | Coarse (epics, themes) | Fine (stories, features) |
| Ease of estimation | Harder — needs real Reach data | Easier — relative Fibonacci |
| Calibration risk | Confidence inflation | Time-criticality inflation |
| Gameability | Medium — one big number | High — three inputs to fudge |
| Best for | Cross-product B2B SaaS planning | SAFe-style sequenced delivery |
| Worst for | Time-sensitive sequencing | Cross-team comparisons |
When RICE Wins
- Cross-product comparisons. A platform team weighing API rate-limit work against a billing rebuild against a mobile push fix. RICE’s common denominator (impact per effort) lets you rank apples and oranges.
- Large-scope quarterly planning. When the question is “which 4 of these 22 epics make the cut for Q3?” — RICE’s explicit Reach forces honest scoping.
- Less-experienced teams who need explicit confidence. The Confidence multiplier teaches teams to admit what they don’t know. WSJF lets you hide it.
When WSJF Wins
- SAFe / scaled-agile environments. If your org runs PI Planning, your tooling and rituals already speak WSJF. Forcing RICE in is friction without payoff.
- Time-sensitive sequencing. When two items are roughly equal in value but one expires (deal close, regulatory date, dependency unblock), WSJF’s Time Criticality input surfaces it cleanly.
- When delay cost varies dramatically across items. A SOC 2 blocker holding $400k ARR is not the same as a UI polish item, and WSJF’s Cost of Delay separates them faster than RICE’s Reach×Impact.
The Hybrid Approach
Most senior PMs end up here: RICE for quarterly planning, WSJF for sprint sequencing within the quarter. The operating model:
- Quarterly. Score every candidate epic with RICE. Cut to top 60% by score. That’s your shortlist.
- Capacity check. Sum the Effort. If shortlist exceeds team capacity, drop lowest-RICE items until it fits.
- Sprint planning. Within the committed shortlist, re-score with WSJF every 2 weeks. Highest WSJF ships first.
- Mid-quarter. If a new urgent item shows up, score it WSJF against the in-flight queue — not against the full RICE list.
Common Scoring Mistakes
- Confidence inflation. Everything scored 100%. Force a distribution: only 20% of items can be 100% confidence. The rest must justify a lower number.
- Effort fudging. Engineers underestimate work they want to do; PMs underestimate work they’ve sold to leadership. Use historical actuals, not estimates.
- Comparing scores across teams. Team A’s “Impact = 3” is not Team B’s “Impact = 3.” Scores rank within a backlog, not across them.
- Scoring in committee. Group scoring drifts toward the loudest voice. Score independently, then reconcile gaps > 30%.
- Not re-scoring after kickoff. Effort triples in week one of build. Re-score then. If WSJF/RICE drops below another shelved item, swap.
Quick-Start Template
Five sample features pre-scored. Use this to sanity-check your own scoring — if your numbers are wildly off this curve for similar work, your calibration is off.
| Feature | Reach | Impact | Conf | Effort | RICE | WSJF |
|---|---|---|---|---|---|---|
| Search redesign w/ semantic match | 4,200 | 2 | 80% | 3 | 2,240 | 5.2 |
| SAML / OIDC SSO for enterprise | 120 | 3 | 100% | 4 | 90 | 7.0 |
| Mobile push notifications fix | 8,100 | 1 | 100% | 1 | 8,100 | 6.9 |
| Bulk export to CSV | 800 | 0.5 | 100% | 1 | 400 | 2.6 |
| Dashboard color theme picker | 2,000 | 0.25 | 80% | 2 | 200 | 0.8 |
Note how RICE and WSJF disagree on the top item. RICE rewards Mobile Push (huge reach, tiny effort). WSJF rewards SSO (high time criticality, unlocks ARR). That’s the framework choice in action.