The Number Of Subordinates That One Supervisor Can Manage

You've seen it happen. Now, one-on-ones get cancelled. Meetings run late. A manager gets promoted, inherits a team of fifteen people, and within three months they're drowning. The "open door policy" becomes a theoretical concept because the door is literally never open — the manager is in back-to-back Zoom calls from 9 AM to 6 PM.

Meanwhile, another manager down the hall has four direct reports. They have time for weekly coaching sessions, they know each person's career goals, they catch problems before they become crises. But the organization wonders: is that efficient? Could that manager handle more?

The question of how many people one supervisor can effectively manage — span of control, if you want the textbook term — is one of those deceptively simple questions that actually determines whether an organization functions or flounders. Day to day, get it wrong, and you don't just get a tired manager. You get burnout, turnover, missed deadlines, and a culture where nobody feels heard.

What Is Span of Control

At its core, span of control is just the number of direct reports a manager oversees. Plus, no mystery. That's it. But the effective* span — the number a specific manager can handle well* in a specific context — that's where it gets interesting.

Classical management theory loved neat formulas. Think about it: in the early 20th century, a French consultant named V. A. Over 24,000. His math: with 4 subordinates, you have 44 possible relationships (direct, cross, and group). With 8 subordinates, you jump to 1,080. With 12? That said, graicunas published a paper arguing that the number of relationships a manager must maintain grows geometrically, not linearly. His conclusion: the practical limit is around 5 or 6.

Around the same time, British colonel Lyndall Urwick suggested the ideal number was 5 for upper management, maybe 8 to 12 for lower-level supervisors where work is more routine.

These numbers became gospel for decades. You'll still see them cited in MBA textbooks and HR policy documents. "The optimal span of control is 7, plus or minus 2.

Here's the problem: those formulas assumed a world where managers only* manage. They don't do the work. They don't write code, close deals, design campaigns, or debug production issues. They just... In real terms, manage. That world doesn't exist anymore.

The modern reality: working managers

Most managers today are player-coaches. Worth adding: they carry individual contributor responsibilities and people responsibilities. In real terms, a engineering lead writes code and runs 1-on-1s. A sales manager carries a quota and coaches reps. A creative director designs and approves work.

When you're a working manager, your effective span shrinks dramatically. Every hour spent debugging is an hour not spent coaching. Not because you're less capable — because your time is sliced differently. Every client call is a cancelled career conversation.

This isn't a failure of management. Flat organizations, agile teams, "span of control" targets driven by finance rather than human capacity — they all push toward wider spans. Think about it: it's the reality of modern org structures. But the human capacity to build trust, give feedback, and notice when someone is struggling hasn't changed.

Why It Matters

Span of control isn't an administrative detail. It's a design choice that ripples through everything.

The trust deficit

Trust requires time. Not "face time" — actual attention. Practically speaking, when a manager has 12 direct reports, they can't possibly know each person's strengths, stressors, career aspirations, and working style in any meaningful depth. They manage by exception: they only engage when something breaks.

The result? Now, employees feel like cogs. They stop bringing problems early because "my manager is too busy." They stop asking for growth opportunities because there's never a good time. Engagement drops. Quiet quitting starts here — not from laziness, from invisibility.

The bottleneck effect

Wide spans create decision bottlenecks. Here's the thing — work piles up waiting for their attention. If every approval, every escalation, every "quick question" routes through one person with 15 reports, that person becomes the constraint. They make faster, worse decisions because they lack context. Or they delegate the wrong things to the wrong people because they don't know their team well enough to match tasks to strengths.

The development gap

This is the one most organizations miss. Stretch assignments. Timely feedback. The high performers leave because they're not growing. Career conversations that go beyond "where do you see yourself in five years?Also, developing people — really developing them — takes sustained, individualized attention. Even so, " When spans are too wide, development becomes a quarterly checkbox exercise. The struggling performers stay stuck because nobody has capacity to coach them.

The manager burnout cycle

Wide spans don't just hurt the team. They destroy the manager. Now, the player-coach with 10 reports works evenings and weekends to keep up. They stop exercising, stop sleeping well, stop being the calm presence their team needs. Eventually they quit — or they get promoted out of the role, leaving a vacuum and a team that's been undermanaged for months.

How It Works: Factors That Determine the Real Number

There is no universal number. Anyone who gives you one is selling something. In real terms, the right span depends on a cluster of variables that interact in messy ways. Here's what actually matters.

Nature of the work

This is the single biggest factor.

Highly interdependent, complex, creative work — software development, product design, strategy consulting, R&D — demands narrow spans. Maybe 3 to 6. The manager needs to be in the weeds enough to unblock, redirect, and make judgment calls. They need context. They need to review work, not just status updates.

Standardized, routine, independent work — call center reps, assembly line workers, data entry, basic admin — supports wider spans. 15 to 20, sometimes more. The work speaks for itself. Metrics are clear. Coaching needs are lower because the path to competence is well-trodden.

Moderately complex, semi-routine work — most corporate functions: marketing campaigns, sales, HR business partners, finance analysts — sits in the middle. 6 to 10 is typical. The manager adds value through prioritization, cross-team coordination, and removing organizational friction.

Manager experience and skill

A first-time manager with 6 reports is often overwhelmed. On the flip side, management is a craft. Day to day, a seasoned director with 6 reports might be bored. It takes years to develop the pattern recognition, the emotional regulation, the delegation instincts, and the difficult conversation skills that let someone handle more people without quality dropping.

Organizations routinely promote high-performing individual contributors into management with zero training, give them 8 reports, and wonder why it fails. So the span wasn't the problem. The preparation was.

