Podcast Summary: No Bullsh!t Leadership with Martin G Moore

Episode Title: How Many Direct Reports Is Too Many?
Episode Date: March 31, 2026
Host: Martin G Moore
Episode Number: 396

Episode Overview

In this thought-provoking episode, Martin G Moore tackles a growing trend in modern organisational design: increasing the number of direct reports in the quest for flatter, more "agile" structures. Martin challenges the seductive myth that fewer management layers automatically lead to innovation and efficiency, demonstrating the real, often hidden costs of extreme delayering. He explores why teams and structures matter, debunks the self-managing team ideal, and offers four practical factors for leaders to assess and build effective span of control in their own organizations.

Key Discussion Points and Insights

1. The Flawed Fantasy of Flatter Structures

[00:41-03:12]

• The belief that self-managing teams with minimal oversight are the future is, as Martin bluntly puts it, “bullshit.”
• Flatter structures are often driven by the desire to cut costs, not by what actually generates results.
• Martin recounts a colleague’s failed “brilliant minds” experiment in tech—putting dozens of highly qualified PhDs together with little structure led to chaos and zero commercial value.

Notable Quote:
“He told me it was like herding cats. Everyone went off in a thousand different directions... yet no commercial value whatsoever was harvested from that unit.” — Martin Moore [02:23]

2. Why Organizations Need Leaders and Structure

[03:13-12:41]

• The division of labor (traced back to Plato and Adam Smith) is essential for functioning organizations.
• Martin clearly lays out five reasons why leaders are necessary for team performance:
  1. Direction: People need guidance and coordination.
  2. Visibility: Measuring results and giving feedback.
  3. Talent Allocation: Matching the right people to the right work.
  4. Execution of Management Will: Ensuring strategy turns into action.
  5. Communication: Messages need to flow effectively top to bottom.

Notable Quote:
“One might even go so far as to say that the self managing, self regulating team is an A grade bullshit story. It was cooked up by executives who were trying to reduce management costs so that they could improve their bonus potential. It was supported by employees who were much happier in the absence of any oversight. And it was perpetuated by leaders who couldn’t articulate why they were critical to the functioning of the business.” — Martin Moore [08:57]

3. The Myth and Math of Span of Control

[12:42-21:08]

• Traditionally, a span of control of 6–12 direct reports is optimal; sometimes fewer when deep expertise is needed (e.g., General Counsel), or slightly more in specialized cases.
• Martin recounts his own CEO experience: he managed just 5 direct reports running a multi-billion-dollar company.
• Tech companies, often outliers, claim larger spans reflect their collaborative cultures, but Martin is skeptical—these sectors also have high rates of failed projects.
• The Meta example: an AI team reportedly operating at a 50:1 engineer-to-boss ratio—“flirting with disaster”.

Quote:
“Historically, even the tech sector has considered a span of 25 to be the outside limit, but apparently Meta has gone to an AI team with a 50:1 ratio.” — Martin Moore [17:29]

• Recent Gallup survey: average US team size rose slightly to 12; two-thirds of managers still have fewer than 10 direct reports.
• Direct (visible) cost savings from delayering are quickly offset by indirect costs: breakdowns in communication, burnt-out line managers, overlooked talent, missed project issues, and deteriorating decision quality.

Quote:
“Companies prove to be highly resilient to the shit decisions that their boards and management teams make. But anyone who thinks that removing layers of leaders doesn’t have an impact is living on borrowed time.” — Martin Moore [20:55]

4. Four Key Factors to Assess Span of Control

[21:09-31:03] Martin shares a clear, practical framework leaders can use:

1. Physical Constraints

• If your direct reports are spread across locations, you may need intermediaries (“span breakers”) so one leader isn’t stretched too thin.
• Example: An operational manager with many stores uses area managers to oversee small clusters.

2. Experience of Direct Reports

• Highly competent senior leaders may need less oversight; less-experienced staff need more direction and support.

3. Uniqueness of Roles

• Each layer in the org chart should have a distinctive purpose, set of deliverables, and time horizon. If not, the structure is likely misaligned.

4. Dominant Culture

• The company’s culture dictates what structures are feasible—do leaders “work on the tools”? Is decision-making centralized or delegated? Is accountability strong?

• In some environments (e.g., Meta), proposing hierarchical changes might even “be a career limiting move.”

• Leaders must move beyond vague feelings—be able to articulate the tangible value a given structure brings to the business.

Quote:
“You’ve got to be able to clearly articulate the value that might come from any structural change. To make any structure work, you need strong leadership and a constructive high performance culture.” — Martin Moore [29:50]

Memorable Moments & Takeaways

• The blunt takedown of “self-managing teams” as “an A grade bullshit story” was a highlight, underscoring Martin’s no-nonsense perspective.
• The real, often hidden costs of delayering—burnout, poor communication, talent neglect—are easy to underestimate but catastrophic over time.
• The four-factor framework for span of control offers a practical, actionable tool for leaders to evaluate their own teams.

Key Segment Timestamps

• [00:00] Introduction and episode theme
• [01:17] The myth of flatter structures & failed experiment story
• [03:13] Why organizations need structure and leaders (division of labour)
• [07:31] The five essential reasons for leadership in teams
• [12:42] Span of control: historical standards and tech industry exceptions
• [16:25] Martin’s CEO experience: spans of direct reports
• [19:40] Direct vs. hidden costs of delayering
• [21:09] Four factors to assess optimal structure and span of control
• [29:50] Articulating the value of structural decisions

Conclusion

Martin G Moore makes a compelling, evidence-rich case against the simplistic pursuit of flat organizational charts. His message: the right structure isn’t about minimizing management, but optimizing leadership for performance, clarity, and value. Listen for the frameworks—stay for the truth bombs.

“Listening is easy, leading is hard... To make any structure work, you need strong leadership and a constructive high performance culture.” — Martin Moore [29:50]