The average manager in the United States went from 10.9 direct reports in 2024 to 12.1 in 2025. That is according to Gallup’s 2025 analysis of span of control, and the same research shows the number has climbed nearly 50% since 2013. Thirteen percent of managers now oversee 25 or more people. And here is the part that turns a staffing statistic into a leadership problem: 97% of those managers are still doing individual contributor work on the side, spending a median of 40% of their time on it.
Nobody sat you down and asked whether you could lead twelve people well. The number just crept up while you were busy. Someone left and was not backfilled. A reorg dissolved a layer and split the survivors across the managers who remained. A hiring freeze meant the two people you were promised became zero. Your span of control grew. The hours in your week did not, and neither did the amount of attention any one human being can give.
The number nobody actually chose
Span of control is one of the oldest ideas in management, and for most of the last century the working answer was somewhere between six and eight direct reports. That range was not arbitrary. It reflected a real limit on how many relationships one person can hold with any depth, how many sets of goals one person can track, how many careers one person can meaningfully develop at once.
What is happening now is that the number is being set by cost pressure rather than by leadership capacity. Companies are cutting the middle. Deloitte’s 2025 research on the future of the middle manager found middle management job postings in the US were down 42% at the end of 2024 compared with spring 2022. The trend has a name now, “delayering” or “unbossing,” and an accelerant: Gartner has predicted that by 2026, 20% of organizations will use AI to flatten their structure and eliminate more than half of current middle management roles.
Gad Allon, who teaches operations at Wharton, has written about this as “the great flattening,” and his point is the one most executives skip past. Removing a management layer does not remove the management work. It just moves that work onto whoever is left, usually without anyone naming it, resourcing it, or checking whether it is physically possible. The org chart looks leaner. The remaining managers are quietly underwater.
Twelve is not six, twice
The instinct when your team doubles is to run the same playbook faster. Same 1:1 cadence, same review habits, same open door, just compressed into less time per person. That does not work, and it fails for a reason worth understanding rather than just powering through.
Attention does not scale linearly. When you had six people, you could hold each person’s context in your head: what they are working on, where they are stuck, what they want next in their career, how they are actually doing this week. At twelve, you cannot. The load is not double; it is worse than double, because you now also have to manage the coordination, handoffs, and conflicts among twice as many people, and those interactions multiply faster than the headcount does. A team of six has fifteen possible pairings. A team of twelve has sixty-six. The relationships you are responsible for did not double. They more than quadrupled.
This is why the Gallup data on engagement gets interesting. The naive read is that bigger teams are simply worse, but that is not what the numbers say. Engagement held up on large teams when one specific thing was true: people strongly agreed they had received meaningful feedback. Roughly seven in ten stayed highly engaged regardless of team size when that box was checked. The size is not the killer on its own. The killer is what size does to the frequency and quality of real contact between a manager and each person, and feedback is the first casualty.
What breaks first, and it is not what you expect
When managers get overloaded, most of them assume the danger is that a ball gets dropped. A deadline slips, a deliverable ships broken, a customer gets missed. Those things happen, but they are the visible failures, and visible failures get attention. The quieter and more expensive failure is that your contact with each person gets shallow.
Shallow contact looks fine from the outside. You still have the 1:1s. You still answer the Slack messages. You still show up to the reviews. But the conversations turn transactional: status, blockers, next steps, done. What disappears is the layer underneath, the part where you notice that a strong performer has gone quiet, or that someone is three weeks into quietly resenting a decision, or that a person is ready for more and about to leave because nobody has said so out loud. That layer is where retention and development live, and it is exactly the layer that a wide span squeezes out first, because it is the part with no deadline attached.
I watched this happen to me directly. During a stretch of restructuring years ago in my IT operations career, I absorbed a peer’s team on top of my own with no reduction in my project load. I went from seven direct reports to fourteen inside a month. My honest belief at the time was that I was handling it. My calendar was full, every 1:1 was happening, nothing was on fire. What I could not see was that I had gone from knowing my people to merely tracking them. I lost two of the fourteen within a year, and in the exit conversations both said a version of the same thing: they had stopped feeling led. Not mistreated. Not overworked. Just unseen. I had been present at every meeting and absent from every relationship, and I did not notice the difference until it cost me two people I could not afford to lose. That is the tax a wide span levies, and it does not show up on any dashboard until someone quits.
Leading a wide span without pretending
You usually cannot fix the number. Telling your boss “twelve is too many” is worth doing once, clearly, with the research behind it, but you should assume the answer is no and lead accordingly. The managers who survive a wide span do it by changing how they lead, not by working more hours. A few shifts that actually hold up.
Stop trying to be the single point of contact for everything. At six reports you could be the hub every question routed through. At twelve you become the bottleneck your own team routes around, waiting on you while work sits. The fix is to push decision rights down explicitly. Name who owns what, and make sure your team knows they do not need you in the room to move. Clarity about who actually owns a given decision is worth more than your availability, because it removes the wait entirely instead of just making you faster at clearing the queue.
Lead through intent, not instruction. When you cannot be close to every piece of work, you have to make sure people can make good calls without you. That means telling them the destination and the reasoning behind it, then letting them find the route. This is commander’s intent, and it is the difference between a team that stalls when you are unavailable and one that keeps moving in the right direction because they understand what you are actually trying to achieve.
Build a layer under you, even an informal one. A wide span is more survivable when a few of your strongest people take on real scope: mentoring newer teammates, owning a workstream end to end, running a piece of the operating rhythm. This is not offloading; it is developing the next tier of leaders, and it extends your reach while giving your best people the growth that keeps them from leaving. The manager with twelve reports and two informal leads under them is running a genuinely different structure than the one trying to hold twelve individual threads alone.
Protect the depth of the contact you can afford. You cannot give twelve people the same depth you gave six, so stop pretending you can and be deliberate instead. Guard your 1:1s as the one place real conversation happens, and resist letting them decay into status updates that could have been a message. Feedback is the thing the research says keeps engagement alive on large teams, so make that the non-negotiable use of the limited attention you have.
Say no to work at the intake, because you are the constraint now. When your span is wide, every new project, committee, and “quick favor” you accept comes directly out of the attention your team needs. The discipline of controlling what work you take on stops being an operational nicety and becomes the main lever you have. A team of twelve led by a manager who is already fully booked is a team that ships late and loses people, and the only variable you fully control is what you refuse.
The honest version of the tradeoff
The flattening is not going to reverse. The economics that drive it, fewer managers plus AI-assisted reporting equals lower cost, are too attractive to executives, and Deloitte’s data on the collapse in middle management postings suggests the shift is structural, not a blip. If you manage, you should plan on your span being wide for the rest of your career and get good at leading that way on purpose.
What you cannot do is lead twelve people the way you were taught to lead six and tell yourself the gap is just effort. It is not effort. It is arithmetic. Attention is finite, relationships multiply faster than headcount, and the part of leadership that gets crowded out first, real contact with each person, is the part that actually holds a team together. Manage the wide span like the real constraint it is, or it will quietly manage you, one unnoticed departure at a time. The whole game becomes deciding where your limited attention goes, which is just another way of saying that a wide span turns trust and clarity from nice-to-haves into the only things holding the whole thing up.