Questions we answerTeam structure and leadership
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.
Free · a few minutes · starts from “I'm not sure how to structure the team”
The short answer
A chief of staff fits when one leader is the genuine bottleneck across several areas, when the work is coordination and follow-through rather than a function needing its own head, and when that leader will actually delegate. It is the wrong answer when what is missing is ownership of a specific function — that needs a functional leader, not a generalist — or when the real need is administrative support. The role is defined by the leader it serves, which makes it powerful where the diagnosis is right and vague where it is not.
The chief of staff role is unusual because it has no fixed remit. That is its strength when one leader is the constraint and the constraint moves every quarter, and its weakness when a company uses it to avoid naming what is actually missing.
It is not a junior version of a COO, and it is not an executive assistant. It is leverage for one person, and it only works if that person is genuinely the bottleneck.
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 is in every important conversation and is the reason several things are late.
- There are cross-cutting initiatives with no natural owner that keep stalling.
- You want someone to run the operating rhythm rather than own a function.
Signs it's something else
- One function clearly needs its own leader and everyone knows which.
- The need is scheduling, inbox and travel, which is a different and cheaper role.
- The leader in question is unwilling to let anyone else decide anything.
What's usually behind it
- A founder or executive who is the single point of coordination across several areas.
- Initiatives that start well and then stall because nobody chases them.
- A leadership team that needs its operating rhythm run by someone.
What people usually get wrong
- Hiring a chief of staff instead of the functional leader everyone knows is missing.
- Defining the role as "help me", which gives the person no way to succeed or be assessed.
- Using the title to give someone senior-sounding progression without senior responsibility.
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.
Chief of staff
One leader is the bottleneck across several areas and will genuinely delegate.
Functional leader
A specific area needs someone accountable for it, and you can name the area.
Operations or programme manager
The need is running things reliably rather than sharing a leader's judgement.
When doing nothing is the right call
List the last ten things that stalled and who would have unstuck each. If they cluster around one person, the role is worth considering. If they scatter across missing functional owners, this hire will not fix it and the pattern will repeat.
What the diagnostic asks
- How the team is arranged and where decisions route.
- Who owns what, and how clear that is.
- Whether anyone internal could take part of the load.
- Whether the team is growing, 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.
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.
What changes the answer
- A single leader who is demonstrably the bottleneck supports the role.
- A specific function with no owner points at a functional hire instead.
- Unclear ownership across the team means this role will spend its time on symptoms.
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
- 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.
- 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 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.
- Who should own this work?Ownership is accountability for an outcome plus the authority to decide. Anything less is a task list with someone's name on it, and it will not hold.
- 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 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.