There is no such thing as BAU work. There is only how you allocate effort.

In most organizations, there are two kinds of work: strategic work and BAU. Strategic work is the transformation programs, 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 a fiction.

What the split actually does

The strategic/BAU distinction allows leadership to set a strategy and plan for its execution without accounting for the work that will actually consume most of the organization's attention.

The strategy deck says: we're investing in market expansion. The operational reality is: the two senior people that market expansion depends on are spending 70% of their week on BAU. The strategy exists in one layer. The effort allocation exists in another. The two are never compared.

This is how organizations have a strategy on paper and a different strategy in practice. The real strategy is always revealed by where effort actually goes — and if you never measure that, you never know.

An organization 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 no one wants to build.

Why BAU gets a separate bucket

The BAU category exists for a specific reason: it protects strategic initiatives from being compared against operational necessity. If everything is on the same ledger — market expansion initiative and support escalation response — the support escalation will always seem more urgent, and it will always win.

The solution most organizations choose: separate the ledgers. "Strategic" work gets tracked, owned, and reviewed. "BAU" work gets run by the operations team without scrutiny.

The problem: the boundary between the two is never maintained. Strategic work bleeds into BAU — the initiative that was supposed to be a focused three-month effort gradually becomes a permanent operating responsibility. BAU work bleeds into strategic capacity — the "quick" 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 went. Nobody looks at both at the same time.

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 that are not available for the market expansion initiative. We're choosing that tradeoff explicitly."

When you put operational work on the strategic ledger, three things happen immediately:

1. 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. The strategy deck can either reflect that honestly or pretend it doesn't exist.

2. Decisions become visible. When the support queue volume spikes — a new enterprise customer with high-touch requirements — the system shows that the spike is consuming capacity from the strategic initiative. The decision to prioritize the support queue isn't invisible anymore. It's a decision.

3. The Do-Not list writes itself. When you see where effort actually goes, the things that shouldn't be receiving strategic-caliber attention become obvious. The legacy system that consumes 20% of the senior engineering team's week. The internal request that routes through the same people as the platform migration. Name them. Decide whether they stay.

The capacity view that matters

The capacity view that makes this work isn't headcount. It's named people with named allocations.

For each of the top three strategic priorities: which specific people does it depend on, and at what percentage of their week? For each operational responsibility that consumes strategic-caliber capacity: same question.

Stack them. The person who appears at 130% across the strategic and operational ledger isn't a capacity problem — she's a prioritization decision the organization hasn't made yet.

The Vindaris position

We don't distinguish between strategic work and BAU work in the system. We distinguish between work that's connected to a strategic priority and work that isn't. Both kinds live in the same system. Both kinds consume 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 — because the numbers are finally honest.

In den meisten Organisationen gibt es zwei Arten von Arbeit: strategische Arbeit und BAU. Die Trennung fühlt sich sauber an. Sie ist eine Fiktion.

Die strategisch/BAU-Unterscheidung erlaubt es der Führung, eine Strategie zu setzen und deren Umsetzung zu planen, ohne die Arbeit zu berücksichtigen, die tatsächlich den größten Teil der Aufmerksamkeit der Organisation verbrauchen wird.

Das Strategiedeck sagt: Wir investieren in Marktexpansion. Die operative Realität: Die zwei Senior-Personen, von denen diese Expansion abhängt, verbringen 70 % ihrer Woche mit BAU. Die echte Strategie zeigt sich immer daran, wo Aufwand tatsächlich hingeht.

Die ehrliche Alternative: Alles auf dasselbe Ledger setzen – und dann die Entscheidungen explizit treffen. Nicht „Das ist BAU, also zählt es nicht gegen unsere strategische Kapazität." Sondern „Dieser Support-Queue bei aktuellem Volumen verbraucht 2,5 Senior-Engineering-Wochen pro Monat. Das sind 2,5 Wochen, die nicht für die Marktexpansion verfügbar sind. Wir wählen diesen Tradeoff explizit."