After years of watching organizations restructure and managers take on expanding teams, a pattern emerges that rarely gets discussed directly. It’s not dramatic. There’s no single breaking point. But somewhere between seven and twelve direct reports – the number varies by role complexity and organizational context – something shifts. The manager stops leading and starts triaging.
The transition is gradual enough that it often goes unnoticed until damage has accumulated. A manager with four or five reports has time to think about each person’s development, to notice when someone is struggling, to have real conversations about career direction. With twelve or fifteen, those conversations become annual checkbox events. The manager becomes a coordinator of work rather than a developer of people.
What I’ve observed most consistently is that the first casualty is quality of feedback. When a manager has fewer direct reports, feedback can be specific, contextual, and frequent. It’s woven into regular one-on-ones and informal check-ins. When the span widens, feedback becomes scarce and often compressed into performance reviews. By then, the moment has passed. The employee has already internalized a pattern of behavior – good or problematic – without real-time course correction.
The Attention Economy Problem
There’s only so much attention a human can distribute in a week. A manager with a reasonable span can hold multiple people’s work in mind simultaneously. They can notice when someone’s usual quality dips, when a team member is unusually quiet in meetings, or when a project is drifting without explicit alarm bells. With too many reports, this ambient awareness disappears.
Instead, the manager operates on a reactive model. Problems have to surface loudly enough to be noticed. Quiet struggles – a person feeling stuck, imposter syndrome building, skill gaps widening – go unaddressed because there’s no bandwidth for detection. The people who need attention most often get it least, because they’re not the ones creating immediate crises.
I’ve seen this play out in hiring decisions too. A manager stretched thin will often hire faster and with less rigor, just to reduce the pressure on themselves. This usually backfires. A poor hire with too many other reports to manage can take months to address, and by then the damage to team morale and productivity compounds.
Decision Quality Degrades
Decisions made under time pressure tend to be worse decisions. When a manager is context-switching between too many people and projects, they’re making choices with incomplete information. They approve a project direction without fully understanding the technical implications. They make staffing decisions based on availability rather than fit. They resolve conflicts without taking time to understand root causes.
What’s particularly damaging is that these decisions often feel fine in the moment. The manager has made a call, moved on to the next fire, and doesn’t see the downstream consequences until much later. By then, the decision has calcified into process or expectation, and changing course is harder than getting it right initially would have been.
Individual Growth Becomes Incidental
One of a manager’s core responsibilities – whether explicitly stated or not – is developing the people on their team. This requires time. It requires knowing what someone wants to do next, what skills they need to develop, what opportunities would stretch them. It requires deliberate conversations and intentional project assignments.
With too many reports, this becomes whatever happens to occur. If someone proactively asks for a stretch assignment, they might get one. If they’re quiet about their ambitions, they stay in their current role. Promotions and growth opportunities go to the people who advocate loudest for themselves, not necessarily the people most ready or deserving. This creates a secondary problem: high performers who feel unsupported start looking elsewhere.
Communication Becomes Broadcast, Not Dialogue
I’ve noticed that managers with large teams tend to shift toward one-way communication. They send emails rather than have conversations. They hold larger group meetings rather than individual check-ins. They communicate policy and direction, but there’s less room for the two-way dialogue that builds trust and surfaces real problems.
This matters more than it might seem. People need to feel heard. They need to know their manager understands their specific situation, not just their job title. When communication becomes primarily broadcast, that connection erodes. Employees stop sharing concerns because they know the manager doesn’t have time to really engage with them. Information flow into the manager decreases, and their decision-making becomes even more disconnected from reality.
The Organizational Debt
The hidden cost of too-wide spans is organizational debt. Small problems don’t get addressed, so they become medium problems. Medium problems don’t get addressed, so they become crises. A person who could have been developed into a strong performer leaves the company instead. A conflict that could have been resolved early festers into team dysfunction. A process that could have been improved continues to waste time.
None of this is catastrophic on any given day. But over months and years, it compounds. The team’s output plateaus or declines. Turnover increases. The remaining people feel unsupported and start protecting themselves rather than taking risks. The manager, feeling overwhelmed, works longer hours and burns out.
The tricky part is that this situation often looks acceptable from the outside. The team delivers work. Projects complete. Revenue targets are hit. But the efficiency is lower than it should be, and the human cost is real. The manager is exhausted. The team members feel neglected or invisible. The organization is running on fumes rather than momentum.
What I’ve learned from watching this repeatedly is that the right span of control isn’t a universal number. It depends on the complexity of the work, the maturity of the team members, the organizational structure, and the manager’s own capacity. But there is a threshold for every manager, and when it’s crossed, the quality of everything they touch degrades. The solution isn’t always to reduce headcount – sometimes it’s to add a layer of management, or to restructure how work is distributed. But ignoring the problem doesn’t make it go away. It just makes it more expensive to fix later.
