Sign InGet Started

Estimating Reach for RICE Scoring

Quantify how many users or events an initiative touches in your scoring window.

Count users or events affected in a fixed period (usually a quarter). Use analytics where they exist; otherwise proxies like funnel volume, segment size, or support volume—and lower Confidence when you are guessing.

Outcome: Defensible Reach numbers that make RICE comparisons meaningful.

Reach estimation practices from analytics and PM literature, condensed for the site.

ProductIntermediate15–30 minutes per initiative

Prerequisites

  • Agreement on the RICE time window
  • Access to some usage or customer data

Reach is exposure over your scoring window—not “value.” Value shows up in Impact. Reach answers how many people or events feel the change.

Start by naming the unit (unique users, sessions, etc.) and the period. Pull counts from product analytics for existing surfaces; for new ideas, use funnel entry, segment size, or indirect signals—and write one line of reasoning next to each number so the team can re-score later without a memory contest.

Other Skills in This Method

Calculating RICE Scores

Run the full formula on a shared sheet.

Calibrating Confidence

Align confidence with evidence quality.

Mapping Effort to Person-Months

Normalize Effort so the denominator is fair.

Learn First

Calculating RICE Scores

Know how Reach plugs into the formula before tuning it.

Learn Next

Calibrating Confidence

Pair Reach with confidence that matches your data quality.

Frequently Asked Questions

What if I have almost no data?

Use the smallest number you can defend, note the source, and cut Confidence. Consider a research spike instead of a full build bet.

Internal vs customer-facing Reach?

Keep them comparable—same units—or run separate scoring sessions so 20 internal users do not fight 20k customers.