Free Calculator

Is Your Team the Right Size?

Most knowledge-work managers run sustainable spans of 5-8 reports. Yours might be perfectly fine. Or it might be the reason your week feels broken. Run the math.

1 6 reports 20

Tell us about the work

Your Span Health

95

Right-sized

Your span sits in the recommended range for your context. Sustainable indefinitely if your other workload is bounded.

Your recommended range

1
20

Recommended low

5

Sweet spot

6

Recommended high

8

For your context (moderate complexity, collaborative work, mixed tenure, experienced manager), the sustainable range is 5-8 reports.

How we calculated your range

What This Means for Your Week

Estimates based on standard manager-time research.

Hrs/week per report

1.2 hrs

1-on-1 + prep + follow-up + coaching

Total weekly mgmt load

7.2 hrs

~18% of a 40h week

Sustainable max

12 hrs

before quality degrades

At 6 reports, you are using 7.2 hours per week on direct management. That leaves room for strategic work, managing up, and your own focused output. Healthy.

What to Do Next

Disclaimer: Recommended ranges are based on management research from Gallup, DDI, and McKinsey on knowledge-work team structures. Your specific context (industry, company stage, regulatory environment) may shift the right answer. Use the output as a planning baseline, not a verdict on your current structure.

Why Span of Control Quietly Determines Your Success

Most managers do not think about span of control until something has already broken. The team feels overwhelming. 1-on-1s start getting skipped. Performance reviews feel like fiction because you no longer know what each person is actually doing. By the time the symptoms show up, the math has been wrong for months.

The underlying mechanic is simple. Each direct report consumes a roughly fixed amount of weekly management time: 1 hour for the 1-on-1, 30 minutes of prep and follow-up, and another 30 minutes spread across coaching, performance management, and unblocking. That is 1-1.5 hours per person per week, before any team-level activities or your own work. Above 8 reports, the math runs out of hours, even for experienced managers, and quality degrades whether or not you notice.

The Three Forces That Set Your Right Span

  1. Task complexity. The more decisions per task that require manager judgment, the lower your sustainable span. A team running standardized operations can have 12-15 reports per manager. A team doing original research can support 3-4. The same person can manage either, but not at the same span.
  2. Coordination requirements. Independent work scales easily across many people. Highly interdependent work creates exponential coordination overhead, and the manager becomes the central node. If your team is constantly negotiating dependencies, your sustainable span drops.
  3. Team and manager maturity. Tenured teams need less of you. Senior managers have more capacity. Both factors expand your sustainable span by 1-2 reports each. New managers leading new teams often discover that 4-5 reports is already at the edge of what they can do well, even though "5-8 is normal" suggests otherwise.

When the Number Is Telling You Something Bigger

A span that is significantly above your recommended range is rarely a "manager who works harder" problem. It is a structural design problem that no amount of personal effort fixes. The math says you cannot run high-quality 1-on-1s with 12 people on a 40-hour week. Pushing the work to 50 or 60 hours buys you a few months before something else breaks: your sleep, your judgment, your relationships outside work, or your willingness to stay in the role.

The fix is structural. Three forms it can take:

  1. Introduce a team-lead layer. Promote one or two senior reports into management responsibility for sub-groups. You go from managing 12 ICs to managing 2 leads, who each manage 5-6 ICs. The total team grows or stays the same, but your span drops to a sustainable number. Hardest option politically, cleanest result.
  2. Tier the cadence. Move your most autonomous senior reports to biweekly 1-on-1s with strong written async updates. Keep weekly cadence with the people who need it. Use our 1-on-1 Meeting Load Calculator to see exactly how much time tiering frees up.
  3. Reduce the load each 1-on-1 carries. If your 1-on-1s have to do everything (status, coaching, career, support, decisions), they expand to 60+ minutes and consume your week. If they only have to do trust and signal, with status moving to async and decisions made in dedicated forums, they can be 30 minutes and still effective. Our free 1-on-1 effectiveness quiz helps surface where your 1-on-1s might be doing too much.

When the Number Tells You You're Under-Utilized

