Strategic prioritization: how to choose what NOT to do

A priority list with twelve items on it isn't a priority list - it's a wish list. Real prioritization isn't adding more important things to do; it's making the harder decision of what you'll deliberately NOT do this quarter.

Why strategies die at the implementation stage

Most strategies don't fail at the concept level - they fail because a team tries to run too many initiatives at once, so none of them gets enough resources to actually work. Resource dilution is the quiet killer of strategy execution, far more common than a bad strategy itself.

Why it's hard to say "no" to good ideas

The problem rarely lies in telling good ideas apart from bad ones - most initiatives that end up on a priority list have real value. The difficulty is that rejecting a good idea requires a different kind of courage than rejecting a bad one - because it involves openly admitting that something valuable is being consciously left for later, which can be politically and emotionally harder than rejecting something clearly weak.

A practical method for trimming the list

• A hard cap on initiatives per quarter. If a team is running more than three or four main initiatives at once, none of them will get enough attention.
• An explicit "not now" list. Writing down rejected but valuable ideas somewhere visible reduces the resistance to cutting them - it's not "never," just "not now."
• An exclusion criterion, not just an inclusion one. Instead of asking "is this important?" (almost always yes), ask "what will this take away from another, more important initiative?"

The leader's role in enforcing the limits

The initiative cap alone isn't enough if the leader gives in to pressure to add "just one more, really important" thing mid-quarter. Effective prioritization requires discipline - an explicit rule that adding a new initiative mid-quarter means removing another, not stacking it on top of the existing list.

A skill that's harder to develop than generating ideas

The ability to consciously let go of good ideas in favor of better ones is one of the hardest management skills - harder than generating the ideas themselves, which most organizations never run short of. In work with boards, training this skill usually starts by practicing it on that company's actual, current priority list - not an abstract example, but a real decision that needs to be made in the coming weeks.

How to communicate rejected initiatives back to the team that proposed them

How a rejected initiative is communicated has a big effect on whether the people who proposed it stay engaged in submitting future ones. A clear explanation of the rejection criterion (not a lack of value in the idea, but limited resource capacity this quarter) and a concrete indication of when the topic might come back keeps motivation alive for submitting further initiatives - unlike quietly shelving an idea with no explanation.

When it's worth making an exception to the hard limit

A hard cap on initiatives doesn't mean rigid inflexibility - sometimes a genuinely urgent opportunity comes up, one whose rejection would cost more than exceeding the limit. The key is making sure such an exception stays genuinely exceptional, with an explicitly stated reason, rather than becoming a quiet norm that eventually undermines the point of having a limit at all.