The Two‑Pizza Team Concept: Why Small Cross‑Functional Teams Outperform Large Ones

Before introducing the "two‑pizza team" idea, the article presents a scenario where a CEO asks HR how many developers are needed for rapid project growth, HR suggests hiring a thousand people, while the CTO references Jeff Bezos' famous quote that the optimal team size is one that can be fed with two pizzas.

The author uses this anecdote to question why many projects tend to expand team size, noting that adding more people does not automatically solve tight schedules or heavy workloads, and that larger teams often become less efficient.

Illustrating the concept, the article humorously estimates that a team fed by two pizzas would consist of no more than 16 members (or fewer if each person eats only a small slice), emphasizing that developers usually need larger portions to stay productive.

It then discusses why Amazon and other organizations advocate limiting team size to the "two‑pizza" level, aligning this with the well‑known "7±2" rule for cross‑functional teams, and highlighting the benefits of small, self‑organizing groups.

The piece stresses that teams should not be treated as interchangeable resources; instead, members are encouraged to exercise self‑leadership and leverage their individual talents, fostering a culture where each contributor can make a significant impact.

When a company or project scales, large teams are split into smaller feature teams, each owning a specific product area and driving rapid business progress through an empowered, collaborative culture.

Drawing from personal experience with both large and small project teams, the author concludes that small teams have lower communication costs, simpler internal structures, and stronger cohesion, whereas large teams without self‑management mechanisms rely on external pressure to meet milestones, which hampers sustainable development and long‑term vision.