Two-Pizza Teams
Teams small enough to be fed by two pizzas.
"If you can't feed it, you can't run it."
What is Two-Pizza Teams? Teams small enough to be fed by two pizzas. Operating cadence and team design.
Amazon's org design principle.
Operating cadence and team design.
Audit team sizes quarterly. Split when they balloon.
Use the model. Pick the move.
Teams small enough to be fed by two pizzas. You've just seen this: Amazon's org design principle. Which lever does the model recommend?
Pick a lever. There are no neutral ones — every incentive funds a behavior somewhere.
Pick a reaction to Two-Pizza Teams
One tap. We'll point you at the most useful next surface based on how this hits.
The full taxonomy entry
Every concept in the Atlas uses the same structure — so Two-Pizza Teams can be compared, recombined, and cited like an element on a periodic table.
- Business
- Leadership
- Government
- Healthcare
- Education
- Sales
- Marketing
- AI
- Negotiation
- Media
- Public Policy
- Relationships
- Where in our org would Two-Pizza Teams most often show up unnoticed?
- Which metric, ritual, or contract clause quietly rewards Two-Pizza Teams?
- If we removed every payoff for Two-Pizza Teams, what behavior would replace it?
- Who benefits when Two-Pizza Teams persists — and who pays the cost?
- People defend the status quo using the language of two-pizza teams.
- Decisions cluster around the easiest narrative rather than the strongest evidence.
- New data changes the slide deck but not the decision.
- Anyone naming the pattern is treated as the problem.
Every Atlas entry is a node in a knowledge graph. See the related rail below to follow the connections.
See Two-Pizza Teams through 2 lenses
Each layer of the Incentives OS reframes this concept with its own thinkers, vocabulary, and diagnostic question.
Do you actually know Two-Pizza Teams?
Three quick questions. Result is saved into your review streak — come back when the term is due to lock it in.
Which best describes Two-Pizza Teams?
Worked example, counter-example & concept map
On-demand AI analysis grounded in the Lab's research. Cached on your device after first run.
When you encounter Two-Pizza Teams, your prefrontal cortex has to do extra work to override the automatic response — and that override budget is finite.
Executive control, planning, impulse override, working memory, System 2. First thing to go offline under stress, fatigue, or low blood sugar. Why your 4pm decisions are worse than your 9am ones.
See Prefrontal in the Brain Atlas →Picked for you, from the Atlas
Ranked by shared learning paths, overlapping chips, and what you've saved.
The minimum energy needed to start a reaction; same idea for starting habits or initiatives.
Combining substances to create a new material stronger than its parts.
A single constraint limits the throughput of an entire system.
A system's throughput is constrained by its single slowest step.
Small visible disorders signal that bigger ones will be tolerated.
Adding manpower to a late software project makes it later.
Send the card, not just the link
A pre-rendered social card with the title, eyebrow, and URL. Copy the link, post it anywhere, or download the SVG for slides.
More definitions to follow
Every term in the Atlas connects to a dozen others. Pick any of these and see where it takes you.
Saying or writing the idea back to yourself in your own words to surface gaps before they're public.
Default identity shift: you read, watch, and listen as a future teacher, not a passive consumer.
Inattention or forgetfulness caused by low attention, hyperfocus, or distraction.
Tversky & Kahneman's classic: identical outcomes flip from 'risk averse' to 'risk seeking' when framed as lives saved vs. lives lost.
High-velocity quotas for enumerators turn data collection into fiction-writing.
Because there's no sharp line, no distinction exists.
Two ways of thinking, both real, both useful, often mis-deployed.
Anticipated harm narrows attention and accelerates action.
A mental shortcut that substitutes a hard question with an easier one.
How much delay the user experience tolerates.
Value grows with the number of users.
Agents act in their own interest, not the principal's.