Amazon's two-pizza rule: autonomous teams small enough for two pizzas

After the 2000 dot-com crash forced two rounds of Amazon layoffs, Bezos wanted to keep hiring lean and move faster. In early 2002 he took his first 'think week' — reading time modeled on Bill Gates — and returned to the senior leadership team with a plan to restructure the whole company around small teams.

Autonomous groups of under ten — small enough that two pizzas feed them — each owning a problem, competing for resources and shipping without heavy coordination.

Presenting in the basement of his home, Bezos said Amazon would organize employees into autonomous groups of fewer than ten people — 'two-pizza teams' — set loose independently on the company's biggest problems. Teams were allowed to compete for resources and duplicate effort, on the theory that being freed from intracompany communication constraints would let them move faster and get features to customers sooner.

The rule became a defining Amazon operating principle: decades later AWS still describes its service teams as small and almost wholly autonomous, with more than 200 service teams working that way. The idea was copied across the tech industry and became shorthand for how Amazon scales innovation without scaling bureaucracy.

Amazon's 'two-pizza team' rule began in early 2002, after the dot-com crash forced two rounds of layoffs. Jeff Bezos, who had borrowed Bill Gates' habit of taking an annual 'think week' to read and reflect, returned from one and presented his next big idea to the senior leadership team in the basement of his home.

The company, he said, would restructure around what he called two-pizza teams: autonomous groups of fewer than ten people, small enough that a couple of pizza pies could feed them while working late. These teams would be set loose independently on Amazon's biggest problems, would compete with one another for resources, and would sometimes duplicate effort — a deliberately Darwinian arrangement.

The logic was coordination cost. Freed from the constraints of heavy intracompany communication, loosely coupled teams could move faster and get features to customers quicker. Bezos put the idea in a memorable form: 'We try to create teams that are no larger than can be fed by two pizzas. We call that the two-pizza team rule.'

The structure proved durable. An AWS principal writing in InfoWorld in 2021 reported that the principle was still 'religiously adhered to' across AWS — teams stay relatively small and almost wholly autonomous, and the cloud unit runs as more than 200 such service teams. The rule became one of the most imitated organizational ideas in technology.

Small teams reverse the default: instead of adding people to a hard problem, Amazon removed coordination overhead by shrinking the unit.

Autonomy plus competition meant teams could try different answers in parallel and duplicate effort when necessary.

Tying team size to a concrete image — two pizzas — made the constraint memorable enough to survive twenty years.

Owning a slice of work end to end turned every team into a miniature business with a customer to satisfy.

Make the unit of work small enough to be autonomous: a team that two pizzas can feed can also own its slice of the problem end to end — coordination cost, not talent, is what caps team speed.

The two-pizza rule became Amazon's most quoted organizational invention and spread far beyond it, appearing in business books, management courses and startup playbooks. Insiders later described refinements — including 'single-threaded' leaders and teams for bigger bets — while AWS kept the small-team principle for its hundreds of service teams, and the rule outlived Bezos' tenure as CEO.