A span below your recommended range is also a signal, just a quieter one. It usually means one of three things: your role was scoped without clear thinking about how big the team should be, you have backed out of management work and are spending the freed-up time on individual contributor tasks (which is comfortable but career-limiting), or your team has shrunk through attrition and the structure has not been reset.

The fix here depends on what you actually want. If you want to be a senior IC with a small team, that is a legitimate path and worth being explicit about. If you want to be a manager with leadership scope, an undersized team is keeping you stuck. Either way, the number is asking you to make the choice consciously rather than drift.

The Conversation This Calculator Is Meant to Start

The most useful thing this calculator can do is give you data for a conversation with your boss that probably has not happened. Run the numbers, screenshot the output, and bring this to your next 1-on-1:

"Based on our work complexity and team makeup, the sustainable span for my role is X-Y reports. I currently have Z. Here is how that is showing up in [specific symptom: 1-on-1s slipping, performance reviews late, my burnout, low team engagement]. I want to propose [specific structural fix]. Can we talk through it?"

Most bosses do not bring up span of control because they have never been taught to see it as a fixable thing. You showing the math and proposing a structural change is rare and useful. Our guide on managing up as a new manager covers how to make these structural conversations routine.

Frequently Asked Questions

What is span of control?
Span of control is the number of direct reports a single manager oversees. It comes from organizational design research, with roots in 1930s-era management theory and refined by modern studies from Gallup, DDI, and McKinsey. The right span varies by context, but for most knowledge-work managers it falls between 5 and 8 direct reports. Below that, you are likely under-utilized. Above that, the math of high-quality 1-on-1s and individual coaching starts to break down.
Why is 5-8 reports the typical range?
Three constraints converge at this range. First, manager attention: 1-on-1s, prep, follow-up, performance management, and individual coaching consume roughly 1-1.5 hours per direct report per week, and most managers have 8-12 hours of weekly capacity for that work. Second, team coordination: above 8, the cross-talk and dependency management starts requiring sub-structure. Third, decision quality: span above 8 typically forces managers into broadcast mode (one-to-many communication) instead of dialogue, which degrades trust and signal.
When is a wider span (10+) actually OK?
Wider spans work in three contexts. (1) Highly independent IC work with clear deliverables and minimal coordination. (2) Mature, senior teams that essentially self-manage and need a manager mostly for political cover and resource allocation. (3) Operations or production environments with standardized work where the manager role is more orchestration than coaching. Outside these contexts, spans above 10 usually mean the manager is doing thin coverage rather than real management.
Why does the calculator adjust for task complexity?
Because complexity directly determines how much manager judgment per task is needed. A team doing repetitive, well-defined work needs the manager mostly for prioritization and unblocking, which scales easily across many people. A team doing strategic, ambiguous, or specialized work needs deep manager engagement on most decisions, which scales poorly. The same person can sustainably manage 12 customer service reps and only 4 senior research engineers.
My span is way above the recommendation. What should I do?
Three options in order. (1) Restructure. If your team is 10+ and you cannot sustain quality, propose a team-lead layer where one of your senior reports takes management responsibility for a sub-group. This is the cleanest fix but takes political capital. (2) Tier your reports. Move autonomous senior reports to biweekly 1-on-1s with strong async updates, and keep weekly cadence with the people who need it. (3) Accept the trade-off. Some companies run wide spans intentionally and accept that 1-on-1 quality will degrade. If that is your reality, invest harder in clarity (written goals, decision rights) and reduce the load 1-on-1s carry.
My span is below 5. Am I under-utilized?
Possibly. Spans below 5 are often a signal that your role is structured wrong, your reports were promoted but the team did not grow, or your time is being consumed by IC work that should be delegated. This is especially common for new managers who keep hands on the work because they are not fully trusting the team yet. Run our Manager's Time Budget Calculator to see if IC work is eating time that should go to managing more people.

Right Span. Right Cadence. Right Tools.

Span is the structural answer. These complement it operationally.

1-on-1 Meeting Load Calculator → Manager's Time Budget Calculator →

← All Calculators