Trade-offs between supervision and hierarchy depth
Organizations face a fundamental tension when designing their structure. A manager handling 20 direct reports can oversee more people, meaning fewer layers between frontline and executive leadership. However, this width creates real constraints: each person receives less individual attention, feedback becomes less frequent, and managers spend more time in status meetings than in coaching. The opposite strategy, narrow spans where each manager supervises only 3-4 people, requires more layers of hierarchy, slower decision velocity, and additional salary overhead, but produces tighter coaching and faster issue escalation.
The 'optimal' span depends on task complexity and team experience. Technical teams with self-directed, senior engineers tolerate wider spans. Early-stage, high-chaos teams with junior staff need tighter supervision and narrower spans.
How organization structure cascades from this choice
A span-of-control decision early in a company's growth phase has structural consequences that persist for years. A startup that installs narrow spans (5 people per manager) at 50 employees will have 2 layers; at 500 people, it needs 4-5 layers just to maintain that narrow span. The same growth with a 15-person span can run on 2-3 layers, keeping decision loops shorter and communication clearer. Every additional layer adds latency, context loss, and the risk that information degrades as it passes up and down.