Team experience and autonomy

A team of seniors who've worked together for years? They coach each other. In practice, they self-organize. They need less management. They escalate appropriately. A manager can handle 10, 12, even more — if the team culture supports it.

A team of juniors, or a newly formed team, or a team in a chaotic environment

Team Experience and Autonomy

Senior, stable teams – Years of shared history create implicit coordination. They self‑check, surface risks early, and coach each other. A manager can safely oversee 12‑15 people because the team’s “operating system” is already baked in.
Junior or mixed‑level teams – New hires need more hand‑holding, frequent clarification, and visible progress tracking. Expect a span of 5‑8 managers for the first 12‑18 months, then expand as competence builds.
Chaotic or crisis‑prone environments – Rapid change, shifting priorities, or high‑stakes projects demand tighter supervision. Even experienced managers should keep spans at 4‑6 until the turbulence settles.

Organizational Structure and Resources

Matrixed vs. functional reporting – In a matrix, managers juggle dual accountability (functional expertise + product delivery). This often forces narrower spans because the manager must balance competing demands.
Support functions – Access to dedicated planners, HR business partners, or analytics teams reduces the manager’s load, allowing a wider span.
Budget for coaching time – When a manager’s calendar includes protected coaching blocks, they can sustain larger teams without burnout.

Leadership Style and Cultural Expectations

Directive vs. servant leadership – A highly directive culture may require tighter spans because decisions flow top‑down. Servant‑oriented cultures, by contrast, thrive on empowered teams, permitting broader spans.
Psychological safety – Teams that feel safe to speak up need less micromanagement. Managers can delegate more authority and widen their span.

Technology and Tools

Visibility platforms – Real‑time dashboards, Kanban boards, and automated status feeds reduce the need for constant check‑ins, supporting wider spans.
Collaboration suites – Integrated chat, video, and document sharing keep distributed teams aligned without a manager acting as a conduit.
AI‑assisted analytics – Predictive workload tools can flag overload risks, giving managers early warning to rebalance.

Geographic Distribution and Time Zones

Co‑located teams – Physical proximity enables quick clarification, allowing spans of 12‑15.
Distributed teams – Time‑zone gaps force asynchronous communication, which can stretch a manager’s capacity. Aim for 6‑10 direct reports unless solid asynchronous tools are in place.

Performance Metrics and Accountability

Outcome‑based KPIs – When success is measured by deliverables rather than activity logs, managers can trust teams to self‑manage, widening the span.
Clear escalation paths – Defined escalation matrices prevent managers from being the default “fire‑fighter,” freeing bandwidth for strategic work.

Feedback Loops and Coaching Cadence

Regular 1:1s – Structured weekly or bi‑weekly sessions keep rapport high without becoming a bottleneck.
Peer‑to‑peer coaching circles – Rotating team members lead skill‑share sessions, reducing the manager’s coaching load.
360° feedback – Periodic surveys surface hidden friction points, enabling proactive span adjustments.

Putting It All Together: A Practical Checklist

Map the work – Classify each sub‑team by complexity (highly interdependent, routine, or moderate). Assign provisional span ranges.
Assess team maturity – Evaluate autonomy, tenure, and self‑management capability. Adjust spans upward for mature teams, downward for newcomers.
Review manager readiness – Consider experience, leadership style, and available support resources. Provide coaching or mentorship if the span exceeds the manager’s comfort zone.
use technology – Ensure visibility tools, collaboration platforms, and analytics are fully adopted before expanding a span.
Set clear accountability – Define outcome metrics, escalation protocols, and feedback mechanisms.
Monitor and iterate – Use 1:1

feedback, peer reviews, and performance data to identify bottlenecks or overload. Adjust spans iteratively rather than rigidly.

For more on this topic, read our article on what is the difference between reflection and refraction or check out what is the length of segment sr.

Cultural Considerations

Trust and Autonomy – In cultures that value hierarchical control, managers may resist widening spans. Start with pilot teams to demonstrate benefits.
Psychological Safety – Teams in high-pressure environments need explicit permission to voice concerns. Pair wide spans with “no-blame” retrospectives to sustain openness.
Work-Life Balance – Distributed teams with wide spans risk burnout. Encourage “right to disconnect” policies and model boundaries to maintain sustainability.

When to Narrow the Span

Even with optimal conditions, some scenarios demand smaller spans:

Highly Complex Projects – Cross-functional initiatives with interdependent tasks may require closer oversight.
New or Inexperienced Teams – Early-stage teams often need more scaffolding; reduce spans until maturity is achieved.
Crisis Situations – Short-term emergencies (e.g., product recalls) warrant hands-on management, even if it temporarily shrinks spans.

The Manager’s Role in a Wide-Span Environment

Managers must pivot from “doers” to “orchestrators”:

Strategic Focus – Prioritize long-term goals, innovation, and stakeholder alignment over tactical oversight.
Resource Allocation – Act as a coach for skill gaps and a negotiator for resource constraints.
Culture Custodian – develop psychological safety and ensure alignment with organizational values.

Conclusion

Optimizing team spans is not a one-size-fits-all equation but a dynamic interplay of context, culture, and capability. By aligning spans with team maturity, leveraging technology to reduce friction, and fostering a culture of trust, organizations can strike the right balance between autonomy and oversight. The goal is not merely to “manage more people” but to empower teams to thrive with clarity, accountability, and support. Managers who master this balance open up scalable efficiency, employee engagement, and sustainable growth—a critical advantage in today’s complex, fast-paced workplaces.