Prioritisation is the most beloved management practice of the last twenty years. There are frameworks for it — RICE, ICE, MoSCoW, WSJF, value-versus-effort matrices. There are tools for it. There are consultants who specialise in nothing else. It is presented, more or less universally, as the solution to the problem of trying to do too much.
It isn't. Or to be more precise, prioritisation is a solution to a different problem than the one most leadership teams actually have. And that mismatch is why so many companies that pride themselves on disciplined prioritisation are still, two quarters later, surprised that they're not moving.
The trap, mechanically
Here's how it plays out, and you've probably watched a version of this.
An organisation has twenty things it could do. It runs a prioritisation exercise. The frameworks come out, the scores get assigned, the spreadsheet gets filled in. The twenty things are ranked. The top seven are now "priorities." The bottom thirteen are "backlog" or "not this quarter" or "below the line."
The organisation now has seven priorities. Seven is fewer than twenty. The exercise feels rigorous. The deck looks great. Everyone leaves the room with a sense that focus has been created.
Six weeks later, none of the seven is moving with any real force. Each is getting some attention, none is getting enough, and the team is exhausted from trying to do all of them at half-velocity. The ranking did its job. The focus didn't appear.
This is the paradox: prioritisation is ranking. Focus is cutting. These are not the same operation, and only the second one produces strategic movement.
Why ranking feels like focus
Ranking is psychologically easier than cutting, which is why almost every prioritisation exercise produces a ranked list rather than a focused one.
When you rank twenty items, nothing gets rejected. Everything stays on the list. The CPO's platform migration is still there. The CFO's margin programme is still there. The CRO's enterprise motion is still there. They've just been arranged in an order. No one had to be told their thing isn't happening. No conversation got hard. No relationships got strained.
Cutting is different. Cutting means someone's priority is gone — not deferred, not below the line, gone. That's a conversation. That's political. That has real consequences for real people in the room. Ranking lets you avoid that conversation entirely. Ranking is conflict resolution through arithmetic — and the cost of avoiding the conflict is paid by the entire organisation, in slow motion, for the rest of the quarter.
The cost shows up as the seven priorities all getting partial attention, none of them getting enough to move decisively, every team being asked to contribute to too many things, and the eventual quarter-end conclusion that "we tried to do too much" — which is the same conclusion the prioritisation exercise was supposed to prevent.
The three kinds of organisation
There are three distinct types of organisations on this spectrum, and most companies misidentify which one they are.
The unfocused organisation has no real prioritisation practice. Everything is equally important, everything competes for the same attention, the CEO decides reactively week by week based on what's loudest. This is what most prioritisation frameworks are built to fix, and they do fix this version — moving from chaos to ranking is a real improvement.
The prioritised organisation has graduated to ranking. There's a scoring framework. There's a quarterly roadmap review. The deck is clean. The organisation feels disciplined. But the top seven items still exceed the available capacity by a wide margin, and nobody has done the math to confirm that. Prioritisation performed without capacity accounting is still a wish list — just a numbered one. This is the trap most mid-size companies are stuck in, and they don't know it because the appearance of discipline is mistaken for the substance of it.
The focused organisation has made explicit cuts. It has a Do-Not list, which is just as important as the priority list — possibly more important. The Do-Not list is what makes the priority list credible. An organisation that can name what it's deliberately not doing has decided. An organisation that can only name what it's ranked has only delayed deciding.
The capacity test
There is a test that cleanly separates prioritisation from focus, and it takes ten minutes to run.
Take your top three to five priorities. For each one, name the two or three senior people whose effort it depends on, and the percentage of their week the priority needs to actually proceed. Then add the percentages up across all priorities, per person.
If anyone is over 100% — and someone will be, often badly — the list is fiction. Not partially wrong. Entirely wrong. You have a wish list with rankings attached.
This is the moment most leadership teams realise that their "prioritisation" was the easy part, and the hard part — cutting until the math works — was the part they avoided. The capacity test is the brutal little exercise that surfaces whether the prioritisation produced a strategy or produced a numbered fantasy.
The good news: once you've run it once, you can't unsee it. The next prioritisation exercise becomes a different conversation, because the question shifts from "what's most important" to "what fits in the capacity we actually have." Those are very different conversations, and only the second one produces focus.
The Vindaris view
Strategy tools that let organisations rank priorities without forcing capacity accounting make the problem worse, not better. They give the appearance of disciplined decision-making while letting the underlying fiction stand. The result is a leadership team that feels rigorous and a workforce that's quietly drowning.
The system should make it structurally impossible to call something a priority without naming the bandwidth behind it, and structurally obvious when that bandwidth is already committed to something else. When that's the case, prioritisation conversations stop being abstract debates about importance and start being concrete trade-offs about capacity — which is what they should have been all along.
Prioritisation without capacity accounting is political fiction with a framework. The framework just gives it better-looking footnotes.