Session Brief: RICE Scoring

Goal

Artifact: RICE Scores

Working Question

Which initiative delivers the greatest expected outcome per invested effort, and where is estimation uncertainty so high that the order says little?

Context

Initiative list with descriptions; known reach metrics (active users per month, funnel numbers); historical impact of similar features if available; rough effort range from past projects.

Setup

• Format: Method session
• Duration: 30-60 min
• Mode: Workshop or async
• Participants: One PM or PO as owner; one Engineering Lead for effort estimates; one researcher or analyst for reach data; optionally designer for impact assessment.
• Owner: One PM or PO as owner
• Participation mode: Team round, shared work and alignment
• Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward RICE Scores. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Table with columns Initiative, Reach, Impact, Confidence, Effort, RICE score; predefined scales (Impact: 0.25 / 0.5 / 1 / 2 / 3; Confidence: 50%/80%/100%); link to initiative description.

Preparation

Create table. Make definitions per factor visible (Reach = number of users per quarter; Impact = quantitative measure on outcome; Confidence = percentage; Effort = person-months). Align team on Impact and Confidence scales before estimating.

Agenda

1. Section 1: Calibrate scales (10 min) Owner: Facilitator Action: Define scale per factor: Reach in absolute users or events per quarter; Impact as multiplier (0.25 minimal / 3 massive); Confidence in %; Effort in person-months. Score one example initiative together for calibration. Hint: If scales remain unclear, participants score in different units. Calibration is mandatory, not optional. Output: RICE Scores

2. Section 2: Estimate Reach (10-15 min) Owner: Facilitator Action: Per initiative: how many users (or events) does the feature touch per quarter? Use numbers from baseline metrics. If uncertain, use range with mean. Hint: Reach is often overestimated. A feature in Settings does not reach 100% of users. Check funnel data, do not guess. Output: Ranked List

3. Section 3: Impact and Confidence (10-15 min) Owner: Facilitator Action: Per initiative: Impact level (0.25/0.5/1/2/3) on outcome goal. Confidence level (50% speculative / 80% tested / 100% proven). If Confidence <50%, park initiative or validate first. Hint: Impact = 3 only with documented evidence (past data, A/B tests). Inflation devalues the scale. Output: Assumption Log

4. Section 4: Effort and score (10-15 min) Owner: Facilitator Action: Estimate effort per initiative in person-months (including design, QA, rollout). Score = (Reach x Impact x Confidence) / Effort. Sort in table. Hint: Effort is often underestimated. If team historically needs 1.5x longer than estimated, apply multiplier. Otherwise expensive initiatives move upward wrongly. Output: RICE Scores

5. Section 5: Sanity check and sorting (10 min) Owner: Owner Action: Review top-5 ranked initiatives. Gut check: does order intuitively make sense? If not, revisit estimates. Document assumptions per top initiative. Hint: RICE is tool, not oracle. If top-1 is obviously nonsensical, do not enforce ranking; inspect estimates. Output: Ranked List

6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: RICE Scores

Closeout

• Update result artifact: RICE Scores
• Define location, version, and review recipients.
• Define owner, next step, and review date.

RICE Scores: RICE Scoring

Working Question

Which initiative delivers the greatest expected outcome per invested effort, and where is estimation uncertainty so high that the order says little?

Context

Initiative list with descriptions; known reach metrics (active users per month, funnel numbers); historical impact of similar features if available; rough effort range from past projects.

Participants

• Owner: One PM or PO as owner
• Participants: One PM or PO as owner; one Engineering Lead for effort estimates; one researcher or analyst for reach data; optionally designer for impact assessment.

Input

Table with columns Initiative, Reach, Impact, Confidence, Effort, RICE score; predefined scales (Impact: 0.25 / 0.5 / 1 / 2 / 3; Confidence: 50%/80%/100%); link to initiative description.

Template

RICE Scoring Working Matrix

Output artifacts

• RICE Scores:
• Ranked List:
• Assumption Log:

Decision or recommendation

What consequence follows from the matrix?

Completion Check

• RICE Scores is complete enough for review:
• Location:
• Version / status:
• Review by:
• Next step:

Next Step

• Review result
• Mark open questions
• Schedule review or decision