At some point in the last decade, "strategic priorities" became a list. A long one.
The list gets built in the offsite. It starts with five items. Then someone from product adds the platform migration. Then the CFO adds the margin improvement program. Then the CPO adds the new enterprise tier. Then the CEO adds the international expansion "because we've been saying we'd do it for two years." Then someone puts the wellness initiative on the list because it felt wrong not to.
Twelve items. All of them "strategic." None of them funded with real capacity.
When everything is a priority, the word has stopped doing any work.
The Booz finding nobody internalizes
Companies with 1–3 strategic priorities show above-average revenue growth. Companies with five or more show below-average. The relationship is not subtle. It's not a close call. More priorities reliably predict worse outcomes.
This has been true for decades. The research has been published, cited, and discussed in every strategy course that matters. And yet, every year, the offsite produces twelve priorities.
Why it keeps happening
Because saying no has a cost that saying yes doesn't.
When the CPO proposes the new enterprise tier, saying "that's not a priority this year" means a real conversation with a real person who cares. Saying "let's add it to the list" costs nothing in the moment. The list absorbs it. The list is infinitely elastic.
The cost arrives later — invisibly, distributed across everyone who tries to execute against twelve things at once. The engineer split across four initiatives. The COO who spends every week in triage. The CEO who gets to the QBR and realizes nothing actually moved.
By then, it's too late to blame the offsite. It feels like execution failure. It was a planning failure.
The math that makes the lie visible
Here's a simple exercise that works in any offsite:
For each "priority," write down: the two to three senior people it depends on, and what percentage of their week it needs to move.
Then add up the percentages for each person across all twelve priorities.
The CTO is at 240%. The head of product is at 310%. Three of the twelve priorities share the same engineering lead at 30% each — which means none of them is getting 30%, because those estimates were optimistic in the first place.
The math reveals what the list conceals: you don't have twelve priorities. You have two priorities, eight wishes, and two things that will quietly die without anyone formally deciding to kill them.
What an honest list looks like
An honest strategic list has three things a wish list doesn't:
- Named people, not functions. Not "engineering." Three names.
- Capacity allocated, not implied. If the capacity isn't there, the priority isn't real.
- Explicit tradeoffs. Every item added requires naming what gets less. The system should make this impossible to skip.
That fourth priority isn't strategic. It's an option. Treat it like one.
The Vindaris position
A strategy system that lets you add initiatives without forcing capacity accounting isn't a strategy system. It's a list manager. The thing that makes strategy real is the moment you have to say: adding this requires taking that capacity from something else. That conversation, made inevitable by the system, is where twelve priorities become three — and where execution actually begins.