The Great Flattening: Engineering Manager Span of Control Data for 2026

Org chart made of wooden blocks and orange threads on a dark table with middle blocks removed

Short answer: Spans of control are widening fast. Gallup data cited by Forbes shows the average manager had 12.1 direct reports in 2025, up from 10.9 in 2024 and 8.2 in 2013. Companies are removing management layers and citing AI as a reason, and engineering organizations are among the most affected.

Key span of control data at a glance

[Table 1]

Why are organizations flattening?

What is the risk for engineering organizations?

The data also shows a cost. DDI's Global Leadership Forecast 2025 puts leadership bench strength at 20%, and 40% of stressed leaders have considered leaving. In engineering, wide spans create 3 specific problems:

  1. Review backlogs. Managers who still approve designs and code reviews become bottlenecks.
  2. Weaker career development. Engineers get less coaching, which hurts retention of the senior people now in highest demand.
  3. A future leadership gap. Fewer manager roles mean fewer people learning to lead, which shrinks the pool of future VPs of Engineering and CTOs.

What span of control works in engineering?

[Table 2]

Wider spans work only when teams are senior and autonomous, platforms are strong and staff or principal engineers carry technical leadership. Our guide to B2B SaaS engineering org design covers how to split those responsibilities.

What should CTOs and VPs of Engineering do?

  1. Separate people leadership from technical leadership. Strong staff and principal engineer tracks let managers carry more reports without blocking decisions.
  2. Automate status work first. Remove reporting overhead before removing managers.
  3. Track the warning signs. Review wait times, regretted attrition and time since last 1:1 show when a span is too wide.
  4. Keep a leadership pipeline. Rotate senior engineers through tech lead and acting manager roles.

Frequently asked questions

What is the average span of control in 2025?

12.1 direct reports per manager, according to Gallup data cited by Forbes.

How many direct reports should an engineering manager have?

Most engineering teams work best with 6 to 10. Spans above 12 work only with senior, autonomous teams and strong technical leadership below the manager.

Is AI eliminating middle management?

It is a stated driver of flattening. Gartner predicted that 20% of organizations would use AI to remove more than half of their middle management positions by 2026.

Discuss org design with other engineering leaders: apply to join CTO Club.

Recent articles

[Table 1] Metric | Figure | Source Average direct reports per manager, 2013 | 8.2 | Gallup via Forbes, 2026 Average direct reports per manager, 2024 | 10.9 | Gallup via Forbes, 2026 Average direct reports per manager, 2025 | 12.1 | Gallup via Forbes, 2026 Change in US manager headcount, May 2022 to May 2025 | Down 6.1% | Live Data Technologies via WSJ Google managers overseeing small teams, year over year | 35% fewer | Google via Forbes, 2026 Employees reporting management layers were cut | 41% | Korn Ferry via Forbes, 2026 Leadership bench strength | 20% | DDI Global Leadership Forecast 2025 Organizations using AI to flatten, per prediction | 20% by 2026, removing over half of middle management | Gartner, October 2024 [Table 2] Span of control | Typical fit in engineering | Main risk 5 to 7 reports | New managers, complex or high-risk systems | Higher management cost 8 to 10 reports | Stable product teams with senior engineers | Less coaching time 11 to 15 reports | Experienced, autonomous teams with strong platforms | Weak career development and review backlog Above 15 reports | Rarely sustainable in engineering | Manager becomes a bottleneck