The Span Your Org Chart Doesn't Show
There’s a number that follows every manager around. It shows up in HR dashboards, workforce planning models, and every consultant’s slide deck. It’s your span of control — the number of people who report to you on the org chart.
And it is almost always wrong.
Not wrong in the sense that the data is incorrect. The reporting lines are accurate. But the number on the org chart tells you almost nothing about how much management load a leader is actually carrying. I’ve worked with managers who had four direct reports and were drowning, and managers who had twelve and were fine. The difference had nothing to do with the number on the chart. It had everything to do with what was behind it.
The consulting orthodoxy
If you’ve spent any time around organizational design consultants, you’ve heard the playbook. Spans should be seven to ten. Fewer layers is always better. Manager headcount is overhead to be minimized. The word “delayering” gets used a lot, usually in the same sentence as “unlocking efficiency.”
The logic is seductive. Each management layer adds cost. More managers means more meetings, more alignment conversations, more overhead. If you can widen spans and remove layers, you save money and speed up decision-making. The math is clean. The slide deck is convincing. The board likes it.
And it’s not wrong, exactly. It’s just dangerously incomplete.
What the delayering narrative ignores is what management actually does. A manager with eight experienced, tenured direct reports who are colocated and working on familiar problems is not doing the same job as a manager with eight direct reports who are new, distributed across time zones, and backstopping an offshore team that doesn’t show up on their org chart at all. Calling both of those “span of eight” is like saying a sprint and a marathon are the same distance because they’re both races.
The load nobody counts
Here’s what actually determines how much management capacity a leader needs:
Tenure. A team of people who have been in their roles for two or more years operates differently than a team where half the group started in the last six months. Experienced teams have established norms, know the product, understand the customer, and can resolve ambiguity on their own. New teams need everything explained — processes, context, expectations, the unwritten rules that never make it into documentation. The management time required per person is dramatically different, but the org chart counts them the same.
Turnover. Teams develop through stages. They form, they work through conflict, they establish norms, and eventually they reach a level of performance where they’re largely self-directed. That progression requires stability. Every significant departure resets it. When a team is churning at 25 or 30 percent annually, they never reach the self-directed stage. They cycle between formation and conflict indefinitely, and the manager absorbs the full weight of that every single day. I’ve seen teams with moderate spans that were exhausting to manage because the manager was perpetually onboarding replacements while trying to hold the existing team together.
The dotted lines. This is the one that rarely shows up in any analysis, and it’s often the heaviest part of the load.
The offshore backstop
Let me describe a scenario I’ve seen play out dozens of times across multiple organizations. A company stands up an offshore team — support, operations, engineering, it doesn’t matter. The team is hired, trained, and placed under a local leader. On the org chart, the onshore manager has no reporting relationship to the offshore team. They have their own direct reports. The offshore team is someone else’s responsibility.
Except it isn’t.
Especially early in the global support model, offshore teams simply don’t have the product knowledge, the institutional context, or the judgment that comes from years of working with the customer base. They follow the process. They handle the routine cases. But when something is ambiguous, when a customer escalates, when a case doesn’t fit the playbook, it comes back onshore. The onshore team — and usually the onshore manager specifically — ends up handling the escalations, reviewing the quality, re-explaining the context, and training and re-training as offshore turnover cycles through.
None of that shows up in ticket volumes. The onshore manager isn’t logging “two hours spent re-explaining our escalation criteria to the offshore team for the third time this quarter.” They’re just doing it, on top of everything else, because the work needs to get done and they’re the person with the knowledge.
This is the span your org chart doesn’t show. The manager’s formal span might be eight. Their effective load — weighted for the offshore team they’re backstopping, the timezone gaps they’re bridging, the quality gaps they’re filling — might be closer to sixteen or twenty. But nobody measures that. Nobody accounts for it. And when the manager starts showing signs of strain, the response is usually “they need to delegate better” or “they need to be more strategic” — as if the problem is their capability and not their capacity.
The turnover multiplier
Offshore teams tend to see significantly more churn than onshore teams. This isn’t a cultural judgment — it’s a labor market reality. In many offshore markets, skilled workers have abundant options, competitive salaries are rising, and loyalty to a specific employer is lower because the employment market rewards mobility. Annual turnover rates of 25 to 40 percent are common in offshore operations. I’ve seen teams where half the roster turned over in a twelve-month period.
Every departure takes knowledge with it. Not process knowledge — that’s in the documentation. The knowledge that leaves is the situational kind: which customers have complex environments, which escalation paths actually work, what the product does in edge cases that aren’t in the training materials, why the team does things a certain way. Research consistently finds that a significant portion of role-specific expertise exists only in the head of the person doing the work. When they leave, it walks out the door.
And every replacement resets the learning curve. New hires need training. They make mistakes that experienced team members wouldn’t. They require more oversight, more review, more coaching. While they’re ramping up, the experienced members of the team carry more weight — and when the experienced members are themselves relatively new because of prior turnover, the entire team is operating in a perpetual state of formation.
The manager absorbs all of this. Every new hire is a management investment. Every departure is a management cost. And when turnover is high enough, the manager is spending more time building and rebuilding the team than actually managing it.
What this costs
The cost isn’t abstract. It shows up in specific, measurable ways.
Coaching disappears. When a manager is stretched beyond their capacity, the first thing to go is proactive development. One-on-ones get shortened, rescheduled, or cancelled. Feedback becomes reactive — addressing problems after they’ve become visible instead of course-correcting early. Career conversations stop happening. The manager isn’t negligent. They simply don’t have the hours.
Your best people notice. High performers are the most sensitive to management quality because they have the most options. When they stop getting feedback, when their career development stalls, when they feel like their manager doesn’t have time for them, they start looking. And because they’re the ones with options, they’re the first to leave. This creates a perverse cycle: the overloaded manager loses their best people, which increases the workload on the remaining team, which makes the manager more overloaded, which causes the next-best people to leave.
Quality erodes quietly. When managers can’t do quality reviews, spot-check escalations, or maintain standards through regular oversight, quality drifts. Not catastrophically — that would be visible and actionable. It drifts incrementally, in ways that take months to show up in metrics and years to reverse.
The manager burns out. This is the most common outcome and the least discussed. Organizational burnout research identifies chronic work overload as a primary driver. A manager carrying an effective load of sixteen while the organization thinks they’re managing eight doesn’t have a workload problem that’s visible to anyone with the authority to fix it. They just have a growing sense that they’re failing at their job, because they are — not due to lack of skill, but due to a load that was never designed to be manageable.
What the consulting model gets wrong
The standard consulting recommendation when span analysis comes up is to widen spans, remove layers, and push accountability down. Cut, cut, cut. And in some cases, that’s exactly right. There are organizations with too many management layers, too many coordinators, too many people who exist primarily to attend meetings and relay information. Those structures should be simplified.
But the prescription “widen the span” assumes that every management layer is pure overhead. It doesn’t account for the situations where managers are doing work that can’t be pushed down because the people below them don’t yet have the capability to absorb it — and won’t, as long as turnover keeps cycling the team.
It also doesn’t account for the dotted-line work. The consultant who recommends widening an onshore manager’s span from eight to twelve hasn’t factored in the fifteen-person offshore team that manager is already backstopping. The resulting effective load isn’t twelve. It’s something closer to twenty-five. And at twenty-five, you don’t have a manager. You have a routing node — someone who triages requests, forwards emails, and puts out fires, but who has no capacity left for the work that actually makes management valuable.
What to do instead
The answer isn’t to ignore span of control. Structure matters. But span needs to be measured by effective load, not org chart lines. And when the effective load is too high, the solution isn’t always “the manager needs fewer reports.” Sometimes it’s:
Invest in the offshore local leader. This is usually the single highest-leverage move available. A strong local lead in the offshore geography can absorb 60 to 70 percent of the day-to-day management load that’s currently flowing back onshore. If your local lead is still developing — learning the product, building authority, gaining the team’s trust — then accelerating their development is the fastest way to reduce your onshore manager’s effective load. Every capability the local lead gains is management capacity you get back.
Stabilize before you scale. If your offshore team is churning at 30 percent annually, adding more headcount doesn’t increase capacity. It increases the onboarding and training burden on the people who are already overloaded. Fix the retention problem first. Understand why people are leaving. Address it. Then scale.
Build structured knowledge transfer. The reason escalations flow back onshore is usually that the offshore team doesn’t have the context to resolve them. You can fix this, but not with a wiki that nobody reads. Build decision trees for the top twenty escalation patterns. Create recorded walkthroughs of complex scenarios. Pair offshore team members with onshore experts for live case handling. Every escalation the offshore team can resolve independently is time the onshore manager gets back.
Make the invisible load visible. This might be the most important step. Share the effective load numbers with leadership. Show them the gap between the org chart span and the real number. Show them how many hours per week are available per person after IC work and offshore backstopping. If leadership doesn’t know the load exists, they can’t help carry it.
The organizations that get this right don’t just measure span of control. They measure management capacity — and they make investment decisions accordingly. The ones that don’t will keep widening spans, losing managers to burnout, and wondering why their offshore programs never deliver the results the business case promised.
The org chart is a map. It’s a useful map. But it’s not the territory. The territory is the actual work of management — the coaching, the escalations, the quality oversight, the cultural translation, the constant rebuilding of teams that keep turning over. That’s the span that matters. And until you measure it honestly, you can’t manage it.
Calculate your real management load with our Span of Control Calculator.
— Bruno