Questions we answerTeam structure and leadership
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.
Free · a few minutes · starts from “I'm not sure how to structure the team”
The short answer
Add a manager when the number of people or decisions reporting to one person makes it impossible for them to do either job properly, and when there is genuinely a layer of work for the new manager to own. Do not add one to resolve unclear ownership or an undefined strategy: a manager inherits the ambiguity and makes it more expensive. The cheaper move first is to delegate specific decisions and see how much of the pressure that removes.
A management layer is a real cost: a salary, a person taken out of doing the work, and a longer path between a decision and the people it affects. It earns that cost when there are genuinely more people than anyone can support well, or when a distinct body of work needs its own direction.
It does not earn it when the actual problem is that nobody knows who owns what. Adding a manager to that produces somebody whose job is to arbitrate confusion, which is a miserable role and a temporary fix.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- People are going without supervision, feedback or a decision because there is no time for them.
- One person is managing more people than they can hold in their head, and the newest joiners get the least attention.
- A distinct body of work has its own direction to set, and nobody is setting it.
- Somebody is ready to manage and will otherwise leave in order to do it elsewhere.
Signs it's something else
- Roles are unclear and the hope is that a manager will sort them out.
- The team is small enough that everybody already knows what everybody does.
- The real complaint is that decisions wait for one person, which is about delegated authority.
- You want a manager so that somebody else can have the difficult conversations.
What's usually behind it
- A team that has grown past the number of people one person can support with any real attention.
- A manager who is still doing their previous job alongside the new one.
- Fuzzy ownership that feels as though it needs somebody to referee it.
- A promotion that felt overdue, looking for a structure to sit in.
What people usually get wrong
- Promoting your strongest individual contributor and losing the output twice over.
- Creating a manager with responsibility and no authority over priorities, budget or hiring.
- Adding a layer in order to avoid deciding who owns what.
- Expecting somebody to manage a team and keep their entire previous workload.
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 from inside
Somebody is ready, wants it, and already knows the work and the people.
Recruit a manager
The team needs experience nobody internally has, and there is time to onboard properly.
Clarify ownership instead
The confusion is about who decides what, not about span of attention.
Split the team differently
Two bodies of work have drifted apart and one person is holding both.
A lead role without the full title
You want to test readiness without making an irreversible promotion.
When doing nothing is the right call
If the team is at the edge of what one person can support but not over it, waiting until the next hire lands is reasonable. Say now how many people you will act at, and act then, rather than reopening the argument every month.
What the diagnostic asks
- What feels wrong: fuzzy roles, everything coming back to you, silos or growth.
- The size of the team, who owns the work, and how much is written down.
- Whether somebody could grow into it, and whether the role is fundable.
“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.
What changes the answer
- Fuzzy roles point at deciding ownership first; a manager added on top inherits the ambiguity.
- A team that has outgrown one person's attention, with ownership already clear, is the honest case for a layer.
- Somebody internal who is ready makes development the cheaper and more durable route.
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
- How should I structure my small team?Most structure problems in small teams are ownership problems. Decide who owns what before you draw a chart or add a layer.
- 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.
- What should my next hire be?Start from the constraint rather than the wish list. The right next hire is the one that releases the most work or removes the largest risk — which is often not the role that feels most overdue.
- 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 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.