Prioritization Without Frameworks

Every PM has been forced to do a RICE scoring exercise. Reach, Impact, Confidence, Effort. Multiply, divide, sort. The output looks rigorous. The numbers are crisp. The top of the list 'wins.'

The problem is that none of the four inputs are knowable to the precision the formula demands. Reach is a guess. Impact is a hope. Confidence is the PM's vibes. Effort is engineering's guess multiplied by 1.5 because they know it will slip. Four guesses combined into a 'rigorous score' is not rigor. It's false precision.

The real problem RICE is trying to solve is harder: comparing apples and oranges in a constrained capacity. The framework doesn't solve it. It just hides the comparison inside math.

Replace the four-dimensional scoring with a two-dimensional plot.

X axis: how confident are we that this moves a metric we care about? Low, medium, high. Pick one. No half-steps.

Y axis: how reversible is the bet? Cheap to reverse, medium, multi-quarter migration. Pick one.

Plot each item. Items in the top-right corner — high confidence, cheap to reverse — go first. Items in the bottom-left — low confidence, hard to reverse — go last or never.

The middle is where conversation happens. High confidence + hard to reverse means the team needs more pre-work before committing. Low confidence + cheap to reverse means you can ship it as an experiment and let data decide.

This isn't a framework. It's a question structure that forces the team to be honest about two things at once: how sure are we, and how stuck would we be if we were wrong?

Confidence × reversibility beats four-factor scoring almost every time.

Prioritization isn't a math problem. It's a judgment problem with capacity constraints. The two-by-two doesn't solve the judgment. It surfaces the judgment so the team can debate it openly.

In RICE land, the team debates the formula. 'Is the impact a 3 or a 4?' That debate doesn't surface the real disagreement. The real disagreement is about whether the bet is worth making at all. The formula obscures it.

In two-by-two land, the team debates the actual quadrant. 'I think this is medium confidence, not high.' That sentence is closer to the real disagreement. The conversation moves faster. The decision lands cleaner.

Frameworks are useful when the team is new and doesn't yet have shared intuition for trade-offs. RICE gives a new team a structure to argue inside. The arguments are productive even if the formula isn't predictive.

Frameworks are also useful for documenting decisions to non-product audiences. An exec who wasn't in the room will absorb 'top RICE-scored items shipped this quarter' faster than 'top two-by-two items.' That's a communication function, not a decision function.

The failure mode is using frameworks as decision functions when they're communication functions. The framework didn't decide. The team did. The framework just made the decision look more legible after the fact. Knowing the difference matters.