Team structure and leadership
Is the shape of the team the problem? Management layers, ownership, seniority and the point at which a founder stops being able to hold everything — the decisions about how a team is arranged rather than how many people are in it.
Free · usually only a few minutes · no account
Structure problems disguise themselves as workload problems. Everything comes back to one person, decisions wait, and the obvious reading is that there are not enough people. Often there are plenty of people and no one is allowed to decide anything.
These questions are about the shape of the team rather than its size: who owns what, who can say yes without asking, and whether the layer of management everyone is arguing about would actually change anything.
The failure mode is adding a senior title to a structural problem and hoping the title fixes it. A new manager inherits whatever ambiguity was there before, and usually makes it more expensive.
Worth settling before any of these
- How many people report to whoever is currently the bottleneck.
- Which decisions have to come back to one person, and whether they genuinely need to.
- Whether anyone inside the team is close to being able to take a layer of this.
- Whether the work is written down well enough for someone else to pick it up.
The questions in this family
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.
Read the answerDo I need a CTO?
Not always, and not always yet. The question is what technical leadership the business needs over the next year or two — and whether that is a permanent seat, a fractional or interim leader, or capability grown from inside.
Read the answerEverything 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.
Read the answerDo 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.
Read the answerIs 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.
Read the answerDo 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.
Read the answerShould 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.
Read the answerWhen 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.
Read the answerDo 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.
Read the answerDo I need a CTO or a lead developer?
One sets technical direction and builds a team; the other builds the product well. Most early companies need the second and advertise for the first.
Read the answer
Nearby decisions
These families overlap with this one often enough to be worth a look — most team decisions turn out to belong to more than one of them.