Structuring a prioritization call you still make yourself
Roadmap creation is a top time-saver PMs cite, but only 14.3% let AI touch prioritization directly, and that reluctance is correct. A model can lay out a RICE table, surface missing inputs, and show how sensitive the ranking is to soft numbers, without pretending it knows your reach and impact. Used this way it structures the debate instead of ending it.
You are helping a product manager structure a prioritization exercise. You organize and expose assumptions; I make the call. Strategy and current focus: {{strategy_context}} Initiatives to compare, with whatever reach / impact / confidence / effort data I have: {{initiatives}} Do the following: 1. Before scoring, list every input you're missing per initiative and ask me for it. 2. Build a RICE table (Reach x Impact x Confidence / Effort). Use only values I provided. 3. Add a "confidence flags" column marking any score that rests on a guess rather than data. 4. Show a short sensitivity note: which one or two soft inputs, if wrong, would reorder the ranking. 5. Offer three sequencing options (e.g., highest-RICE-first, quick-wins-first, strategic-bet-first) with the trade-off of each. Rules: - Do not invent reach, impact, or effort numbers. Where I didn't give a value, put "[estimate needed]" and leave the score blank rather than guessing. - State that the ranking is a starting point for a team discussion, not a decision. - Don't cite benchmark conversion rates or effort estimates from memory; those must come from my data.
Fill in your details and the prompt updates live — then copy.
Missing inputs I need: pricing redesign has no reach or impact estimate; confidence isn't set for any item. | Initiative | Reach | Impact | Confidence | Effort | RICE | Flags | |---|---|---|---|---|---|---| | Guided source picker | 2,000 | 3 (high) | [estimate needed] | 3 wk | — | impact is a guess | | Onboarding checklist | all new | 2 (med) | [estimate needed] | 1 wk | — | reach not quantified | Sensitivity: if the picker's impact is actually medium not high, the checklist likely outranks it. Ranking is a starting point for the team, not a decision.
The full workflow
- Answer the model's questions about missing reach and effort data before accepting any scores
- Replace every [estimate needed] with a real figure or an explicit team estimate
- Take the sensitivity note into the prioritization meeting as the thing to debate
- Record the final call and the reasoning yourself — the ranking doesn't decide, you do
Watch out for
A confident RICE table hides how much is guesswork. If Impact and Confidence are vibes, the precise-looking ranking is false precision — treat it as a way to structure the argument, not settle it.
Roadmap items and strategy are confidential. Keep initiative names generic or use an approved enterprise tool; don't expose next quarter's bets in a consumer account.
Models trained on old data will happily supply 'typical' conversion or effort benchmarks. Those don't reflect your product; only your own numbers belong in the scoring.
Where this comes from
Every use case on this site is grounded in real reports from working product managers — not invented by us.