The two-pizza rule, twenty years on

Early in Amazon's history, a rule took hold: no team should be bigger than two pizzas can feed. It is quoted in almost every book about how to run teams. It is also usually quoted wrong.

The size was the side effect

The point was never the number of slices. It was that each small team owned one thing end to end, with its own goals and its own way to ship, and did not need permission from five other teams to do it.

Small teams were simply what you got when you drew the boundaries that way. Fewer people meant fewer meetings, faster decisions, and nobody hiding in the middle.

Where it breaks

Teams that copy the size without the ownership end up worse off. They have eight people and twelve dependencies, and every launch turns into a negotiation.

A small team that cannot ship on its own is just a small committee.

The rule also gets harder as a product grows. Some work, like payments or security, touches everything. Amazon's answer was to turn those into services with clear interfaces, so other teams could use them without asking.

What you can borrow

Before you split a team, write down what each new team will own and how it will measure success. If you cannot write one sentence for each, the split will create more meetings, not fewer. Size follows ownership, never the other way around.