Questions we answerTeam structure and leadership
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.
Free · a few minutes · starts from “I'm not sure how to structure the team”
The short answer
There is no headcount that is correct for a team. A team is too small when the work it is genuinely accountable for cannot be done by the people in it at a sustainable pace — and it usually feels too small long before that, because of unclear ownership, a process nobody designed or one person holding everything. Establish what would actually stop if nobody joined. If the answer is specific and important, the team is short-handed. If the answer is vague, the problem is probably shape rather than size.
Nobody benchmarks their way to this answer. Comparable teams elsewhere have different tooling, different scope and different definitions of the same job title, and half of them are struggling too.
The only frame that works is internal: what is this team accountable for, and can the people in it deliver that at a pace they could keep up for a year? Everything else is anecdote.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- You can name specific commitments the team cannot meet, and they are not one-offs.
- People are covering two roles each and both are suffering.
- The scope has grown demonstrably and nothing has been taken away.
Signs it's something else
- Everyone is busy but nobody can say what would stop if the team were bigger.
- Most decisions wait for one person, so extra hands would wait too.
- The same work is being redone because standards or hand-offs are unclear.
What's usually behind it
- A scope that has grown steadily while the team stayed the same size.
- Ownership so unclear that work takes two people to get through one decision.
- One person holding several roles at once, which makes the whole team feel thin.
What people usually get wrong
- Benchmarking headcount against other companies with different scope and tooling.
- Adding people to a team where the constraint is decisions rather than hands.
- Growing the team without taking anything off it, so the same feeling returns at the larger size.
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.
Add capacity
The commitments are genuine, owned and simply exceed the hours available.
Reduce the scope
The team is accountable for more than anyone ever decided to resource.
Fix ownership
Work is slow because decisions queue, not because nobody is doing the work.
When doing nothing is the right call
If you cannot name what would stop without more people, that is worth knowing before you spend a salary finding out. A month of writing down what the team is actually accountable for tends to answer this question on its own.
What the diagnostic asks
- How many people are in the team and how the work is arranged between them.
- Who owns what, and whether that is clear to everyone.
- How much of the process is written down.
- Whether the pressure is growing, steady or temporary.
“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.
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.
Do nothing yet
Record the issue, set a revisit date, and decide what would change your mind.
Outsource
Hand a defined, ongoing scope of work to an external provider.
What changes the answer
- Work with no clear owner points at structure rather than size.
- A scope that has grown while headcount held steady supports the size reading.
- A process that lives in people's heads makes any team feel smaller than it is.
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.
- 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.
- How do I know if my team needs more headcount?Look for a gap that is durable, growing and visible in outcomes rather than in how busy people feel. Missed commitments, work that has quietly stopped and an inability to absorb anything new are better evidence than hours.
- Is this a busy period or a real capacity problem?A peak has a shape and an end; a capacity problem does not. Telling them apart before you commit to a salary is the single most valuable thing you can do here.
- 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.