Every few years a new prioritisation framework arrives with the promise of objectivity. It has a formula, a spreadsheet template and a workshop. Teams adopt it, score their backlog, and feel a satisfying sense of order.
Then the scores produce a ranking that nobody believes, and the real decision happens in a side conversation anyway.
The framework is not the problem. The expectation is.
A score is an argument in disguise
A prioritisation score combines several judgements into a single number: how many people are affected, how much they care, how confident we are, how much effort it takes. Each of those inputs is a guess. Combining guesses does not produce a fact; it produces a compressed argument.
Compression is useful when it forces the argument into the open. It is dangerous when it hides it. A RICE score of 42 looks objective. It is really saying: we believe this reaches a certain number of people, with a certain intensity, with a certain confidence, for a certain cost, and we are willing to defend those beliefs.
The value of the exercise is in the conversation about the inputs, not in the output ranking.
Where scores go wrong
False precision. A score of 42.7 versus 41.9 is not a meaningful difference. It is two estimates with wide error bars pretending to be a decimal.
Shared denominators. Reach and impact are often estimated with different levels of rigour. A well-researched reach estimate combined with a guessed impact score produces a number that looks more reliable than either input.
Gaming. Once a score determines funding, people learn to score. Confidence goes up, effort goes down, reach expands. The number stops measuring anything except the skill of the person filling in the template.
Missing displacement. Most frameworks score an item in isolation. They do not ask what the item displaces. A score of 40 might be excellent if it costs nothing else; it might be terrible if it consumes the only team that can work on the more important problem.
Four questions that matter more
Before the score, ask four questions.
What problem does this solve, and for whom? If the answer is a segment rather than a specific situation, the estimate is probably fiction.
How confident are we, and why? Confidence should be tied to evidence: a previous experiment, a customer commitment, observed behaviour. “The team feels good about it” is a data point about the team, not the market.
What does it cost to build, and to keep? The second half is usually missing. Every feature has an ongoing cost: support, maintenance, cognitive load, surface area. A cheap build with an expensive life is not cheap.
What does it displace? The real currency of prioritisation is opportunity cost. Every yes is a no to something else, and the something else is usually more informative than the item itself.
Make disagreement visible
The most useful thing a prioritisation process can do is expose where people disagree.
If two people score the same item very differently, the difference is the interesting part. One of them has information the other lacks, or they are optimising for different outcomes, or they have different models of the user. Surfacing that disagreement is more valuable than averaging it away.
A simple practice: score independently, then discuss the largest gaps rather than the final ranking. The conversation tends to reveal assumptions that would otherwise stay buried until after launch.
The decision log
Prioritisation without memory becomes a quarterly argument from scratch. A short decision log (what was chosen, what was deferred, what evidence was used, what would change the call) turns the exercise into a cumulative body of judgement.
It also makes deferral honest. An item that was explicitly deferred, with a reason, is different from an item that quietly fell off the list. The first can be revisited. The second usually reappears as an emergency.
What good prioritisation looks like
It looks less like a ranked list and more like a set of commitments with reasons attached. It is willing to say: this is the problem we are choosing to solve now, this is what we are choosing not to solve, this is the evidence behind the choice, and this is what would make us change our mind.
That is not a formula. It is a story about evidence, told clearly enough that other people can challenge it.
A prioritisation everyone agrees with is usually one that avoided the hard choice. A useful one makes the hard choice visible, and gives the team a way to revisit it without starting over.