Adding people to a team does not add capacity proportionally, and the reason is arithmetic rather than sociology.
Communication paths grow faster than headcount. Five people have ten possible pairs. Ten people have forty-five. Twenty have a hundred and ninety. Nobody maintains a hundred and ninety relationships, so at some point the team stops being one team and becomes several that share a name.
For a practical reference on workforce analytics software, Monitask provides this resource.
The useful question is not what the right size is. It is what breaks at each threshold and what to do about it.
Around three to five
Everyone knows what everyone is doing without any mechanism for it. Coordination is free. Decisions happen in conversation.
What breaks: nothing, until someone is away. A team this size has no redundancy, and one absence removes a capability entirely.
What to do: make sure at least two people understand anything critical. This is the only structural risk at this size and it is easy to ignore because everything else works.
Around six to nine
Still one conversation. Standing meetings start to have a purpose. Someone begins coordinating without anyone deciding they should.
What breaks: informal coordination starts costing real time, and it lands unevenly — usually on whoever is most conscientious.
What to do: name the coordination work rather than letting it be absorbed invisibly. It is a job, and someone is doing it.
Around ten to fifteen
The first genuine threshold. The team no longer fits in one conversation. Meetings where everyone attends stop being useful, because most attendees are not involved in most of the content.
What breaks:
- Everyone-attends meetings become a tax
- Nobody has the whole picture except the manager, which makes them a bottleneck
- Sub-groups form informally, and the informal boundaries are not the useful ones
- One-to-one time per person compresses. See span of control
What to do: split the meetings before splitting the team. Most of the pain at this size is meeting structure rather than headcount. Also: write things down, because verbal transmission has stopped covering everyone. See documentation as infrastructure.
Around sixteen to twenty-five
The team is now several teams that share a name and a manager.
What breaks:
- Sub-teams develop different practices and stop noticing
- Coordination between sub-groups requires deliberate mechanism
- The manager cannot know what everyone is working on and starts learning it from reports rather than observation
- Development conversations quietly stop happening
What to do: split it properly, into groups whose work is genuinely separable, with a lead each. Splitting along lines the work does not follow creates a coordination problem worse than the size problem — this is the most common way splits go wrong.
Beyond that
You have an organisation, and structure becomes a design question rather than a threshold question. Decision rights and interfaces between groups start mattering more than team size. See decision rights.
What actually determines the workable size
Not a universal number, and the same team can support very different sizes depending on:
Interdependence. Independent workstreams support larger groups. Highly interdependent work pushes coordination onto everyone and caps size early.
Experience. Experienced people need less direction and coordinate themselves.
Rate of change. Stable work supports larger teams than work being redefined quarterly.
Distribution. Distributed teams cap lower, because none of the coordination happens incidentally.
What growth does that nobody expects
Onboarding becomes continuous. Past a certain size and turnover rate, there is always someone in their first three months. The team's practices have to be written down, because they are being transmitted constantly.
Consensus stops working. It scales badly and stops entirely somewhere around a dozen. Organisations that treat consensus as a value rather than as a technique for small groups discover this slowly and painfully.
Specialisation appears whether or not you want it. People stop being interchangeable, which creates capacity and creates single points of failure. See roles versus people.
The manager's job changes completely, and usually without anyone acknowledging it. Managing five people who you work alongside and managing eighteen through two leads are different jobs, and the second is rarely trained for.
The signal to act on
Not headcount. The proportion of a typical meeting that is relevant to a typical attendee.
When most people in the room are not involved in most of the discussion, the team has outgrown its structure — regardless of the number. That signal appears before the coordination problems do, and acting on it early is much cheaper than acting on it after a reorganisation becomes necessary. See reorganisations.
For broader public guidance and background, consult the OECD.