Your best manager did not get worse. You gave her a job no human can do well. Here is how to spot it and fix it in an hour.

Your best manager just missed three one-on-ones in a row. Not because she stopped caring. Because she has 14 people reporting to her, and the math broke.

That is a span of control problem, and most scaling teams create it by accident.

The trap goes like this. You promote a strong lead. People like her, so you keep adding reports to her plate. Then one day her team is the one with the quiet quitters, the skipped check-ins, and the feedback that never comes. You assume she got worse. She did not. You handed her a load no human manages well.

‍

The Problem: Nobody Decides the Number, So It Just Grows

Span of control is the number of people who report directly to one manager. Simple idea, brutal consequences when you ignore it.

In most startups the number is never chosen. It accumulates. You hire fast, you flatten the org to "stay nimble," and you quietly hand your managers more reports than they can coach.

The trend is real and it is measurable. Lattice benchmarking data shows the average number of direct reports per manager rose from 4.3 in 2020 to 5.2 in 2022. Gallup, measuring a broader US working population, puts the 2025 average at 12.1 reports per manager, up nearly 50% since it first measured in 2013.

But here is the honest version of that Gallup number, because the average hides the real story. The median team is still only five to six people. What is dragging the average up to 12 is a minority of very large teams: about 13% of managers now oversee 25 or more people. Most managers still run small teams. A growing few are drowning. The question is not "what is the average," it is "which of my managers is quietly in that drowning minority, and have I even looked."

Why does an overloaded span hurt so much? Because management is not a status. It is a set of behaviours that take time: a real one-on-one, honest feedback, a career conversation. When you stretch the span too wide, those are the first things to vanish. The manager survives by going transactional, and the team feels it.

Gallup found that managers drive 70% of the variance in team engagement. So when you overload a manager, you are not denting one person's calendar. You are taxing the engagement of everyone underneath them.

‍

The Insight: No Magic Number, but a Right Range

People want one answer. Seven. And the instinct is not crazy, the search for an ideal span has run since the 1920s. But the honest version has more texture.

Gallup's own analysis found that manager engagement peaks at around 8 to 9 direct reports and falls off as the span widens past that. Interestingly, it is also low at the very narrow end: managers with only 1 or 2 reports tend to be less engaged too, probably because the role loses the team-building challenge that makes management worth doing. Too few and managers over-manage and hover. Too many and they go absent by necessity. The sweet spot is wider than founders fear and narrower than overloaded orgs pretend.

But the real driver is not a number. It is the nature of the work. And here the best framework comes from McKinsey, which studied thousands of managerial jobs and reached the same conclusion this blog is built on: chasing one universal number actually reduces effectiveness. Instead, they sorted managers into five archetypes by how complex and standardized the work is.

The pattern is clear. The more a manager is doing real, non-standardized work alongside leading people, the fewer reports they can carry. The more standardized and repeatable the work, the wider the span can safely go.

This is also where one of our own frameworks lands squarely on the research. We call it the Player-Coach Trap: the manager who is still a top individual contributor and a people leader at the same time. McKinsey's narrowest archetype, the player/coach at 3 to 5 reports, is the same person. If your VP is still shipping code or closing deals and also has 12 reports, the number is not aggressive. It is impossible. The work and the span are fighting each other.

‍

Why Wider Is Not "Leaner"

Founders love a flat org. It feels scrappy. It feels like David, not Goliath. But a flat org with no real management layer is not lean. It is a coaching desert.

When one person owns 15 reports, they cannot coach. They can only react. The team drifts into artificial harmony, because nobody has the airtime to surface real conflict. You lose the exact thing that lets small teams beat big ones: tight feedback and fast trust.

And feedback is the specific casualty worth naming. Across more than 44,000 employees, Gallup found that people who got meaningful feedback in the prior week stayed highly engaged regardless of team size, and when feedback dried up, engagement fell sharply. That is the mechanism. Span of control matters because it decides whether feedback happens at all. Stretch a manager past their limit and the feedback is the first thing to go, which means engagement is the next.

This is the same pattern we wrote about in the manager gap that breaks culture when you promote your top performers. A wide span makes that gap worse, because even a great manager cannot out-hustle bad math.

‍

The Hidden Cost Lives in the Middle

Your middle managers are the multiplier. Stretch them too thin and the damage compounds: weaker hires, slower decisions, more regrettable attrition. We made the full case for protecting this layer in why manager development pays off the most.

Span of control is the quiet version of the founder bottleneck. When a founder hoards decisions, the company stalls at the top. When a manager holds 15 reports, the team stalls in the middle. Same disease, different floor of the building.

‍

Audit Your Spans This Week

You do not need a reorg. You need a spreadsheet and one honest hour. Try this on Monday.

A couple of the steps deserve a note.

The complexity tag in step two is the whole game, and it is where the McKinsey archetypes earn their keep. A senior engineering team building new product is player/coach or coach work: keep it near 3 to 7. A support team running a known playbook is closer to facilitator or coordinator work, where 12 or more can be fine. Same company, very different right answers.

The one-on-one test in step four is the tell that cuts through everything. Ask each flagged manager a single question: when did you last have a real career conversation with each person on your team? If they cannot answer, the span is too wide, full stop. The number is never abstract. It shows up as the skipped one-on-one and the feedback that never came.

Here is the kind of thing that surfaces when you actually run this. A founder has a VP with 16 direct reports. He splits the team into two pods of eight, no new headcount, just one promoted senior. Within two months, two people who had looked "checked out" re-engage. They were never checked out. They were unseen. That is what a right-sized span buys you: the manager gets the airtime to actually see people again.

‍

When to Add a Layer, and When Not To

Adding a management layer is not failure. It is physics. Once a manager passes the right span for their work, you have two moves: split the team, or promote a lead.

But do not add layers to soothe an ego or mint a title. Add them when the coaching load is genuinely real. A good rule: if a manager has more than 8 people and the work is genuinely complex, you need another leader, not another all-hands.

The goal of our Six Levels framework is a culture of leadership, where you grow more leaders instead of collecting more followers. Right-sized spans are how you make the room for that. A manager buried under 15 reports cannot build a single new leader. A manager with 6 can build two.

‍

The Bottom Line

Your manager did not get worse. The math did. Span of control is the cheapest lever you have to protect engagement, and almost nobody pulls it on purpose. Count the reports. Tag the complexity against the work. Fix the worst one first. Then watch the people you thought you had lost come back to the table, because it turns out they were never gone. They were just never seen.

‍

‍

Frequently Asked Questions:

‍