Prioritize Your Feature Backlog with RICE Scoring and Flagged Weak Assumptions
Get a ranked RICE scoring table for your pasted backlog, with the math shown, weak assumptions flagged, and a short list of what to build next.
You getScoring table, top 3 to build next and weak assumptions to validate
Prompt
You are a senior product manager who runs quarterly planning with RICE scoring.
Job: prioritize the feature backlog I will paste right after this prompt. Before scoring, ask me these questions in one numbered message and wait for my answers:
1. How many users or accounts will each feature reach per quarter, and where does each number come from (analytics, survey, guess)?
2. How many person-months will each feature take, and who estimated it?
3. What is this quarter's main goal (e.g., activation, retention, revenue) for judging Impact?
4. Any deadlines, dependencies or commitments that should override the score?
Rules:
- Use standard scales: Impact 3, 2, 1, 0.5, 0.25; Confidence 100%, 80%, 50%. RICE = Reach x Impact x Confidence / Effort.
- Use only my Reach and Effort numbers. If one is missing, mark the feature "missing" and leave it unranked.
- Flag with ⚠ any score resting on a guess, a single person's estimate, or an Impact you inferred, plus a one-line reason.
- Show the calculation for every score so I can check it.
Output format:
1. Scoring table: Rank | Feature | Reach | Impact | Confidence | Effort | Calculation | RICE | Weak assumption
2. Top 3 to build next, one sentence each on why.
3. Weak assumptions to validate, with the cheapest way to check each.
4. Overrides from deadlines or dependencies.
End with one line naming the biggest risk in this ranking.Example output
Tips and common edits
Why this works
- Asking for reach and effort sources first keeps the model from inventing numbers and exposes which inputs are guesses.
- Showing the calculation in each row lets you audit every score in seconds.
- Flagging weak assumptions with a cheap validation step turns the ranking into an action plan, not a false certainty.
Use before quarterly or sprint planning. Paste your backlog list into ChatGPT, Claude or Gemini, then have rough reach numbers, effort estimates and your quarter's goal ready to answer.
Common edits
- Swap RICE for ICE scoring if you lack reliable reach data.
- Ask for the table as CSV so you can paste it into a spreadsheet or Jira.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Build a Competitor Feature Comparison and Positioning Summary
Get a feature comparison table with every cell tagged as user-provided or needing verification, plus win/lose points, a positioning statement and a fact-check list.
Analyze Your Product Funnel and Find the Biggest Drop-Off to Fix First
Paste your funnel step counts and get a conversion table, the largest leak flagged with reasoning, and one testable fix per step with an expected lift range.
Design an A/B Test Plan with Sample Size Math and Pre-Set Stop Rules
Get a complete A/B test plan with one primary metric, a clear hypothesis, a worked sample size calculation, runtime, and stop rules fixed before launch.
Diagnose a Sudden Metric Drop with a Ranked List of Likely Causes
Get a ranked table of likely causes for a metric drop, covering tracking, segments, platforms, releases, seasonality and external factors, each with an exact check.
Run a Post-Launch Retrospective Comparing Goals to Actual Results
Get a blameless launch retrospective with a goal-versus-actual table, facts kept apart from causes, and lessons that each carry an owner and a change for the next launch.
Write an Event Tracking Plan Where Every Event Maps to a Success Metric
Get a tracking plan table with object_action event names, exact triggers, typed properties and the success metric each event feeds, plus a list of events to cut.