Questions we answerTeam structure and leadership
How many people should report to one manager?
There is no correct number. The limit is set by how much of that manager's week is actually management, and by how different the reports' jobs are.
Free · a few minutes · starts from “I'm not sure how to structure the team”
The short answer
There is no correct number, and anybody offering one is describing a different business. The real limit is how much of that manager's week is management rather than delivery: somebody still carrying a full workload strains at a handful of reports, while somebody whose job is managing carries considerably more. Before adding a layer, check what is actually breaking — unclear ownership and decisions routing through one person look identical to too many reports, and a new manager fixes neither.
The published advice on this question is mostly a number, repeated. It is usually enterprise research about dedicated managers of similar teams, applied to a founder who is also doing a full job, which is the one case it does not describe.
What makes a span workable is not arithmetic. It is how much time the manager has for it, how similar the jobs are, and how much autonomy the people have. Six people doing the same thing, experienced, with clear ownership, is a light week. Four people doing four different things, all of whom need a decision from you before they can move, is not.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- One-to-ones are being cancelled because there is no room for them, not because they are unnecessary.
- You know what each person is doing but no longer know how well.
- New people are being absorbed by whoever has capacity rather than by whoever should own them.
Signs it's something else
- The pain is decisions waiting for you, rather than people waiting for you. That is an ownership problem.
- Only one or two relationships are hard, and the rest are fine.
- The team is the same size it was when this worked, and something else changed.
What's usually behind it
- A founder or lead who is managing alongside delivering, and feeling both slip.
- A team that has grown past the point where one person can hold every decision.
- Ownership that was never made explicit, so everything routes upward by default.
What people usually get wrong
- Adding a layer on top of undefined ownership, which inherits the ambiguity and adds a salary to it.
- Promoting the strongest contributor because the span is uncomfortable, and losing their output without gaining management.
- Treating a published figure as a target, and restructuring towards a number rather than towards a problem.
The options, and when each one fits
In no particular order. Which of these fits depends on your situation, not on the question you typed.
Redistribute ownership
Decisions route through one person because nobody else has explicitly been given them.
Free up the manager's time
The span would be fine if the manager were not also carrying a full delivery load.
Develop a team lead
Somebody internal already exercises judgement and would need management craft rather than domain knowledge.
Hire a manager
There is a coherent set of responsibilities for them to own, and nobody inside is close.
When doing nothing is the right call
If the span is uncomfortable but nothing is being dropped, waiting a quarter while ownership is made explicit is often the cheapest experiment available — and it frequently removes the pressure without a layer.
What the diagnostic asks
- How many people are in the team and how it is currently arranged.
- Who owns the work today and how clearly that is understood.
- Whether anyone internal could take a layer of responsibility.
- Whether the team is growing, steady, or shrinking.
“I don't know” is always an answer. Nothing is assumed on your behalf.
The routes it weighs
Every diagnostic weighs all ten routes. These are the ones that tend to matter for this question — a description of the rules, not a promise about your answer.
Redistribute
Move ownership of the work to where it fits, and make that explicit.
Process improvement
Change how the work flows — remove steps, name an owner, fix the hand-offs.
Develop
Build the capability in someone already in the team, with time and support.
Recruit
Recruit a new person for a durable, sizeable need that is central to the team.
Do nothing yet
Record the issue, set a revisit date, and decide what would change your mind.
What changes the answer
- A manager who is also delivering full-time is the constraint, whatever the headcount is.
- Reports doing very different jobs cost far more management attention than reports doing the same one.
- Decisions queueing rather than one-to-ones being squeezed usually means unclear ownership rather than too many people.
Get your own read
A handful of short questions, then the strongest route for your situation, what's also credible, what we still don't know and what would change our view. No account, no setup.
Related questions
- Do I need a management layer?A layer is justified by the number of decisions and people one person can hold, not by headcount milestones. Added to unclear ownership, it makes the ambiguity more expensive.
- Do I need another manager?Only if the problem is span of attention rather than unclear ownership. A manager helps when there are more people than one person can support properly; added to fuzzy roles, a manager adds a layer to the confusion.
- Everything comes back to me — what do I do?Decide which decisions genuinely need you, hand the rest over with the authority to go with them, and write down what only lives in your head. Most founders are the bottleneck because nobody has been told where the line is.
- Nobody owns this work. What do I do?Give it an owner. That is almost always the first move, and it is faster and cheaper than anything else on the list.
- Do I need a chief of staff?A chief of staff multiplies one leader's capacity across whatever matters that quarter. It works where the bottleneck is genuinely that leader — and disappoints where the problem is missing functional ownership.
- Do I need an HR person?Usually not as an employed role at this size. What gets called HR is three different jobs, and only one of them is a person you hire.