In most companies, two artifacts are produced every year and never collide. The strategy lives in a leadership deck — bets, objectives, big arrows pointing right. The headcount plan lives in a finance spreadsheet — names, costs, hire dates, attrition assumptions. Neither one references the other. They are produced by different people, on different cadences, for different audiences, and the gap between them is exactly where the year goes to die.
A strategic priority without a named percentage of named people's weeks is not a priority. It is an aspiration with executive sponsorship.
The collision nobody runs
The exercise itself is embarrassingly simple. List the strategic priorities. For each priority, list the people whose time it actually requires and what fraction of their week it credibly consumes. Sum those fractions per person. Compare against 100 percent.
In practice, this exercise nearly always produces totals north of 130 percent. Often north of 200 percent. The same engineering lead is committed across four priorities at "about 30 percent each." The same RevOps manager is the named partner on six different initiatives, each of which assumes she has bandwidth. The arithmetic was never run because no single person felt responsible for running it. The arithmetic was the strategy, and nobody noticed.
When the totals come in over capacity, the team doesn't actually do more work. They quietly choose which priorities happen. They are not bad at choosing — they are excellent at it, in fact, because they have to be. But they will not choose the priorities you would have chosen. They will choose the ones with the loudest stakeholder, the closest deadline, the most personal relationship to the requester. The strategic intent loses to operational gravity every time.
Why finance can't fix it
Finance owns the headcount table. Strategy owns the priorities. Neither owns the reconciliation between them, and so the reconciliation does not happen. This is not laziness or incompetence — it's a structural gap. The CFO can tell you what each function costs. The CSO can tell you what each function is supposed to deliver. Neither can tell you whether the second is credibly supported by the first, because the bridge between them was never anyone's job to build.
You can see the consequences in any planning cycle. The strategy off-site produces twelve priorities. The budget review approves headcount for the year. The two documents sit next to each other on the company drive and never inform one another. By Q2, somebody notices that three of the twelve priorities are dramatically under-resourced, by which point reshuffling people is too expensive and the priorities quietly slip.
The fix is not more headcount. It is putting capacity in the same room as strategy, in the same artifact, at the same time, with the same owner. Until the two collide on a single surface, the strategy will continue to be a wish list with a glossy cover and the headcount plan will continue to be a finance exercise nobody outside finance reads.
The three numbers that make a priority real
For every strategic priority, you should be able to write down three numbers. If you can't, the priority isn't ready to be on the list.
The first is bandwidth. Named people, named percentage of their week, for a named duration. Not "the platform team will support" — three specific engineers, at thirty percent each, from week one to week fourteen. If the names aren't on the priority, the priority isn't real. Naming creates accountability. Vague support creates plausible deniability.
The second is budget. Named euros, with a category and a line of sight to the GL. Not "we'll figure out the cost as we go." A number that the CFO has agreed to, against a specific bet, with a specific expected outcome.
The third is calendar. The first day and the last day this priority occupies that bandwidth. Open-ended priorities are the worst kind — they consume capacity indefinitely, never resolve, and quietly suffocate everything else. A priority without a calendar isn't a commitment; it's a slow leak.
If you cannot fill in all three for any item on your strategy list, the item is not a priority. It is a candidate. Candidates belong in a separate document, where they are explicitly not consuming bandwidth and not counted against capacity. The mixing of candidates with commitments is what produces the 200 percent over-allocation that nobody can fix once the year is underway.
What changes when capacity is in the room
Two specific things change, and both of them are uncomfortable.
The first is that fewer priorities make the cut. Once the math is run, the leadership team is forced to confront the actual size of the executable plan, which is usually about a third of what was originally proposed. Cutting two-thirds of the proposed strategy feels like a loss. It is, in fact, the first time in years the strategy has been honest about its size.
The second is that trade-offs become explicit. When somebody proposes a new initiative mid-quarter, the question stops being "is it a good idea?" — almost everything is a good idea — and becomes "whose week does it consume, and which existing commitment do we relax to make room?" That second question is the one that turns strategy from accumulation into actual selection.
The Vindaris view
An execution layer that doesn't include capacity is a wish-list visualizer with a search bar. The system has to make it impossible to add a new bet without showing whose week it consumes, what it costs, and which existing bet gives way. Anything less leaves the reconciliation to a quarterly heroics exercise that, in practice, never happens.
Strategy that doesn't reconcile against capacity is the politest form of self-deception available to a leadership team. It costs nothing to say at the offsite, looks excellent on a slide, and is paid for, line by line, by the team's evenings and weekends until something visible breaks. Capacity is not the operational consequence of strategy. It is strategy. The deck just hasn't caught up yet.