A strategic plan that lists three priorities and assigns money to each is half a plan. The other half is the answer to a much harder question, one most leadership teams do not even know they should be writing down: whose week is this, and for how much of it?
That's a bandwidth budget. Almost no organisation writes one. Every organisation that wants its strategy to survive contact with the next month needs one.
Why money budgets are not enough on their own
Money is fungible and slow. Attention is finite and weekly. A €500K initiative can be approved on Monday by a finance committee and quietly stall by Friday because the two senior engineers it depends on are still firefighting last quarter's launch — and there is no mechanism in the company that notices the contradiction. The money was never the binding constraint. The week was.
This is the gap that explains why so many well-funded initiatives go nowhere. The annual planning process treats capital as the thing being allocated, because capital is what finance knows how to model. But the actual scarce resource — at any company past a certain size — is the bandwidth of a small number of senior individual contributors and managers whose involvement determines whether anything strategic moves at all.
Capacity is rarely the constraint. Focus is. Walk into any management room. Count the initiatives. If it's over seven, you don't have a strategy. You have a wish list.
What a bandwidth budget actually looks like
For each strategic priority, write three numbers and refuse to launch the initiative until you can.
The named people. Not "engineering." Not "the platform team." Three names. If you can't name them, the priority is not staffed — it's hoped. Hope is not an allocation mechanism.
The percentage of their week. 60% for the lead, 30% for the supporting engineer, 20% for the PM. Write this down per individual, per priority. Then stack the percentages across every strategic priority. The first thing you'll discover is that your CTO is allocated at 240%. The second thing you'll discover is which "priority" your organisation is actually choosing — because it's the one that got the named people. Everything else is a slide.
The duration in weeks. Strategic work without an end date is a haunting, not an initiative. If the answer is "ongoing," you haven't defined the bet sharply enough to be able to tell when it's done.
What changes the moment you write it down
Three things, immediately:
Adding a new initiative becomes a visible trade-off. You can no longer add a fourth bet without naming whose week comes off bet one, two, or three. The conversation that used to happen in the hallway — quietly, with no record — has to happen in the planning room, with the percentages on screen.
The Do-Not list writes itself. Anything that wants the same people as a current priority either replaces it or waits. There's no more pretending that two competing initiatives can both proceed at full intensity because nobody did the math.
The weekly cadence stops being a status meeting and starts being a re-allocation meeting. The question changes from "how are we doing?" to "is this still where the bandwidth should be?" That's a fundamentally different conversation. It surfaces drift earlier, and it forces the leadership team to actively re-decide the strategy every week instead of letting it erode passively.
The objection that always comes up
"This is too rigid. People wear multiple hats. Work is fluid."
Yes, and the bandwidth budget should be re-baselined regularly — that's the point of the weekly cadence. The argument isn't that the percentages are static. It's that they need to be visible. The version where you don't write them down isn't more fluid. It's just more deniable. The senior engineer is still 240% allocated either way. The only question is whether the leadership team has to look at that number when they decide whether to add the next initiative.
Why this is the layer most plans skip
Bandwidth budgets are uncomfortable to write. The percentages always add up to more than 100% the first time you try, which means the leadership team has to admit out loud which priority they actually intend to drop. That admission is exactly the conversation most planning processes are designed to avoid. So the plan gets the money column filled in, the strategy column filled in, and the bandwidth column left implicit — which is where it dies.
The Vindaris view
Strategy without an honest accounting of capacity is fiction. The operating system should make it impossible to add a new initiative without showing what comes off, what bandwidth it consumes, and which named people the new commitment depends on. When initiatives, capacity and ownership live in the same graph, the bandwidth budget stops being something the leadership team has to remember to maintain — it's the consequence of the model. A money budget tells you what you can afford to start. A bandwidth budget tells you what you can afford to finish.