Three glowing spheres converging on a black background, representing a small team coordinating closely.
A two-pizza team is small enough that a few people stay in sync without heavy process, like these three points converging on one spot.

A two-pizza team is a team small enough to be fed by two pizzas, which works out to roughly five to ten people. Amazon never fixed an exact number, and different teams read it differently. The idea comes from Amazon and is attributed to Jeff Bezos. A team this size keeps everyone aware of what everyone else is working on, so it moves fast without heavy meetings or approval chains.

A plain analogy

Think about cooking dinner. Two people share the kitchen without stepping on each other. They talk as they go, and no one needs a schedule. Now imagine twenty cooks in the same kitchen. You need a rota, a head chef, and constant coordination just to avoid collisions. The two-pizza rule keeps a team in the first situation, where communication is cheap and natural.

How it works

The rule sets a hard ceiling on team size. Amazon uses ideally fewer than ten people per team. When a service grows too large for one team to own, Amazon splits it into separate two-pizza teams rather than growing a single team past the limit. This keeps the organization flat and each team autonomous.

Size Cap the headcount No team bigger than two pizzas can feed, ideally under ten people.
→
Own Single-threaded ownership Each team owns one product or service across its whole lifecycle.
→
Split Divide when it grows A service that outgrows one team becomes two teams, not one large one.

Two benefits follow from the size limit. First, small teams minimize lines of communication and cut the overhead of bureaucracy and decision-making, so they can focus on customers rather than internal process. Second, each team holds single-threaded ownership over a specific product or service, so responsibility is clear. This ownership model maps directly onto service-oriented and microservices architectures, where each service has one team behind it.

The two-pizza rule in the AI era

On 2026-06-30, Amazon CTO Werner Vogels published a post titled “A return to two-pizza culture” on his blog, revisiting the idea for a world of AI coding agents. His argument: AI agents let a small team build a working prototype in days instead of months. So teams should build and test first, then write the documentation once it reflects real experience. He describes this as preserving two-pizza culture while adapting the older habit of writing detailed specifications up front. Vogels notes that as companies scale, organizational entropy rises and threatens the speed that made small teams successful, which is why the size discipline still matters.

The two-pizza team pairs with working backwards , Amazon’s practice of starting from the customer and writing the desired outcome before building. Vogels argues that AI agents shift the order of those two habits, letting teams prototype before they document. His 2026 post is covered in more depth in the Werner Vogels two-pizza culture news item, and his wider views appear in coverage of his final re:Invent keynote . If you are shipping a first product with a small team, the from zero to production guide walks through the practical steps.

Further reading

Sources