Back to the Playbook
Define & DesignDD-03
How to use RICE
Score independently before discussion and preserve legitimate reasons to choose out of score order.
Product statusAvailable now
Input4 required inputsRoadmap candidates · Reach data and impact judgements · Confidence evidence and person-month estimates
SkillsCalculate RICE scores · Prepare task context · Review an artifact against agreed criteriaProduct Manager + Product Manager Agent
OutcomeRICE score sheet: definitions, reproducible calculation table, ranked comparison and recorded exceptions.Artifact: RICE score sheet
Owner
Product Manager
Human + Agent
Participants · Agents
EngineerDesignerProduct Manager Agent
Trigger
Roadmap candidates are evaluated over one reach period.
Required context
JiraRoadmap candidatesAnalyticsReach data and impact judgementsArchitectureConfidence evidence and person-month estimatesProduct BrainInitiative focus and approved Product Brain guidance
Optional context
Customer evidenceCustomer evidence per candidate
Skills
Calculate RICE scoresPrepare task contextReview an artifact against agreed criteria
Suggested conversation arc
- 1Agree comparison basisFix the reach period, impact scale 3/2/1/0.5/0.25, confidence interpretation and whole-team effort units.Skills: Prepare task context
- 2Calculate evidence-backed scoresCapture independent estimates and compute reach × impact × confidence ÷ effort. Expose missing evidence and prohibit zero effort denominators.Skills: Calculate RICE scores
- 3Discuss outliers and dependenciesCompare differences in estimates and inspect low-confidence high scorers; identify enabling dependencies or strategic commitments the formula does not capture.
- 4Confirm the chosen orderCheck the final order and clearly record exceptions to RICE, with rationale rather than changing numbers to justify a desired answer.Skills: Review an artifact against agreed criteria
Output
RICE score sheet: definitions, reproducible calculation table, ranked comparison and recorded exceptions.
Artifacts
Creates: RICE score sheet
What good looks like
- Confidence percentages are converted correctly and effort is positive.
- All candidates use comparable reach periods and effort units.
- No invented reach data and no automatic promotion of the highest score.
Quality gate
The Product Manager confirms the order and the reasoned exceptions.
Destination
RoadmapJira
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Choose the path that matches your role.
Set the Product AI direction with us, or test the shared Product Brain on real work with Jira and code.