The capacity problem nobody puts in the business case
Headcount is not your workforce capacity, what's left after BAU is.
Most execution plans assume people are available, focused, and uninterrupted.
Then everyone wonders why delivery slows, priorities slip, and their best people look like they're underperforming.
Most leaders already know BAU competes with execution.
The problem isn't awareness. It's that while it's known, governance does little about it.
And the reason governance doesn't act on it is simpler than it sounds.
Most organisations don't hold an integrated view of the resourcing required to deliver their strategic roadmap.
Rather, resourcing happens project by project, in isolation.
Every project looks resourced in its own plan, while the same handful of people are stretched across multiple initiatives and BAU at the same time.
That's why one project leader can't see the cumulative load on an individual. And why the individual usually won't raise it until they're already at breaking point.
What I found in my own research adds another layer. Over half of the executives I interviewed said their strategy depended on people working across the organisation, yet workforce planning for strategy execution is rarely treated as a portfolio-level discipline.
Nobody holds the cumulative view because holding it isn't anyone's job. Every project can be resourced correctly in its own plan and the same twelve people are still committed three times over. Building the function that governs throughput rather than demand is part of what Execution sets up.
A simple way to see what's actually happening in your system:
- Demand: the incoming work, projects, initiatives, and the endless quick asks.
- Capacity: the people and time you think you have.
- Throughput: what you can actually deliver once BAU, meetings, dependencies, and switching costs have taken their cut.
This is where governance most often fails.
Leaders govern demand, they approve new work. But they don't govern throughput, they don't protect flow.
The result isn't progress. It's bottlenecks.
When everything is a priority, people don't move faster. They start more things. And starting more things is exactly how the system slows down.
The fix isn't a heroic push. It's system design, starting with visibility of cumulative load and the willingness to make real trade-offs.
Execution doesn't break because people don't care. It breaks because we keep feeding demand into a system that can't absorb it.
The governance moves that actually protect throughput are in the carousel below.
This is part of lever 5 (Execution Feasibility) of the Strategy Execution by Design Model. See the full framework →
Not sure which of the seven levers is holding your execution back? Take the Strategy Execution Maturity Model Assessment →
Written by Rebecca Reti, strategy and execution consultant working with boards and executive teams across Australia and New Zealand.
The governance moves that actually protect throughput are in the carousel. See the carousel on LinkedIn →