RSS Amplifier

Laws of Software Engineering · Jun 24, 2026

Dunbar's Number

0
Sign in to vote or save

Dr. Milan Milanović · Laws of Software Engineering

2 min read

There is a cognitive limit of about 150 stable relationships one person can maintain.

Takeaways

  • Dunbar’s number (~150) is the size of a community in which everyone knows each other’s identities and roles. Beyond this, our brains struggle to track relationships.
  • In software organizations, teams larger than ~100-150 will require more hierarchy or splitting into subgroups to function effectively. Coordination overhead rises sharply.
  • Smaller limits exist for closer relationships. Effective working groups might be much smaller than 150, but 150 is an upper bound for a community feeling.
  • Strong collaboration happens in groups far below the 150 threshold. Small teams win.

Overview

Dunbar’s Number means that an engineering department of 150 might function informally, but as it grows past that, you start needing more formal rules, communication channels, and management layers. Informal knowledge (“I know who to talk to about X”) begins to fail, and teams feel impersonal.

The rule encourages designing sub-teams or “teams of teams” that are small enough to work together effectively. Dunbar also proposed smaller social layers: ~5 intimate relationships, ~15 trusted collaborators, ~50 close working relationships, and ~150 stable social connections.

For software teams, high-trust work happens in tiny groups, teams larger than ~10-15 lose cohesion, and the 150 limit applies to departments or communities, not day-to-day collaboration.

Dunbar's Number illustration

Dunbar’s Number

Examples

Many startups report that around the 150-employee mark, the culture shifts. You no longer know everyone’s name, informal communication falters, and you start needing all-hands meetings and internal newsletters. That’s Dunbar’s number in action.

The Linux kernel community has thousands of contributors, but within it are maintainers and subsystem teams that are relatively small. Communication is structured into mailing lists by subsystem, so any given person communicates only with a small number of peers.

Amazon’s “two-pizza teams” (5-10 people) show that even within 150, effective working teams are smaller units.

Origins

Robin Dunbar introduced this number in a 1992 paper and popularized it in his book Grooming, Gossip, and the Evolution of Language. He found a correlation between primate neocortex size and social group size, predicting human size at ~150.

Examples such as historical village sizes, military company units, and communal groups often hover around 100-200, lending credence to the figure.

Further Reading

Want to go deeper?

All 63+ laws are covered with more depth, examples, and practical guidance in the Laws of Software Engineering book.

Get the Book

Last updated: June 24, 2026

Read the original on lawsofsoftwareengineering.com

Comments

Nothing yet. Say the first thing.

    Sign in to join the conversation.