Questions we answerTeam structure and leadership
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.
Free · a few minutes · starts from “I'm not sure how to structure the team”
The short answer
In a small team the structure question is usually about ownership rather than hierarchy. What matters is that every important outcome has one name against it, that the people doing the work can make ordinary decisions without asking, and that nothing critical lives only in one person's head. Layers are worth adding when the number of people reporting to one person makes those things impossible — not at a headcount milestone, and not because an org chart looks thin.
Founders often reach for an org chart when the real issue is that responsibilities are fuzzy, everything comes back to one person, or work falls between people.
The diagnostic asks what feels wrong and points at the smallest change that would help.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- Work falls between people, and each assumed the other had it.
- Two people are doing overlapping work and neither will say so.
- New joiners cannot tell who to ask about what.
Signs it's something else
- The shape is clear and there is simply more work than it can hold.
- Everything routes through one person, which is about delegated authority rather than structure.
- One relationship is not working, which no chart will resolve.
What's usually behind it
- Roles that were never written down because everyone knew each other.
- Growth that has made the old shape stop fitting.
- A founder who is still the answer to every question.
What people usually get wrong
- Drawing the chart around the people you have, so it expires when someone leaves.
- Copying a structure from a much larger company with problems you do not have yet.
- Adding a layer before deciding who owns what.
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.
Name owners for each area
Responsibilities are fuzzy and work is falling between people.
Redraw around outcomes rather than tasks
Roles were written as lists of activities and have drifted out of date.
Give someone a lead role
A group of work needs day-to-day direction and there is someone ready.
Recruit into a defined gap
Ownership is clear and there is genuinely nobody to own one part of it.
When doing nothing is the right call
A small team that knows what each other does rarely needs a chart. If nothing is being dropped and nobody is confused, leaving the shape alone until growth actually strains it is the cheaper choice.
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 the team is growing, holding steady or shrinking.
- Whether anyone inside the team could take on more than they hold today.
“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.
What changes the answer
- Fuzzy roles point at deciding ownership, not adding people.
- Rapid growth with a fundable hire can justify a new role once ownership is clear.
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
- 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.
- 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.
- 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.
- 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.