Skip to main content
Back to Resources
Management

Managing too many direct reports? It's not you. It's the org chart.

Your org chart doubled. Managing too many direct reports isn't a willpower problem, it's a structural one. Here's the system that makes it sustainable.

Roadmap Team · Leadership Development
March 28, 202611 min read

The email came on a Tuesday in October. Reorg effective immediately. Two of Priya's peer managers were let go, and their teams, seven people combined, would report directly to her starting Monday.

She already had five direct reports. She now had twelve.

Same calendar. Same number of hours in the week. No additional guidance on how to manage too many direct reports, no training, no new tools. Just twelve names in her org chart and a recurring Monday 1:1 block that suddenly needed to stretch to accommodate six more people.

Three months later, she was still trying to figure out how to give every one of those twelve people the attention they deserved. She was failing, and she knew it. Not because she was a bad manager. Because the math did not work.

This is the situation more managers are finding themselves in right now. And if it is yours, the first thing worth knowing is: you did not create this problem. Your org did.


What "the great flattening" actually means for you

Over the past two to three years, organizations across industries have aggressively cut middle management. Middle management job openings have fallen more than 40% since 2022, according to Revelio Labs. The average number of direct reports per manager grew from 10.9 in 2024 to 12.1 in 2025, Gallup found in a study of nearly 9,000 managers. That is nearly 50% higher than when Gallup first measured this number in 2013.

This trend has a name: the Great Flattening. Companies are reducing the number of layers between frontline employees and senior leadership. On paper, it is about efficiency, speed, and reduced overhead. In practice, it means the managers who remain are absorbing the workload that used to be distributed across a broader leadership layer.

You are not imagining it. The org chart got flatter and your calendar did not get bigger.

What makes this particularly difficult for entry and mid-level managers is that most advice about handling it is written for senior leaders with the organizational authority to restructure their teams, create new leadership tiers, or delegate strategically. That advice assumes a kind of power most managers three to five years into their roles do not yet have.

You may not be able to change how many people report to you. But you can change how you manage them. The rest of this article is about exactly that.


How many direct reports is too many?

The short answer: it depends on the complexity of the work, your experience level, and how independently your direct reports operate.

The research benchmark holds at four to five reports for knowledge-worker managers dealing with complex, non-standardized work. Experienced managers working with more structured roles can stretch to six to nine. Beyond that, the cognitive math stops working.

Gallup data from 2025 shows that managers with seven or fewer direct reports score 20% higher on team engagement than those managing 15 or more. That gap is not explained by manager talent alone. It is explained by attention.

There is a cognitive ceiling on meaningful management relationships. Neurological research suggests humans can hold roughly four to five complex relationships in active working memory at once. When you are managing 12 people, you cannot be equally present to all 12 with the same depth you brought to five.

That is not a personal failing. It is the way the brain works.

The useful question is not "what is the ideal number of direct reports?" It is: given the number you actually have, how do you allocate your attention with intention rather than accident?


The double load female managers carry

Here is what almost no article about managing too many direct reports acknowledges: the math is worse for women.

Research consistently shows that female managers absorb a disproportionate share of invisible work on top of their official management duties. The McKinsey and Lean In Women in the Workplace report found that six in ten senior-level women report frequently feeling burned out, the highest level in 11 years of research. Female manager engagement fell seven percentage points in a single year, according to Gallup, the steepest drop of any manager group.

Part of what drives these numbers is what researchers call "office housework" and "mankeeping." Women managers are more likely to be asked to plan team events, mediate interpersonal conflicts, take notes in meetings, and provide emotional support to struggling colleagues, regardless of whether any of that is in their job description. A Lean In study found that female leaders are twice as likely as male counterparts to spend substantial time on diversity, equity, and inclusion work, and 40% say that work is not acknowledged in performance reviews.

When Keisha's org eliminated two management layers last year, she did not just inherit seven new direct reports. She inherited the conflict mediation work, the morale tracking, and the informal emotional support roles those managers had been quietly carrying. Within six months, she was logging off every Friday with a list of things she had not gotten to, a persistent feeling of failing her team, and no time for her own development goals. "I'm doing three people's jobs," she told her partner. "And one of them is invisible."

If you recognize yourself here, it is not because you are bad at setting limits. It is because you are operating in a system that has learned to rely on you absorbing what no one else is being asked to carry.

Naming this is not the same as solving it. But it is the necessary starting point. (For a deeper look at the emotional labor managers carry, see The hidden cost of emotional labor for managers.)


Why managing 12 people the same way you managed five won't work

Most advice tells managers to work smarter, not harder. But that assumes the problem is effort. The problem is bandwidth.

Gallup's 2025 data found that 97% of managers have individual contributor responsibilities on top of their leadership duties, and they spend a median of 40% of their time on non-managerial work. That means the average manager is running a full team and doing a significant chunk of her own independent work simultaneously.

