In most companies, work falls into two buckets. Strategic work is the transformation programmes, the big bets, the initiatives with executive sponsors and slide decks. BAU — business as usual — is everything else: the operational day-to-day, the support queue, the maintenance releases, the "quick" cross-functional requests that somehow always take two weeks. The split feels clean. It's also a fiction, and it's one of the most expensive fictions in modern business.
What the split actually does
The strategic/BAU distinction allows leadership to set a strategy, plan its execution, and never account for the work that will actually consume most of the organisation's attention. The strategy deck says: we are investing in market expansion. The operational reality is: the two senior engineers that market expansion depends on are spending 70% of their week on BAU — incidents, support escalations, the integration project that was supposed to end in March. The strategy exists in one layer. The effort allocation exists in another. The two are never compared because, structurally, they're not in the same conversation.
This is how organisations end up with a strategy on paper and a different strategy in practice. The real strategy is always revealed by where effort actually goes. If you never measure that, you never know which one you're running.
An organisation that claims to be pursuing market expansion but allocates 80% of senior capacity to maintaining existing operations is not pursuing market expansion. The real strategy is in the spreadsheet nobody wants to build.
Why BAU gets its own bucket in the first place
The BAU category exists for a specific, almost rational reason: it protects strategic initiatives from being compared against operational necessity. If everything sits on the same ledger — the market expansion initiative and the urgent support escalation — the support escalation will always feel more urgent, and it will always win. The customer is on fire. The strategic initiative is patient. So leadership creates a separate bucket for the strategic stuff, fences it off from the daily noise, and hopes the fence holds.
The fence never holds. Strategic work bleeds into BAU — the initiative that was meant to be a focused three-month effort gradually becomes a permanent operating responsibility nobody can put down. BAU work bleeds into strategic capacity — the "quick" enterprise request that takes the lead engineer off the transformation for a week. Over time, the strategic ledger shows the plan. The BAU ledger shows where the work actually went. Nobody looks at both at the same time, because looking at both at the same time is uncomfortable.
The honest alternative
The honest alternative is to put everything on the same ledger and then make the choices explicitly. Not "this is BAU, so it doesn't count against our strategic capacity." Instead: "running this support queue at its current volume consumes 2.5 senior engineering-weeks per month. That is 2.5 weeks not available for market expansion. We're choosing this trade-off, by name."
When you put operational work on the same ledger as strategic work, three things happen quickly.
The strategy becomes honest. If market expansion requires 8 senior engineering-weeks per month, and the operational baseline consumes 6, the strategy needs 14. If there are only 10 available, the strategy is wrong, or the operational baseline has to shrink, or new people have to be hired. The strategy deck can either reflect that arithmetic or pretend it doesn't exist. Pretending stops being free once the arithmetic is visible.
Decisions become visible as decisions. When the support queue spikes because a new enterprise customer joined with high-touch requirements, the system shows that the spike is consuming capacity the strategic initiative was relying on. The decision to prioritise the support queue isn't invisible anymore. Somebody made it. Somebody is accountable for it. The trade-off has a name on it.
The do-not list writes itself. When you see where effort actually goes, the things that shouldn't be getting strategic-calibre attention become obvious — the legacy system consuming 20% of senior engineering, the internal stakeholder routing requests through the same two people as the platform migration, the recurring report nobody reads. Name them. Decide whether they stay. Most of them won't.
The capacity view that actually works
The capacity view that makes this real isn't headcount and isn't FTE allocation in a finance spreadsheet. It's named people with named allocations against named work.
For each top strategic priority: which specific people does it depend on, and at what percentage of their week? For each operational responsibility consuming strategic-calibre capacity: same question. Stack them. The person who appears at 130% across the combined ledger is not a capacity problem. She is a prioritisation decision the organisation hasn't made yet, and avoiding the decision is itself a decision — usually the worst one available.
This is uncomfortable on purpose. Headcount-level capacity views let leaders move people around in their heads. Named capacity views force the conversation about which actual human is doing too many actual things and which of those things has to come off her plate.
What changes when you stop pretending BAU is separate
Two things change. The first is internal: the planning conversation shifts from "what new initiatives should we add" to "what existing effort comes off to make room." That's a harder conversation, which is why companies avoid it, which is why their strategies don't move. The second is cultural: people in operational roles stop being treated as a different class of contributor whose effort doesn't count toward "the real work." All effort counts. All effort competes. The leadership job is to choose, in public, what wins.
The Vindaris view
We don't distinguish between strategic work and BAU in the system. We distinguish between work connected to a strategic priority and work that isn't. Both kinds live in the same place. Both kinds draw from the same capacity pool. The COO can see, at any time, what percentage of senior attention is going to each strategic priority versus everything else. That view changes the conversation — not because the numbers are different, but because the numbers are finally honest. BAU isn't a category. It's a story leadership tells itself to avoid the trade-offs the strategy actually requires.