Span of Control

Span of control is the number of direct reports a single manager has, with the typical healthy range being 5-8 for most management roles. Extreme spans signal organizational issues: very narrow spans (1-3 reports) often indicate empire-building or under-leveraging managers, while very wide spans (12+ reports) indicate manager burnout, under-coaching, or premature flattening. It's a structural metric that reveals how well a company is using its management capacity.

The benchmark ranges:

Span of control	What it typically signals
1-3 reports	Under-leveraged manager; possible empire building; manager doesn't need to be a manager
4-5 reports	Slightly under-leveraged but workable, especially for senior leaders
5-8 reports	Healthy sweet spot for most management roles
9-12 reports	Stretched; works for highly autonomous teams or simple structures
12+ reports	Manager overload; under-coaching; usually a sign org structure needs another layer

Why 5-8 is the sweet spot:

Weekly 1:1 capacity: a manager doing 30-45 minute weekly 1:1s with 6 reports = 3-4.5 hours/week on 1:1s alone. More than 8 reports makes weekly 1:1s impractical.

Coaching depth: managers can know 5-8 reports' work deeply; beyond that, knowledge becomes superficial.

Decision velocity: 5-8 reports can be brought together for decisions efficiently; larger groups become committees.

Performance management: tracking, reviewing, and developing 5-8 people fits in a manager's headspace; more than 8 starts to skim.

When wider spans work:

Highly autonomous teams: senior engineers or product managers who don't need much oversight can be in larger groups (10-15 reports to one director).

Tech-touch CS or sales: SDR managers can effectively manage 10-12 SDRs because the role is heavily process-driven.

Subject-matter expert managers: when reports do similar work and the manager mostly provides expertise, larger spans work.

Player-coaches: working managers who also have IC responsibilities sometimes need smaller direct-report counts.

When narrow spans work:

Senior executives: CEO, COO often have 4-7 reports (function heads). Narrower spans are appropriate for organizational complexity.

New manager: 2-3 reports is appropriate for first-time managers learning the role.

Specialized work: when each report requires very different expertise.

What span of control reveals about org design:

Too many layers: if you have managers with 2-3 reports, you probably have one layer too many. Flatten.

Single point of failure: managers with 15+ reports become bottlenecks. Add a layer.

Empire building: tracking span growth over time reveals managers who hire to build empires vs. genuine need.

Founder-as-bottleneck: founders managing 12-15 directs at scale signals organizational debt; restructure.

The math at scale:

Org with 100 employees and span of 6: roughly 100 ÷ 6 = ~17 first-level managers. Those 17 managers need 17 ÷ 6 = ~3 second-level managers. Plus founder. About 3 layers total.

Org with 100 employees and span of 3: 100 ÷ 3 = ~33 first-level managers, then 33 ÷ 3 = 11 second-level, then 11 ÷ 3 = 4 third-level, then founder. 4-5 layers, too many for a 100-person company.

Wider spans = fewer layers = faster decisions.

What founders get wrong: Letting spans drift without intentional design. Some managers end up with 2 reports (under-leveraged), others with 15 (overloaded). The right discipline: target 5-8 as design principle; review at every org review; restructure to maintain healthy spans.

Related: Org Chart · Hiring Plan · Founder Roles · Career Ladder · One-on-One Meetings

FAQ

What is span of control?
The number of direct reports a single manager has. 5-8 is the typical healthy range; extreme spans (1-3 or 12+) signal organizational issues.

What's the ideal span of control?
5-8 direct reports for most management roles. This allows weekly 1:1s, deep coaching, decision velocity, and effective performance management. Goes wider for autonomous teams; narrower for senior executives or new managers.

What's wrong with narrow spans (1-3 reports)?
Often signals under-leveraged manager (could be doing more), empire building (manager hiring to build status), or that the role doesn't actually need to be a management role. Consider flattening or removing the layer.

What's wrong with wide spans (12+ reports)?
Manager overload, can't do weekly 1:1s, surface-level coaching, performance management slips. Usually means another management layer is needed. Add a layer or restructure.