Span of control is where good GCC leaders quietly break
The reports keep coming, the layers keep flattening, and the leader who was close to the work loses the distance the role now needs.
Draft. Figures marked like this are illustrative and pending verification against Recruise placement data & Sachith sign-off before publication.
Key takeaways
- As a centre scales, the reports multiply and the layers flatten, and the leader who was close to the work loses the distance the role now needs.
- The break is quiet: no crisis, just a leader spread too thin to lead well and too proud of proximity to let it go.
- Span is fixed by structure, not stamina — the answer is a real layer two, built before the span becomes unmanageable.
The failure is invisible because nothing breaks.
Span-of-control problems don’t announce themselves. There’s no missed deadline, no blow-up, no obvious cause to point at. There’s just a leader who used to be sharp on every part of the centre and is now a little slower on all of it — more meetings, thinner attention, decisions that wait a day longer than they should. The centre still runs. It just stops getting better, and no one can quite say when that started.
This is where a lot of genuinely good GCC leaders quietly break. Not from incompetence, but from a span that grew past what any one person can hold while still doing the job the way they always have.
“Nobody fails at span. They just keep succeeding at a smaller and smaller version of the role, and call it staying close to the work.”
Sachith Rai · MD & Founder, Recruise
Proximity was the strength. Now it’s the trap.
The leaders most exposed to this are often the ones who were best at the earlier stage — the ones whose value was being close to the work, in the detail, reachable by anyone. That instinct built the centre. At scale it becomes the thing holding it back, because a leader who is close to everything is far from the few decisions only they can make. Letting go of proximity feels like letting go of the job. It is actually the job changing.
When we assess a scaling head, comfort with distance is one of the clearest predictors of whether they’ll grow with the centre or top out inside it.
You solve span with structure, ahead of need.
The fix is not resilience training or a better calendar. It is a real second layer — leaders who own outcomes, not just tasks, so the head can widen without deepening on everything. And it has to be built before the span becomes painful, because the moment it’s painful is the moment the head has the least bandwidth to build it. Centres that add the layer early keep improving; centres that wait for the strain tend to promote in a panic and get the layer wrong.
Span is a design decision. Treated as one, it’s solvable. Treated as a test of the leader’s endurance, it slowly costs you the leader.
One pattern worth knowing, every week.
The Signal is our weekly read on the senior GCC talent market — one chart, one pattern, no noise. Written from live placement data.
More from Recruise Insights.
What Bengaluru GCC heads actually do in their first 90 days
We spoke to GCC heads who have been in role under a year. The published playbook and the actual playbook diverge sharply.
The GCC head's hiring authority problem
Many GCC heads in India still don’t have unilateral hiring authority over their leadership team. The cost shows up later, where no one connects it to that decision.
The first 90 days decide whether a centre leads or executes for years
Strong GCC heads spend the opening quarter earning the authority the title implies — mapping who really decides before making a single big call.