the two-pizza team

ops culture

The rule that a team should be small enough to feed with two pizzas.

Attributed to Jeff Bezos, the idea is that communication overhead explodes as a team grows, so smaller teams move faster and own their work more clearly. It is a rule of thumb for autonomy and the organizational half of building loosely coupled systems.

The two-pizza team is Amazon's rule that a team should be small enough to be fed by two pizzas, which lands somewhere between six and ten people. The pizza is a memorable proxy for the real constraint, which is communication overhead: coordination cost grows with the square of team size, so small teams spend more of their time on work and less on staying synchronized.

The part that gets dropped is that team size was never the actual point. The rule came bundled with autonomy and ownership: a team that small only functions if it can decide, deploy and operate without waiting on others, which is why the same reorganization produced the service boundaries and the API mandate. Small teams inside an approval-heavy organization get the coordination costs anyway, plus less capacity to absorb them.

The honest limits are worth stating too. Small teams have small bus factors, they struggle to sustain on-call rotations, and splitting work that is genuinely coupled produces coordination between teams instead of within them, which is more expensive rather than less. Conway's law is the check: the team structure will become the architecture, so choose boundaries you would actually want to live with.

Also known as: two-pizza rule, 2-pizza team

← All glossary entries