Somewhere in the last decade, the phrase "strategic priorities" became a list. A long one.
You know how it gets built, because you've probably been in the room. It starts at five. Then someone from product adds the platform migration. The CFO adds the margin program. The CPO adds the new enterprise tier. The CEO adds international expansion "because we've been saying we'd do it for two years." Someone else slips the wellness initiative onto the list because it felt wrong not to. By Tuesday afternoon there are twelve items on the slide. All of them tagged "strategic." None of them funded with real capacity. Everyone leaves the offsite feeling productive.
Six months later, nothing has moved. And nobody quite knows why.
The Booz finding nobody internalises
Strategy& has been publishing the same uncomfortable finding for years. Companies with one to three strategic priorities show above-average revenue growth. Companies with five or more show below-average growth. The relationship is not subtle. More priorities reliably predict worse outcomes.
This has been true across industries and decades. It's taught in every MBA strategy course that takes itself seriously. And yet, every year, every offsite, the same room produces the same twelve-item list.
Why does the evidence not stick?
Why it keeps happening
Because saying no has a cost that saying yes doesn't.
When the CPO walks in and proposes the new enterprise tier, saying "that's not a priority for this year" means a real conversation with a real person who has put a real proposal on the table. It means standing behind a trade-off in front of peers. It means somebody walks out of the room with less than they walked in with.
Saying "let's add it to the list" costs nothing in the moment. The list absorbs it. The list is infinitely elastic. You can add a thirteenth, a fourteenth, a fifteenth item, and the list will not push back. The list never says "you can't have me, I'm already full."
The cost arrives later — invisibly, distributed across the whole organisation. The engineer split across four initiatives at 25% each, which means none of them at 25%. The COO who spends every week in triage instead of building. The team lead who learned three weeks ago that nothing on her plate matches what leadership keeps saying matters. By the time the CEO walks into the QBR and realises nothing actually moved, the offsite is a year in the past. It feels like an execution failure. It was a planning failure.
The math that makes the lie visible
Here's an exercise that works in any offsite, and is uncomfortable enough that most leadership teams instinctively avoid it.
For each "priority" on the list, write down the two or three senior people whose time it depends on, and the percentage of their working week the priority will need to actually move. Then, for each named person, add up the percentages across all twelve priorities.
What you will find, every single time, is that the CTO is at 240%. The head of product is at 310%. Three different priorities share the same engineering lead at 30% each — and those estimates were optimistic in the first place because the people building them hadn't yet thought about the meetings, the recruiting, the incident response, or the half a quarter the lead is already committed to a different initiative nobody mentioned.
The math reveals what the list has been concealing. You don't have twelve priorities. You have two priorities, eight wishes, and two things that will quietly die over the year without anyone ever formally deciding to kill them.
What an honest list looks like
An honest strategic list has three properties a wish list doesn't.
It names people, not functions. "Engineering" cannot be the owner. Three named individuals can. The moment ownership lives at the function level, accountability dissolves into a committee that was never actually convened.
It has capacity allocated, not implied. If the engineering capacity for this priority isn't reserved on a named team's roadmap, the priority isn't real. It's a hope wearing a number.
And it has explicit trade-offs. Every item added to the list requires a sentence about what gets less — which existing initiative slows, defers, or stops. The system, not the discipline of the room, should make this impossible to skip. Discipline erodes. Structure doesn't.
That fourth priority on your list isn't strategic. It's an option you're keeping open at the cost of the first three. Treat it like one.
The Vindaris view
A strategy system that lets you add initiatives without forcing capacity accounting isn't a strategy system. It's a list manager. What turns strategy from intent into reality is the moment, repeated every quarter, when adding something new requires explicitly naming what it takes capacity away from. That conversation — the one most leadership teams instinctively route around — is exactly where twelve priorities collapse into three. And three is where execution can finally begin.