Spans and layers: how many direct reports is too many?

Two numbers describe the shape of any company. Span is how many people report to one manager. Layers are how many levels of managers sit between you and the person doing the work. Almost every “why are we so slow now?” problem in a company of 10 to 200 people comes back to one of them.

Span: it's about the work, not a number

People want a rule. Five reports, seven, ten. But span follows the work. When the work is alike and repeats, one manager can support a lot of people. The decisions look the same. When the work is hard and every call takes judgment, the same manager drowns with far fewer. Each person needs real thinking, not a quick yes.

So don't just count heads under a manager. Ask this. Is each person getting decisions made, getting coached, getting unstuck? Or has the manager quietly become someone who just runs status meetings? A span is too wide the moment managing stops happening. That number is different on every team.

A span isn't too wide because of the count. It's too wide the moment people stop getting managed.

Layers: every level should own something

Layers fail the other way. Each level of managers you add puts one more handoff between a question and an answer. A little of that comes with size. Too much, and decisions die on the way. They go up, sideways, and back down before anyone who can say yes sees them.

The sign of an extra level is a manager who manages one or two people. That job usually exists to pass messages along, not to own a result. It looks like structure. Really, it's a speed bump with a job title. Cutting it almost always speeds the company up. And the people below get a real decision-maker instead of a messenger.

The two problems look the same from your chair

This is why it's hard to spot on your own. Spans too wide and too many layers cause the same problem. Things feel slow. Balls get dropped. And you can't name one person at fault.

But the fixes are opposites. Spans too wide need more structure: split the team, add a role. Too many layers need less: cut a level, and give the managers who stay more people. Guess wrong and you make it worse. You add a level to a company that was already too tall. Or you flatten a team that was already unmanaged.

So look at the shape. Don't guess it. See where decisions really go, not where the org chart says they go. Then change the structure.

Flat isn't the goal

People treat “flatten the team” like it's always good. It isn't. Flat means fewer levels and faster decisions. But push it too far and each manager has too many people. Nobody really gets managed, and your best people burn out covering the gap. Aim for the fewest levels you can run. Every person should still have a real manager and know what they own.

How a Staff Analysis checks it

This is the Structure part of a Staff Analysis. It maps who really reports to whom and how many levels you have. It finds where decisions stall or pile up. It sorts the jobs that carry too much from the ones that only pass messages along. You get the few moves that fix the shape: widen here, cut a level there, split this job. They come in order, with a 90-day plan. It's about roles, not people. It never points at a named person.