Overview
Dunbar’s number is the anthropologist Robin Dunbar’s estimate of how many stable relationships a person can maintain: about 150 people, those you would not feel awkward joining for a drink if you met them in a bar. It comes from his work on primate group size and brain size (the neocortex). The number is usually described in rings (roughly 5, 15, 50, 150), where closeness and time spent together drop off with each ring. It is used in organisation design as an argument for capping the size of units where people must trust one another.
Why it matters for organisations
Source: Leaders Eat Last: Why Some Teams Pull Together and Others Don’t
- Our ancestors lived in groups of about 100–150, where everyone was known and could be trusted to help the group. Our brains still expect that scale
- W. L. Gore & Associates caps its plants at about 150 people and builds a new one, sometimes next door, once a site grows past it. Bill Gore arrived at the figure by observation, when he walked the floor and no longer knew who worked for him
- Beyond that size people become abstractions to each other, which weakens trust and cooperation (see Milgram’s obedience experiment on distance and harm). A leader looking after a Circle of Safety can only do so for a group they can know
Use in team design
Source: Team Topologies
- Team Topologies treats Dunbar’s number as a limit on trust and recommends scaling by Dunbar: size team groupings to the natural limits of relationships, which it lists as about 5 people for close relationships and working memory, about 15 for deep trust, about 50 for mutual trust and about 150 for people whose capabilities we can remember (500 and 1,500 are suggested as further limits)
- Recommended sizes: a single team of about 5–8 people (up to 15 in high-trust organisations), a “tribe” (group of teams) of no more than 50 (150 in high-trust organisations), and divisions or business lines of no more than 150 or 500
- Growing past these limits makes trust break down. When a limit is reached, split off a semi-independent unit and realign the software architecture to the new team boundaries
- The same limits on team size cap the cognitive load a team can carry, so each team should own only as much software and domain complexity as it can understand
Caveats
- The 150 is a statistical estimate with a wide range of uncertainty, and its link to the neocortex has been disputed. Treat it as a rule of thumb, not a law
- The Team Topologies figures follow the book’s chapter on scaling teams using Dunbar’s number; it takes the rings from Dave Snowden’s “rule of 5, 15 & 150” and Dunbar’s 1992 paper on neocortex size and group size
Resources
- 2026-11-17 ◦ Leaders Eat Last: Why Some Teams Pull Together and Others Don’t (Simon Sinek, 2014) — Gore’s 150-person plants and Dunbar’s number
- Team Topologies — team size and trust limits in software team design