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
- Before hiring, ask: "Could we do this with one fewer person if we simplified the scope or process?"
- Measure output per person alongside total output.
- Protect high-performers from headcount dilution by keeping teams as small as the work allows.
- 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. A meta-analysis of social loafing further shows that individual effort tends to decline as group size grows, a distinct mechanism from coordination overhead that compounds the cost of adding headcount. (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
- Karau, S. J., & Williams, K. D. (1993). Social loafing: A meta-analytic review and theoretical integration. Journal of Personality and Social Psychology, 65(4), 681–706.
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.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Designing a Calm Company (Fried & Hansson)
- Default to asynchronous communication
Treat real-time communication as the exception, not the default — most things do not require an immediate response.
- Protect mornings for deep work — no internal meetings before noon
Morning is when cognitive capacity is highest for most people; spending it on reactive coordination is a predictable waste.
- Set realistic goals and chip away at them — resist "crush it" culture
Aspirational goals that require heroic effort normalize crisis; realistic goals with steady progress normalize calm.
- Maintain at most three active priorities at one time
More than three active priorities is the same as no priorities — attention cannot be shared four ways.
- Disagree and commit — reduce the decision drag of endless debate
Decisions that are made and executed at 80% confidence are almost always better than decisions endlessly refined but never taken.
- Make "no" the default — saying yes should require active justification
Every yes costs future time and focus; treat it as a commitment that requires real justification.