Walk into almost any leadership offsite and watch what happens when the conversation turns to "this quarter's priorities." Twenty Post-its go on the wall. Everyone votes. The Post-its get clustered. A facilitator helpfully arranges them into a ranked list. Someone takes a photo. The team leaves the room feeling that focus has been achieved.
It hasn't. What's been achieved is a sorted backlog with executive endorsement. That isn't focus. It's the same wish list in a nicer order.
The data nobody quotes anymore
Booz's classic strategy work — the one most MBA programs still teach and most operators still ignore — found this decades ago. Companies with one to three strategic priorities outgrow companies with five or more. The relationship isn't subtle. It isn't a regression artefact. It's been replicated under different methodologies and survived the move from print to deck to whitepaper.
We just keep ignoring it, because cutting is harder than ranking. Why is the number so persistently the same? Because attention is the binding constraint. A leadership team can hold three things in working memory across a quarter. It cannot hold seven, and pretending it can is how seven becomes zero.
Why ranking always wins the room
Ranking is collegial. Everyone's idea makes the list. The argument is about order, not existence. By the time the meeting ends, the strategy includes a little of everyone's bet — which is to say, no strategy at all, because strategy by definition is the bet you took instead of the others.
Cutting is the opposite of collegial. Cutting names a trade-off. It tells someone in the room — usually someone senior, often someone whose budget depends on it — that the thing they care about isn't on the list this quarter. That's why focus rarely survives a leadership offsite without a strong forcing function. The room rewards consensus. Consensus rewards inclusion. Inclusion is the enemy of focus.
The honest leadership team accepts that focus is going to make at least one peer mildly unhappy at the end of the quarter, and treats that unhappiness as a leading indicator that the work is working.
Three forcing functions that actually hold
These are the only three I've seen survive contact with reality. Anything weaker collapses by week four.
A capped count. Three strategic priorities. Not three plus a few honourable mentions. Not three big ones and four "supporting" ones. Three. The cap is the discipline. The moment you allow a fourth, you have license for a fifth, and within two quarters you're back at the wish list.
A symmetric Do-Not list. Equal in length to the Do list, written down, with named owners empowered to refuse. The things you are explicitly choosing not to fund this quarter. If the Do list has five items and the Do-Not list has none, you haven't decided anything — you've added.
Bandwidth tied to each bet. Every priority has named people, a named percentage of their week, and a named budget. If two priorities want the same person at 60% each, one of them is fiction. The capacity model is the truth-teller. Without it, "focus" is a slide; with it, focus is a calendar.
What this looks like in practice
A leadership team that has actually focused can answer three questions in under a minute. Which three things are we doing this quarter? Which named people are doing them, at what percentage of their week? Which things did we explicitly choose not to do, and who's authorised to refuse them if they come back?
If any of those three answers takes more than a minute, the team has prioritized. It hasn't focused. The difference matters because prioritization fails silently — the bottom of the list quietly slides off the edge, and nobody notices until the QBR. Focus fails loudly — somebody complains in week two that their thing got cut, and the leadership team has to defend the decision. The loud failure mode is the healthier one, because it produces conversation; the silent one produces drift.
The Vindaris view
Strategy without an honest accounting of capacity is fiction. The system you run on should make it structurally impossible to add a new initiative without showing what gets removed, what bandwidth it consumes, and what budget it spends — at the moment the initiative is being added, not three weeks later when the conflict surfaces.
Anything less than that is a wish list with project codes. Pretty in the slide, useless on Tuesday morning when two priorities turn out to want the same engineer and somebody has to choose. The choice is the strategy. Everything else is just colour.
The leadership teams that consistently outgrow their peers are not the ones with the most sophisticated planning frameworks. They're the ones who treat focus as an act of deletion, not arrangement — who walk out of the offsite with a shorter list than they walked in with, and who can name the things they removed faster than the things they kept. That asymmetry is the entire game.