Two-Pizza Teams (Amazon)

Amazon’s principle of keeping teams small and giving them focused, sustained ownership of a product or service. Scope, authority, resources, and dependencies matter alongside approximate size.

The two-pizza-team idea is Amazon’s memorable shorthand for a small team with focused ownership. In Amazon’s account, the team has a clear product or service responsibility and the capabilities needed to maintain it across its lifecycle. The food metaphor is approximate; the important design questions concern scope, autonomy, dependencies, and sufficient resources.

Smallness alone does not create independence. A six-person group can spend its time negotiating dependencies, while a larger group may coordinate a tightly connected task well. Count the handoffs and decisions the work actually requires. The number of possible pairs grows with headcount, but that arithmetic is not a measurement of actual communication cost or a reason to split every team at a fixed threshold.

When to use it

When a team grows, responsibilities become diffuse, or an organizational boundary creates repeated coordination delays.

How it can help

Helps examine whether a team can own a coherent outcome and make relevant decisions without excessive handoffs.