Layering 12 meaningful management relationships on top of that is not a willpower problem. It is a structural mismatch.

Managing too many direct reports the same way you managed fewer does not fail because you are not trying hard enough. It fails because you are asking a different cognitive demand to fit into the same container. The 1:1 cadence that worked at five people requires twice the calendar real estate at ten. The mental space you used to hold for each person's context, goals, and development conversations gets crowded. Things start dropping. Not because you stopped caring, but because you ran out of room.

The solution is not more effort. It is a system that holds what your brain cannot hold anymore.


The management operating system: what scales when heroics don't

When heroic effort stops being enough, structure takes over. The managers who navigate large teams without burning out are not more disciplined or more talented. They have a repeatable operating rhythm, so each person on their team gets consistent attention without requiring the manager to reinvent the wheel every week.

Here is what that looks like in practice.

The non-negotiable 1:1 cadence

With more than eight direct reports, 1:1 scheduling gets complicated fast. But skipping 1:1s to recover time is a false economy. When direct reports lose their dedicated touchpoint with you, problems surface later and harder. What you save in meeting time you spend in crisis management.

The adjustment is frequency, not elimination. For direct reports working on stable, lower-risk work, a biweekly 1:1 may be right instead of weekly. For anyone in a critical project phase, onboarding, or a performance concern, the 1:1 stays weekly.

The key is documentation between sessions. When you have 12 people and see each one only every two weeks, you cannot rely on memory to carry the thread. Every 1:1 needs a persistent record: what was discussed, what was committed to, what is still outstanding. Not a scattered note in a doc. A structured record you can open in two minutes before the meeting and know exactly where you left off.

Roadmap keeps a persistent profile for each of your direct reports, so every 1:1 builds on the one before it. When you open the record before a meeting, the context is already there.

A priority ritual that surfaces who actually needs your attention this week

With 12 direct reports, you cannot give everyone equal attention every week. The managers who handle this well have a regular ritual for deliberately deciding where to focus, rather than defaulting to whoever is loudest or most recently in front of them.

A simple version: at the start of each week, spend ten minutes scanning your team. Who has something time-sensitive happening? Who has gone quiet and might need a check-in? Who is in a critical phase of a project? Who might you have been unintentionally neglecting?

This kind of intentional triage does not mean some people matter less. It means you are allocating your finite attention with purpose instead of accident. It is the difference between dropping things randomly and making deliberate choices.

One place for every promise to your team

This is the piece that falls apart fastest when teams grow. With five direct reports, a good manager can hold most of her outstanding commitments in working memory. With 12, that stops working. Things drop. Not from negligence, but from volume.

The fix is simple and non-negotiable: every commitment made in a 1:1 gets captured somewhere other than memory, organized by person, and surfaced before the next meeting. Not a general to-do list. A promise log connected to the person waiting on it.

When Priya finally moved her promise-tracking out of her head and into a system, she described the change this way: "I went from managing with guilt to managing with intention. I still have 12 direct reports. But I know what I owe each of them."

That is what scales. Everything else is just hoping your memory cooperates.


What you are allowed to stop doing

Here is the section most advice skips.

When you are managing too many direct reports, something has to give. The question is whether you decide intentionally what gives, or whether it gets decided for you by accident.

Most female managers, conditioned to absorb slack and over-function, let things drop in the worst possible order. They stop investing in their own development. They stop protecting the strategic thinking time that makes them better at the job. The reactive and performative work stays at full capacity while the things that actually create career momentum get cut.

A more useful question than "how do I do everything" is: given the team I actually have, which relationships need me most right now, and which things on my plate do not need to exist at all?

Saying no is a management skill. Triage is a management skill. Letting a low-stakes project sit at 80% so a high-stakes relationship gets 100% of your attention this week is not failing anyone. It is allocating a finite resource to where it actually matters.

You are not going to manage 12 people the way you would have managed five. Accepting that is not lowering the bar. It is building a sustainable system for the team you actually have.


Where to start when you're managing too many direct reports

You cannot fix the org chart. But you can build a system that works inside of it.

Start with one thing this week: before your next 1:1, open a document and write down one outstanding commitment from your last conversation with that person. Review it. Did you follow through? If yes, tell them. If not, address it directly.

That is the beginning of a promise-keeping system. Add the persistent 1:1 record next. Add the weekly triage ritual after that. One layer at a time, you build an operating rhythm that makes managing more people sustainable rather than just survivable.

The managers who hold large teams together are not doing something heroic. They have a system that does the holding for them.

Roadmap is the management operating system built for exactly this. One profile per direct report, every commitment tracked, every 1:1 building on the last.

Want more insights?

Explore more articles to help you lead with clarity and confidence.

Back to Resources