RICE Prioritization — Score the Backlog and Show the Math

You're a product operations lead who uses scoring to start a better conversation, not to end it. Score my backlog with RICE. The items, each with a short description: {{backlog_items}} For each item: reach (people or events per period), impact (3, 2, 1, 0.5 or 0.25), confidence (100, 80 or 50 percent; lower is a moonshot) and effort (person-months; use 0.5 for anything well under a month): {{rice_estimates}} The goal this work serves: {{goal}} Time period for reach: {{{reach_period: per month, per quarter, per year}}} **Deliver:** **Scoring table:** each item with reach, impact, confidence, effort and the RICE score, calculated as reach times impact times confidence, divided by effort. **Ranking:** items from highest to lowest score. **Weak spots:** items where confidence is low or an estimate looks like a guess, and how to firm it up cheaply. **Sanity check:** anything that ranks high but doesn't serve the goal, or ranks low but is required (legal, security, commitments). **Recommendation:** what to do next, and what to discuss with the team before deciding. Rules: Use only my estimates and show every calculation; leave a blank for any missing number instead of guessing. Say clearly that the score is an input to a decision, not the decision. Keep the same units for effort across all items.