RICE Scoring Sheet for Product Managers: template, structure and example

When to use it

Reach for it in the Plan phase when you have more validated candidates than capacity and need to sequence them defensibly. It works best when several items compete for the same team and you want scoring criteria, rationale and trade-offs in one place. Use it to make the recommendation transparent before you move into a MoSCoW Prioritisation Document.

When not to use it

If you have a single obvious priority, or the direction itself is still unvalidated, RICE adds ceremony without adding a decision. When items are so different that Reach and Effort are not comparable, or when the call is really about strategic fit rather than throughput, a discovery brief or opportunity assessment will serve you better.

What you need before you start

• The list of features, ideas or backlog candidates being compared, and the problem or outcome each targets
• Reach estimates: users or accounts affected in a defined period, with the basis for each count
• Impact and Effort estimates, with the scale used and the assumptions behind the person-time
• The evidence base behind reach, impact and confidence, including recency and any contradicting signals
• Capacity limits and constraints for the period being planned
• Named contributors from Product Owner, design, engineering, data, delivery and customer insight

Recommended structure, section by section

1. Summary — The top-ranked items, the outcome of the scoring, the spread between them, and the recommendation the sheet makes.
2. Purpose and Scope — The purpose of the sheet, the boundaries and exclusions of its scope, the audience it serves, and the decisions and outcomes it is meant to inform.
3. Items Scored — The features or ideas being compared, and the problem or outcome each targets.
4. Reach — The number of users or accounts each item affects in a defined period, and the basis for the count.
5. Impact — The expected effect of each item on the target outcome, and the scale used to rate it.
6. Confidence — The confidence in the reach, impact, and effort estimates for each item, and what drives it.
7. Effort — The estimated effort in person-time for each item, and the assumptions behind the estimate.
8. RICE Scores and Ranking — The calculated RICE scores, the resulting ranking, and the spread between items.
9. Assumptions and Sensitivities — The assumptions in the estimates, the sensitivities, and how much they could move the ranking.
10. Evidence and Confidence — The evidence base behind the sheet, the quality and recency of its sources, the coverage and consistency it provides, the contradicting signals, and the confidence level in the conclusions.
11. Recommended Next Steps — The items to take forward, the estimates to firm up, and the next action.
12. Ownership and Review — Who owns the sheet, the accountable owners and contributors, where the source evidence lives, the review rhythm and decision rights, and the events that trigger a revisit.

What good looks like

A good RICE Scoring Sheet is easy to follow and gives you confidence in the thinking behind it, because the ranking rests on evidence rather than personal preference. It states assumptions, shows what has been agreed, and makes trade-offs and sensitivities visible. A new reader can describe the sheet's purpose, understand the recommended order of work, see who approved it and identify what would make it need updating.

Quality checklist

• The recommendation and the top-ranked items are visible near the start
• Every score is supported by evidence, with sources dated and contradicting signals noted
• Assumptions and sensitivities are stated, showing how much they could move the ranking
• The final order can be traced back to the evidence, not to preference
• Named accountable owners and contributors are recorded, and reviewers have confirmed the decision required, risks, dependencies and next review date
• Final sign-off sits with the Product Manager, with agreement from accountable product, design and delivery leads

Who creates it, and when

In Gensudo this document is a governed template for:

• Product Manager in the Plan phase (as “RICE Scoring Sheet”)

Where it sits in the flow

Before this document: Opportunity Assessment for Product Managers · Customer Problem Statement for Product Managers

This unblocks: Prioritisation Framework for Heads of Product · Product Roadmap for Product Managers

Frequently asked questions