---
id: "concept-one-pizza-teams"
type: "concept"
source_timestamps: ["00:20:18", "00:21:21"]
tags: ["organizational-design", "agile", "team-scaling"]
related: ["claim-team-size-reduction", "quote-one-pizza-teams", "entity-rajiv-rajan", "entity-org-atlassian"]
sources: ["s05-claude-design-30min"]
sourceVaultSlug: "s05-claude-design-30min"
originDay: 5
---
# The One-Pizza Team

## Definition
The evolution of Amazon's 'two-pizza team' concept, where AI leverage allows a single person or micro-team to execute full product lifecycles previously requiring 6–10 people.

## From Two Pizzas to One
The **two-pizza team** is a famous Amazon (Bezos-era) heuristic: a product team should be small enough to be fed by two pizzas — typically 6–10 people, encompassing PM, Design, Engineering, and QA. This size was historically necessary because of the **coordination overhead** required to translate specs → mockups → code (see [[concept-the-translation-layer]]).

With AI agents that can handle end-to-end generation, that coordination tax collapses:
- A single PM can generate a working prototype (see [[framework-new-pm-workflow]]).
- A single engineer can focus purely on scale, not UI translation (see [[claim-engineering-focus-shift]]).

The required headcount to ship a feature drops dramatically.

## Field Signals
- An engineering leader at an agricultural company is paraphrased: *'two-pizza teams are turning into one-pizza teams.'* See [[quote-one-pizza-teams]].
- [[entity-rajiv-rajan]], CTO of [[entity-org-atlassian]], notes some teams are now writing *zero lines of code*, acting purely as orchestrators of agents.

## Caveat
The enrichment overlay flags 'bus-factor' risk: small teams + agent unreliability (15–30% UI generation hallucination rates in some studies) can demand *more* oversight, not less. Coordination tax drops but doesn't vanish for production-scale apps.