What is the “two pizza team” rule?
The two pizza team rule, attributed to Jeff Bezos, is the principle that no internal team should be larger than what two pizzas can feed — practically, 6-10 people. Any team larger than that produces communication overhead that destroys productivity, slows decision-making, and creates internal politics. The principle is operationalised at Amazon as the foundation of how the company structures product, engineering, and operational ownership.
The communication math
The principle has a mathematical basis: communication channels in a team grow at n(n-1)/2. A 4-person team has 6 channels; a 10-person team has 45; a 20-person team has 190. The communication overhead grows much faster than the productive throughput. Past 10 people, most teams spend more time coordinating internally than building externally.
Why two pizza teams work
Four operational benefits. (1) Decision velocity — small teams reach decisions in single conversations; large teams require multiple meetings. (2) Ownership clarity — small teams own their outcomes unambiguously; large teams diffuse responsibility. (3) Communication efficiency — small teams operate without process; large teams require formal structure. (4) Recruiting selectivity — small teams can carefully evaluate each new member; large teams accept hiring compromises.
Two pizza teams at scale
The key question: how does an organisation grow to thousands of employees while preserving two-pizza-team properties at the individual unit level? Amazon’s answer: organise the company as a network of two-pizza teams, each owning a service or product with API-style interfaces between teams. The result is a “service-oriented” organisational architecture mirroring Amazon’s technical architecture.
Common implementation failures
Three patterns. (1) Two pizza teams without clear ownership — small teams with overlapping responsibilities create more coordination overhead than fewer larger teams. (2) “Two pizza” used as headcount cap without process — teams cap at 10 but communication channels with adjacent teams explode. (3) Founder romanticism — early-stage founders use “two pizza” rhetoric to justify under-hiring when their company actually needs more capability.
Türkiye context
Türk hierarchical organisational traditions sometimes resist two-pizza-team decentralisation. The cultural default — clear top-down authority and team-level deference — clashes with the autonomous decision-making that makes two pizza teams productive. Successful Türk scaling companies (Trendyol, Hepsiburada, Insider) have explicitly built two-pizza team architectures, often with founder coaching to overcome the hierarchical default.
Related: Founder Syndrome, Disagree and Commit, Founder Mode.