---
skill: rice-prioritisation
title: RICE Prioritisation
input: "Rank for next quarter: 1) Onboarding redesign — ~5000 users/qtr, big activation impact, ~3 person-months. 2) Dark mode — ~8000 users want it, low impact, ~1 person-month. 3) SSO for enterprise — ~400 accounts, high deal impact, ~4 person-months, low confidence."
source: representative example (hand-written)
---

# RICE Prioritisation — Next Quarter

RICE = (Reach × Impact × Confidence) ÷ Effort. Impact scale: 3 = massive, 2 = high, 1 = medium, 0.5 = low.

| # | Initiative | Reach (/qtr) | Impact | Confidence | Effort (PM) | **RICE** | Rank |
|---|------------|:-----------:|:------:|:----------:|:-----------:|:--------:|:----:|
| 1 | Onboarding redesign | 5,000 | 3 | 90% | 3 | **4,500** | 🥇 1 |
| 3 | SSO for enterprise | 400 | 3 | 50% | 4 | **150** | 🥈 2 |
| 2 | Dark mode | 8,000 | 0.5 | 100% | 1 | **4,000**? | — |

> ⚠️ Dark mode's raw score (4,000) looks high purely from reach. The low impact (0.5) is doing the real work — it's a satisfaction nicety, not a needle-mover. Flag for a "quick win" lane, not the strategic backlog.

## Recommendation
1. **Onboarding redesign** — clear top priority: high reach, massive impact, well understood (90% confidence).
2. **SSO** — high deal impact but the score is dragged down by low confidence and high effort. **De-risk first**: validate the enterprise pipeline ($ tied to SSO) before committing 4 person-months.
3. **Dark mode** — ship it as a low-cost quick win between larger projects; don't let its reach inflate its priority.

**Watch-out:** the SSO confidence is the swing factor. A week of sales discovery could move it from 50% → 80% and change the ranking.
