{
  "path": "/writing/rice",
  "site": "at://did:plc:m25hu5wadnbqnt47zep7xza6/site.standard.publication/self",
  "$type": "site.standard.document",
  "title": "RICE",
  "description": "Roadmap prioritization with a simple scoring model.",
  "publishedAt": "2026-05-02T00:00:00.000Z",
  "textContent": "[RICE](https://community.atlassian.com/forums/Jira-Product-Discovery-articles/Guide-Mastering-prioritization-with-RICE/ba-p/3169901) is a prioritization model for comparing roadmap candidates with the same planning horizon.\n\nHigher scores suggest stronger relative priority, assuming the inputs are estimated consistently.\n\n## Formula\n\n$$\n\\frac{R \\times I \\times C}{E}\n$$\n\n| Symbol | Input      | Meaning                                       |\n| ------ | ---------- | --------------------------------------------- |\n| R      | Reach      | Number of affected entities in a time period  |\n| I      | Impact     | Expected improvement for each affected entity |\n| C      | Confidence | Certainty in the reach and impact estimates   |\n| E      | Effort     | Total work required to deliver the project    |\n\n## Inputs\n\n| Input      | Unit                     | Notes                                                                      |\n| ---------- | ------------------------ | -------------------------------------------------------------------------- |\n| Reach      | Entities per time period | Use a consistent period, such as users per month or transactions per day.  |\n| Impact     | Numeric scale            | Use one scale across all candidates. A 1-5 scale keeps scoring simple.     |\n| Confidence | Percentage               | Use `0-100%` as a multiplier. Lower confidence reduces speculative scores. |\n| Effort     | Time or capacity         | Include research, design, development, testing, launch, and coordination.  |\n\n## Example\n\n| Project           | Reach | Impact | Confidence | Effort | Score |\n| ----------------- | ----: | -----: | ---------: | -----: | ----: |\n| Add dark mode     | 1,000 |      3 |        80% |      2 | 1,200 |\n| Refactor codebase |   500 |      4 |        70% |      4 |   350 |\n| Add new feature   | 2,000 |      5 |        60% |      6 | 1,000 |\n\nThe example assumes reach is measured in users per month and effort is measured in person-weeks."
}