Questions we answerTeam structure and leadership
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.
Free · a few minutes · starts from “I'm not sure how to structure the team”
The short answer
You need a layer when one person can no longer do both jobs properly — when the number of people and decisions routing through them means either the management or the work is being neglected, and there is genuinely a coherent set of responsibilities for a new manager to own. You do not need one because the team crossed a headcount number. A layer added to unclear ownership inherits the ambiguity and adds a salary to it, and the cheaper move is almost always to delegate specific decisions first and see what pressure remains.
Management layers get added for two reasons: because someone is drowning, or because the org chart looks flat next to companies of a similar size. Only the first one is a reason.
The test is not how many people report to someone. It is how many decisions do, and whether those decisions genuinely need them.
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 person has more reports than they can meet properly and still do their own work.
- There is a describable set of responsibilities the new manager would own, not just people to supervise.
- Decisions are late specifically because one person is the only route to them.
Signs it's something else
- Nobody can say what the manager would decide that isn't decided today.
- The real problem is that priorities change weekly, which a layer will transmit rather than absorb.
- The motivation is retention — someone deserves progression — and management is the only path on offer.
What's usually behind it
- One person with more direct reports than they can give attention to.
- Decisions queuing behind someone who is also trying to do their own job.
- A wish to create a promotion path, which is a real need pointed at the wrong solution.
What people usually get wrong
- Promoting the best individual contributor into management and losing them at both.
- Adding a layer to a team whose actual problem is that nobody has decided who owns what.
- Creating a manager with reports but no authority, which adds a meeting rather than a decision-maker.
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.
Promote or develop internally
Someone is close, wants it, and the team would accept them leading it.
Hire a manager
The layer is real, nobody internal is ready, and the role owns outcomes rather than just people.
Delegate decisions instead
The pressure is decision volume and specific decisions could simply move.
When doing nothing is the right call
Try delegating three specific decisions for a month first. If the pressure eases, the problem was decision routing rather than structure, and you have saved a salary. If it does not, you now have evidence rather than a feeling, and a much clearer brief for the role.
What the diagnostic asks
- How many people are in the team and how it is arranged.
- Who owns the work today and how clear that is.
- Whether anyone internal could take a layer of it.
- 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.
Recruit
Recruit a new person for a durable, sizeable need that is central to the team.
Develop
Build the capability in someone already in the team, with time and support.
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.
Do nothing yet
Record the issue, set a revisit date, and decide what would change your mind.
What changes the answer
- A clearly overloaded span of control supports adding a layer.
- Unclear ownership argues for fixing that first — a manager cannot inherit clarity that does not exist.
- A credible internal candidate changes it from a hire into a development decision.
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 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.
- Should I promote internally or hire a manager?Promotion keeps context and risks losing a good contributor; hiring brings experience and starts from zero context. The deciding factor is usually support, not talent.
- 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.
- Is my team too small?Team size only means something against the work. The useful question is whether what is being asked of the team is achievable by the people in it, arranged the way they are.
- 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.
- When should a startup hire a COO?When operational load is genuinely holding the business back and there is a defined remit to own — not when a founder wants to stop doing the parts of the job they dislike.