Frame 1 · Three factors
Capacity is a product of three
Resources: enough people. Capability: the right skills. Bandwidth: free attention. If one of the three is zero, capacity is zero. Organisations look at the first two and forget the third.
Before you start a change, you ask the question: is there room? Enough people and the right skills are not enough. The missing piece is bandwidth: free attention. Without that room, capacity is zero.
In the first phase of a change you look at the ground through several lenses. The capacity ceiling is one of them. The reflex afterwards is: we had too few people. But capacity is not one thing. It is the product of three factors: resources (enough people), capability (the right skills), and bandwidth (free attention). If one of the three is zero, capacity is zero. A team of twenty people with the right skills that is fully booked can absorb nothing new.
Of the three factors, bandwidth is the most invisible and the most decisive. The people are there, they are able, but they have no room in their heads. Cognitive load is finite. Every new system, every new procedure, every additional meeting eats into the same supply of attention. On paper the team is ready. In practice the vessel is full.
Judging this before you start is the work of phase 1. A team that has everything on paper, enough people, enough knowledge, but no room in their heads, will not come along with a change. You want to know that before roll-out, not after.
And bandwidth is not only about time. It is also about the right conditions to learn. Most organisations pour all their energy into formal training: courses, e-learning, manuals. But the vast majority of what people learn, they learn by doing it, from colleagues, through coaching. If there is no time to practise the new way of working, no coach nearby, and no colleague to watch, then no course will help. The conditions for learning are part of the bandwidth you judge up front.
The ceiling is not at organisation level. It sits with specific groups that are loaded from several directions at once. Before you start, you map out: which team is hit by which initiatives at the same time? A finance team that has to absorb a new system, an audit and a reorganisation simultaneously hits saturation. You only see that if you look group by group up front, not by org chart.
If you see up front that the pressure is going to break through the ceiling, you have three options for adjusting the plan. Spread over time: plan a roll-out later so the group gets time. Add capacity: temporary support so the daily work does not stop while the team learns. Or reduce scope: less at once, so attention is not scattered. All three are legitimate. None of them is a sign of weakness.
We judge the capacity before the change starts. We look at the free attention per group, the overlap with other initiatives already running, and the signs of fatigue that are already visible. That gives a realistic picture of what a team can absorb, and it grounds the conversation with the steering group about pace and order. Read more about how we work →
Changes rarely run aground on a bad strategy. They run aground because people had no room left and nobody tested that up front. Judge it before the start and you plan realistically. Skip it and you find out when it is too late. The question is not "can they do it?" but "do they have the room to learn it?"
In a conversation we help you judge what your team can absorb, so your change is planned realistically.