A Score Is Not a Strategy

The spreadsheet says Initiative A should win. Its RICE score is 93.6. Initiative B sits at 81.2. The rows are sorted, the cells are color-coded, and the answer looks objective.

Then someone asks where the impact estimate came from. Silence.

The number wasn’t discovered. It was negotiated. Reach came from an optimistic forecast. Effort excluded the work legal and operations would have to do. Confidence was assigned after the team had already fallen in love with the idea. A formula turned those assumptions into a decimal, but it did not make them true.

That is the central mistake in prioritization: confusing a method for comparing choices with a system for making them. A framework should expose judgment, not replace it.

Most prioritization failures happen before anyone opens a scoring sheet. So settle five things first.

What outcome are we trying to change?

Not “grow the product.” A useful outcome names a customer or business change, a population, and a timeframe. Reduce the time a new small-business customer waits for their first payment. Without an outcome, prioritization becomes a contest among features.

What level are we deciding at?

“Enter a new market,” “redesign onboarding,” and “change the button label” do not belong in one sheet. Compare markets with markets, initiatives with initiatives. If two candidates can’t be described at the same level, the ranking will mislead you.

What’s non-negotiable?

Safety, legal, accessibility, security, and contractual commitments should be gates, not point-scorers competing against growth ideas. The question isn’t whether a constraint has enough reach to matter. It’s how to satisfy it wisely.

What evidence counts?

A measured reach estimate and an executive’s hypothesis should not look identical in the final sheet. Label the difference.

When will we reconsider?

Prioritization is a temporary decision made with current information. Give it an expiration condition: a date, a prototype result, a competitor move. Without one, yesterday’s assumptions quietly become today’s commitments.

Only then pick a framework, and pick one. RICE for comparing similar-sized initiatives. MoSCoW for protecting a fixed release. Kano for separating basics from delighters. WSJF for sequencing delay-sensitive work. Impact-Effort for a fast first pass. Running three scoring methods against the same list doesn’t add rigor. It adds ways to count the same preference twice.

AI raises the stakes

It can summarize thousands of comments, calculate scores, and produce a polished rationale in seconds. It can also turn weak assumptions into confident-looking recommendations faster than any spreadsheet ever could. Use it to build the evidence, challenge the inputs, run sensitivity cases, and keep the decision record. Do not let it decide which customers your strategy is willing to disappoint, or what trust and safety are worth. Those are responsibility problems, not calculation problems.

A framework earns trust when people can see how the decision was made and the organization is willing to revisit its assumptions. It loses trust when the score becomes a costume for authority.