Prioritization is a beloved management practice. There are frameworks for it — RICE, ICE, MoSCoW, WSJF. There are tools for it. There are consultants who specialize in it. It is presented as the solution to the problem of doing too much.

It isn't. Or more precisely: prioritization is a solution to a different problem than the one most organizations have.

The prioritization trap

Here's how the trap works:

An organization has twenty things it could do. It runs a prioritization exercise. It ranks the twenty things. The top seven become "priorities." The others become "backlog" or "not this quarter."

The organization now has seven priorities. Seven is fewer than twenty. The exercise feels like it produced focus.

It didn't. A ranked list of seven is not a focused strategy. It's a shorter wish list.

Prioritization is ranking. Focus is cutting. These are not the same operation.

The distinction Felipe Castro made

Felipe Castro articulated this clearly: "Many people believe focus is prioritization — creating a laundry list of dozens of 'priorities.' But focus is cutting. Prioritization is ranking. A list of 20 priority projects might be ranked. It is not focused."

The organizations that mistake prioritization for focus end up with a ranked queue. The top item gets most of the attention. Items two through seven get the rest — spread thin, none of them receiving enough concentration to move decisively.

The organizations that understand focus end up with one to three bets. The rest is explicitly not being done. Not ranked lower. Not being done.

Why ranking feels like focus

Ranking is psychologically easier than cutting. When you rank twenty things, nothing is rejected. Everything stays on the list. Everyone's priority is still on the list — just lower. The CPO's platform migration is still there. The CFO's margin program is still there. They're just ranked six and seven.

Cutting means someone's priority is gone. That's a conversation. That's political. That's a real decision with real consequences. Ranking avoids that conversation. Ranking is conflict resolution through math.

The cost of avoiding the conversation is paid by the organization for the entire next quarter, distributed invisibly across every team that was promised something that ranking implied was on the path to getting done.

The three organizations

There are three distinct types of organizations on this spectrum:

The unfocused organization has no prioritization 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 prioritization frameworks are designed to fix.

The prioritized organization has a ranking practice. The ICE score. The MoSCoW framework. The quarterly roadmap review. Everything is ranked. The organization feels disciplined. But the top seven items still exceed available capacity. Prioritization performed without capacity accounting is still a wish list — just a numbered one.

The focused organization has made explicit cuts. It has a Do-Not list — an enumeration of things the organization has chosen, deliberately, not to pursue. The Do-Not list is as important as the priority list. It's what makes the priority list credible. An organization that can name what it's not doing has decided. An organization that can only name what it's ranked hasn't.

The capacity test

The test that separates prioritization from focus is the capacity test.

Take your top three to five priorities. For each one, name the two or three senior people it depends on and what percentage of their week it needs to proceed. Add up the percentages per person across all priorities.

If anyone is over 100% — the list is fiction. Not partially wrong. Entirely wrong. You have a wish list with rankings.

The prioritization exercise was supposed to give you a list you can execute. If the capacity accounting shows you can't execute it, the list isn't done. You haven't prioritized. You've ranked.

The Vindaris position

Strategy tools that help organizations rank priorities without requiring capacity accounting make the problem worse, not better. 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.

Prioritization without capacity accounting is political fiction with a framework.