Dunbar's Number and Refactoring Team Topologies: The 5/15/50/150 Rule of Scaling
Anthropology says humans cap out at 150 stable relationships — and 50, 15, and 5 are also magic numbers. Why your team feels broken at 23 people, 52 people, and 153 people, and the refactor pattern that fixes it.
- Robin Dunbar (1992) proved humans can sustain ~150 stable relationships, with sub-tiers at 5, 15, 50.
- Teams and orgs collapse predictably as they cross each threshold — not because of bad management, but because of cognitive ceilings.
- Apply Team Topologies: split before you hit the threshold, not after.
- Amazon's 'two-pizza team' (~5–9 people) maps cleanly to the inner Dunbar circle.
- HR's job is to schedule team refactors as proactively as engineering schedules code refactors.
Almost every founder describes the same set of crises: it broke at 8, broke again at 25, broke spectacularly at 50, and the wheels came off at 150. They blame their hiring, their tooling, their offsite. Dunbar would say: stop blaming yourself. You hit a biological ceiling.
The 5/15/50/150 hierarchy
| Layer | Size | Relationship quality | Org analogue |
|---|---|---|---|
| Support clique | ~5 | Daily, deep, total trust | Pod / squad / 'two-pizza team' |
| Sympathy group | ~15 | Weekly, high context | Team / chapter |
| Affinity group | ~50 | Monthly, recognisable | Department / tribe |
| Active network | ~150 | Quarterly, name + face | Business unit / company |
What breaks at each threshold
- Crossing 5–9: pair-programming and informal sync stop working; you need a daily standup.
- Crossing 15: you need a tech lead and explicit ownership boundaries.
- Crossing 50: tribal knowledge becomes a liability; you need an org-wide handbook.
- Crossing 150: nobody knows everyone; politics emerges as a side-effect of cognitive limits, not character.
The team refactoring playbook
- At 80% of any Dunbar threshold, plan the split. Do not wait until you hit it.
- Split along value streams (see the Conway article), not along seniority or geography.
- Each new sub-unit owns its full stack: hiring, on-call, roadmap, comp recommendations.
- Preserve weak ties — cross-team rituals (hack weeks, demo days, internal conferences) keep the 50/150 layer alive.
- Re-measure team health (psychological safety, eNPS, citizenship) 60 days after the split. Expect a temporary dip, then improvement.
- 5–9: keep as isTwo-pizza team, no formal structure needed
- 10–15: add a tech leadExplicit ownership, one daily standup
- 20–50: split into 2–3 sub-teamsIndependent sprints, shared rituals
- 50–150: form a tribe with a directorChapter leads, handbook, demo days
- 150+: spin a new business unitIndependent OKRs, dedicated platform support
Takeaways
- Team breakage at certain sizes is biology, not bad management.
- Refactor teams proactively, not reactively.
- Pair Dunbar (the people math) with Team Topologies (the system math) for clean scaling.
- Robin Dunbar — Neocortex size as a constraint on group size in primates — Journal of Human Evolution, 1992
- Hill & Dunbar — Social network size in humans — Human Nature, 2003
- Skelton & Pais — Team Topologies — IT Revolution, 2019
Read next
All playbooksMelvin Conway proved teams ship their own communication structure as software. The Inverse Conway Maneuver flips this — HR designs reporting lines to mirror the ideal microservice architecture, not the legacy org chart.
Org charts tell you who reports to whom. REND tells you who lights up the room — and who turns the lights off. The next layer of Organizational Network Analysis.
Psychological safety doesn't just exist on a team — it spreads. The patient-zero behaviours of middle managers and how to interrupt the contagion before it collapses dynamics.