Most leadership teams don't lack a prioritisation process. They lack the willingness to commit; to say out loud that some things on the list won't happen this year. How to prioritise strategic initiatives is a question they return to every planning cycle. The answer they usually get is a ranked list. The answer they actually need is a shorter one.

The list that never shrinks

Here's the pattern we see repeatedly. A strategy gets signed off. It identifies four or five areas of focus. By the time it reaches the operating level, those five areas have spawned fourteen initiatives. Each team has added its own interpretation, its own adjacent priority, its own urgent thing that fits broadly under the strategy. Nobody has said no to anything, because nobody has been asked to.

The result is not a bad strategy. It's a diluted one. Resources get split across too many fronts, progress is visible everywhere and meaningful nowhere, and when the year-end review comes around, the honest answer is that the strategy moved sideways rather than forward.

Ranking the fourteen initiatives doesn't solve this. It creates the illusion of prioritisation while leaving the underlying problem intact — too many things in motion, too few done well.

Ranking is not choosing

A ranked list is a comfort mechanism. It tells everyone their initiative is still alive, just positioned differently. Number seven on the list is still funded, still staffed, still in the quarterly review. The team behind it is still busy.

"You can't prioritise without a view on where you're playing. Without that anchor, every initiative has an equal claim on your attention."

Real prioritisation requires a decision about what you will not do. That's the uncomfortable part, and it's why most organisations avoid it. Stopping something that's already in motion means someone's work gets deprioritised, someone's budget disappears, someone must explain to their team why the project they've been building is being shelved. The social cost is immediate. The strategic benefit feels distant.

So, the list stays long. And the strategy stalls.

What choosing requires

The reason so many initiatives feel equally urgent is that the strategy hasn't made the trade-offs explicit. When everything is a priority, it usually means the underlying question, where are we playing and where are we not, hasn't been answered clearly enough to force a real choice.

The sequencing matters here. Before you can meaningfully prioritise, you need clarity on which market spaces you're committing to; the competitive arenas where you've decided to show up and win. Then, within those spaces, what do customers genuinely value, specifically enough to shape what you build and how you resource it? And only then: which initiatives sit at the intersection of those two? Without that sequence, prioritisation becomes an internal negotiation — whoever argues hardest or has the most senior sponsor wins. The filter is internal rather than external, which means it's political rather than strategic.

When you work through market spaces first, something useful happens. You stop asking "is this initiative important?" and start asking, "does this initiative serve the customers we've chosen, in the spaces where we've decided to compete?" That question is considerably easier to answer. And it makes the cutting conversation less contentious, because the grounds for the decision are external.

What this looks like in practice

We worked with a mid-sized product company that had built up an initiative list of fourteen items across their annual plan. Everyone had been approved. Everyone had resource attached. The leadership team knew, privately, that they couldn't execute all fourteen well — but nobody had called it.

When we worked through where they were genuinely positioned to win and mapped that against what their core customers were trying to achieve, three strategic focus areas became clear. Not fourteen. Not even seven. Three areas where the company had real right to compete, real customer pull, and the capability to deliver something differentiated.

Eleven of the fourteen initiatives either mapped to one of those three areas or they didn't. The ones that didn't weren't bad ideas. They simply weren't bets worth making given where the company had chosen to play. Stopping them freed up the capacity to do the remaining three properly.

"The question isn't which initiative is most important. It's which ones you'll resource fully — and which ones you'll stop."

That reframe changed the conversation entirely. It moved from ranking to deciding.

Before the next planning cycle

If you're heading into a planning cycle with a long list and a sense that everything is urgent, the first question worth asking isn't about the initiatives at all. It's about the strategy underneath them.

Can your leadership team articulate, with genuine specificity, which market spaces you're competing in and which ones you've set aside? Can they describe what your target customers value in ways concrete enough to make a design decision? If those questions produce vague or conflicting answers, the initiative list will keep growing — because there's no shared anchor to push back against.

That's the difference between a strategy that ranks and a strategy that chooses.

Key takeaways

Ranking strategic initiatives preserves optionality — it delays the decision about what you're not doing. Real prioritisation requires stopping things, not just sequencing them.

When everything feels urgent, it usually means the underlying strategy hasn't defined clearly enough where the company is playing and where it isn't.

Prioritisation becomes less political when the filter is external. Asking "does this initiative serve the customers in the spaces we've chosen?" is a more tractable question than asking teams to argue their case.

The initiative list is a symptom. If it keeps growing, the underlying question — where we are playing and where are we not — hasn't been answered clearly enough.

The test of a working prioritisation process: every senior leader can name the two or three bets the company is fully resourcing — and say what was stopped to make that possible.