Protect the advantages of small — resist headcount as a measure of success

Adding people to a team adds communication overhead faster than it adds output — protect the productivity of small.

Why it works

Communication overhead in a team scales approximately quadratically with headcount (n² connections). A small team can move faster and maintain higher shared context than a larger one executing the same task — but only if the work is not artificially expanded to justify the headcount. The "calm company" principle resists the cultural equation of growth with progress by valuing output per person over total output.

How to do it

1. Before hiring, ask: "Could we do this with one fewer person if we simplified the scope or process?"
2. Measure output per person alongside total output.
3. Protect high-performers from headcount dilution by keeping teams as small as the work allows.
4. When a team feels too big, look at the communication load first — it is often the signal.

Evidence

Brooks’s Law (adding people to a late software project makes it later) reflects real coordination cost data from project management research. Small team advantages are well documented in agile software contexts. (observational)

Small-team advantages are domain-specific; tasks requiring diverse expertise or massive parallel execution do benefit from larger teams. The principle applies most strongly to knowledge work.

Sources

• Brooks (1975), The Mythical Man-Month — empirical observations on team size and productivity

Common mistake

Measuring organizational health by headcount growth rather than output per person, which optimizes for size while degrading the coordination advantages that made the original team effective.