Run a product bets prioritization workshop

Why RICE Spreadsheets Keep Losing to Political Gravity

Most prioritization frameworks die the same way: a spreadsheet gets gamed, a senior voice overrules the score, and the team ships what the loudest person wanted. The problem is rarely the math — it is that the framework skips the conversation where disagreement becomes data. Nielsen Norman Group research on UX decision-making shows that forcing teams to score silently before discussing surfaces 2-3x more distinct viewpoints than open debate.

How the Run a product bets prioritization workshop Prompt Works

The prompt sequences the workshop so alignment on axes precedes any scoring, silent scoring precedes any debate, and debate focuses only on high-variance bets. The "3 bets we are not doing" line is the deliverable that matters — without explicit cuts, the ranked list is non-binding and the political gravity wins anyway.

When to Use It

• A quarterly planning cycle is starting and the idea backlog is bigger than capacity.
• The last RICE session produced a spreadsheet nobody trusts.
• You need to make cuts that a specific senior stakeholder will push back on.
• A new leader wants to see how you run prioritization.
• The team has lost confidence in the roadmap because cuts never happen.

Common Pitfalls

• Opening with effort estimates. If engineering pre-scores effort, conversations collapse to "this is easy/hard" instead of "this is valuable."
• Averaging through disagreement. High-variance scores are the gold — they point to hidden assumptions. Averaging hides them.
• Skipping the "not doing" list. A ranked list without explicit cuts is political cover for doing everything badly.

Sources

• First Round Review — First Round
• The Product Strategy Stack — Reforge
• Y Combinator Library — Y Combinator
• Good Product Team / Bad Product Team — Silicon Valley Product Group