Two-Pizza Teams

principle

Keep teams small enough that members can track one another’s work and coordinate directly. Once that visibility breaks down, divide the work into smaller units with explicit interfaces between them.

Amazon reportedly keeps teams around fifteen people—not because fifteen is magically productive, but because beyond that point members “can’t keep track of what all they are doing.” Adding people can therefore reduce a team’s practical capacity even while increasing its headcount.

Headcount consumes visibility

Every new member adds more than one person’s work: they add relationships, dependencies, and decisions that others may need to follow. Direct awareness eventually gives way to status meetings, relayed information, and assumptions. A coordination problem begins inside the team itself.

Small units contain that complexity within a human-scale boundary. Members can see who owns what and adjust without routing every change through management. Splitting also enables specialization, but only when the resulting units have clear responsibilities and ways to coordinate across their boundary.

Where it shows up

Amazon’s fifteen-person ceiling

The Amazon example treats team size as a limit on shared awareness: once people can no longer track what colleagues are doing, the team has crossed from direct coordination into management overhead.

Splitting moves the problem

A small team is not automatically coherent, and division does not eliminate coordination—it relocates it. If two units depend heavily on each other but lack clear interfaces, the internal problem becomes a multi-sided one across teams. Formal reporting lines may clarify ownership, but authority alone cannot guarantee cooperation.

Map who must track whom

For your next project review, ask every member to name the work elsewhere in the team that they must continuously track. If most people cannot answer—or everyone must follow nearly everyone else—redraw the team as smaller ownership units and specify the decisions, inputs, and outputs that must cross between them.

Episodes that teach this

You Can Only Have 150 Friends - Dunbar's Numbers Explained · explained at 9:02 3,058 views
Amazon teams are kept around 15 people because beyond that "you can't keep track of what all they are doing"