Contents
Two pizzas. That’s all it should take to feed a team. The rule is attributed to Amazon founder Jeff Bezos, and the company gives fewer than ten people as a guideline. It sounds like a break-room joke. In fact, Amazon rebuilt its organization and its software around it – and later corrected it itself. An example of the Team Principle of Size.
A Company Slows Itself Down
Situation
In the early 2000s, Amazon was growing fast. Its software was tightly interlocked, and central departments had a say in a great many things. New projects advanced slowly; an internal approval process for new initiatives was seen as bureaucratic. The more people joined, the more time went into coordination.
Connection to the team principle
The Team Principle of Size says: every additional member adds strength and costs coordination – a team should be as small as the task allows. Amazon experienced the first half of that sentence at the scale of an entire company. The additional people brought strength, but coordination grew faster than impact.
The Rule and What Comes With It
Situation
According to Brad Stone’s book “The Everything Store,” the company was to be organized into small, autonomous units that could work without constant coordination. Each team would own a service or product completely, from idea through build to operation, with no handoffs to others. Each team would include all the specialists it needed: development, testing, product management, operations. Each team was also to be given a metric that showed its impact. And the software was broken down into small, separate services so that a team could work on its part without asking the others.
Connection to the team principle
Headcount alone would have achieved nothing. A team of eight that needs five other teams for every change is really just part of a large group. That is why Amazon did not merely shrink its teams but shaped the task so that a small team could carry it. Only that makes the second half of the sentence true: “as the task allows.”
What the Research Says
Situation
The researcher Jennifer S. Mueller studied 26 development teams with 238 members. In the larger teams, individuals performed less well. The main reason she found was what she calls “relational loss”: members felt less supported.
Connection to the team principle
The finding shows a correlation, not proof of any particular number. But it explains what “costs coordination” means in everyday work. It’s not just about more meetings. In a large group, people know less clearly whom they can turn to. Research does not yield a fixed optimal size, and for some types of team, studies even find slightly better performance with more members.
Where Two Pizzas Aren’t Enough
Situation
In their book “Working Backwards,” the former Amazon executives Colin Bryar and Bill Carr describe the model’s weaknesses. Leaders who had mastered every discipline were hard to find. And some projects simply needed more people than two pizzas can feed. So Amazon evolved the model into the “single-threaded leader”: a leader who focuses exclusively on one initiative, with a team that depends as little as possible on others. By this account, what mattered most was not headcount but whether the person in charge had the skills, authority and experience the task required.
Connection to the team principle
The rule gave way to the task. That is not a defeat for the principle but a confirmation of it. Size is a means. The goal is for a team to move its work forward without constantly checking back with others. Where that takes twelve or twenty people, twelve or twenty is right – as long as outside dependencies stay small.
The Price of Small Teams
Situation
Amazon itself names the risks: duplicated work and silos between teams. To counter them, the company relies on written memos and regular weekly, monthly and quarterly business reviews.
Connection to the team principle
If you save coordination within teams, you have to organize it deliberately between them. It doesn’t disappear; it moves. Many small teams need a few fixed places where they learn about one another’s work.
Key takeaways
Key Lessons
- Don’t just check how many people are on your team – check how many others you all depend on to deliver a result.
- Give a small team a complete task. A piece of work that hinges on three handoffs won’t make any team fast.
- Bring all the necessary skills into the team instead of requesting them from outside as needed.
- Treat every size rule as a rule of thumb. If the task calls for more people, follow the task.
- Decide where small teams keep one another informed – otherwise things get built twice.
Summary
Amazon turned an observation into a design rule: small teams with full ownership move faster than large ones with many dependencies. The two-pizza rule is the catchy image for it. What came next is instructive. The company found that headcount is only a means and that some tasks need more people. That is exactly what the Team Principle of Size says: every additional member adds strength and costs coordination – and how small a team can be is set by the task, not by the pizza.