What is span of control?
Span of control is the number of people who report directly to one manager or leader. It's one of the first numbers an org-design review looks at, because it drives so much else: management overhead, decision speed, and how many layers sit between the front line and the top of the organization.
Narrow vs. wide span of control
A narrow span (a manager with only a few direct reports) usually means closer supervision and faster individual feedback, but more management layers, more overhead cost, and slower decisions as they travel up and down the hierarchy. A wide span (many direct reports per manager) is leaner and pushes decisions down, but can leave managers stretched too thin to coach or supervise effectively.
There's no single "correct" number — the right span depends on the work. Roles that are highly standardized or self-directed can usually support a wider span than roles that need close coaching, complex judgment calls, or tight quality control. Commonly cited rules of thumb put a "healthy" span somewhere in the 5–10 range for people-management-heavy roles, but real organizations run successfully well outside that band depending on the work and the manager.
Why it matters for a reorg
Span-of-control analysis is usually one of the first things measured in a restructuring: an org with unusually narrow spans at a given layer often has room to flatten (removing a layer of management without losing supervision quality), while unusually wide spans can signal managers who are overloaded or supervising in name only. Comparing span of control alongside layers (how many levels exist between the CEO and the front line) is the standard way to spot both problems at once.
How BlissPoint Organization Viewer approaches this
Span of control is computed live for every org chart in Organization Viewer: each manager's direct-report count, the company-wide average, and a flag on anyone supervising more than ten people directly. Because it's recomputed as you edit, it carries straight into scenario modeling— clone the org, flatten a layer or widen a team, and compare the span and headcount impact before promoting the change.