wowprompt

Feature Prioritisation With RICE Scoring

A ranked backlog scored with the RICE method, showing reach, impact, confidence, effort and the final score for every item. Use it when a team has more feature requests than capacity and needs a defensible order.

A table of backlog items with reach, impact, confidence, effort and calculated RICE score, sorted from highest to lowest
The output this prompt produced, unedited.

The prompt

Role

You are a product manager who makes prioritisation transparent so stakeholders can challenge the inputs rather than the outcome.

Task

Score and rank the feature list below using RICE: Reach multiplied by Impact multiplied by Confidence, divided by Effort.

Inputs

  • Product and goal for this period: [product and the goal, for example improve activation]
  • Time period for reach: [for example per quarter]
  • Feature list with any known data: [features, user numbers, estimates, requests]
  • Team capacity: [person-weeks available]

Output format

  1. Scoring scale used:
  • Reach: number of users or events in the period
  • Impact: 3 massive, 2 high, 1 medium, 0.5 low, 0.25 minimal
  • Confidence: 100, 80 or 50 percent
  • Effort: person-weeks
  1. A table sorted by score with columns: Rank, Feature, Reach, Impact, Confidence, Effort, RICE score, Basis for estimates.
  2. Capacity cut line: mark which items fit within the team capacity.
  3. Sanity check: two items whose rank feels wrong and whether the inputs or the method explain it.
  4. Inputs to validate: the estimates with the lowest confidence and how to firm them up quickly.

Quality rules

  • Show the calculation for the top three items.
  • Impact is judged against the stated goal, not general usefulness.
  • Where no data exists, estimate conservatively and set confidence to 50 percent.
  • Do not let one loud request inflate reach; count users, not mentions.
  • Keep each basis note under 20 words.
rice scoringfeature prioritisationproduct backlogroadmap planningprioritization framework

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity