Two-Pizza Teams is teams small enough to be fed by two pizzas. It sits in the Cognition dimension (COG) of the Human Behavior Taxonomy™ as element HBT-COG-0682, within the Systems family. The core principle: teams small enough to be fed by two pizzas. In incentive terms, it matters because it changes the payoff people perceive before they choose — which means it can be designed for, or exploited.
Scientific Definition
Teams small enough to be fed by two pizzas.
Plain-English Definition
Teams small enough to be fed by two pizzas.
Feynman Explanation
If you can't feed it, you can't run it.
Core Principle
Teams small enough to be fed by two pizzas.
Mechanisms
Pending editorial review.
Teams small enough to be fed by two pizzas.
Pending editorial review.
Pending editorial review.
Pending editorial review.
Pending editorial review.
Operating cadence and team design.
Inputs (Triggers)
Pending editorial review.
Outputs (Behaviors)
Pending editorial review.
Behavioral Signature
If you can't feed it, you can't run it.
Examples
- Amazon's org design principle.
- Operating cadence and team design.
Pending editorial review.
Original analysis from The Incentives Lab — how this element behaves inside real payoff structures.
Why this element matters to incentive design
This element is common enough to feel like human nature and specific enough to be engineered around. The mechanism underneath it is straightforward: teams small enough to be fed by two pizzas. You can recognize it in the field by its signature: if you can't feed it, you can't run it. Every element in the Cognition dimension changes the perceived payoff of an action before the action happens, which is exactly where incentive design has leverage.
How it gets exploited
Left undesigned, operating cadence and team design. It is amplified whenever operating cadence and team design. Inside organizations that shows up as operating cadence and team design. The pattern is the same one Goodhart's Law describes: the measurable proxy attracts the effort, and the purpose behind it quietly loses funding.
How the Lab designs around it
The redesign move is to audit team sizes quarterly. Split when they balloon. Treat it as infrastructure. Once you can see it in your own system, most of the argument about culture resolves itself.
Famous Experiments
Pending editorial review.
Design Principles
- Audit team sizes quarterly. Split when they balloon.
Measurement Approaches
Pending editorial review.
Evidence
Pending editorial review.
Pending editorial review.
The Perverse Incentive Lens™
How this behavior is exploited — and how to redesign around it.
- Audit team sizes quarterly. Split when they balloon.
Pending editorial review.
Pending editorial review.
Interactive Mini Network
Click any neighbor to re-center the graph and follow the threads of connection.
Knowledge Graph Neighbors
Auto-linked to the rest of the Human Behavior Taxonomy by family, domain, dimension, and shared keywords.
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.
Adding people to a late project makes it later.
A substance that speeds up a reaction without being consumed.
Nonlinear systems are highly sensitive to initial conditions.
Inputs combine under conditions to produce new outputs — sometimes irreversibly.
Software architecture mirrors org structure.
Working together has a cost that scales with the number of people.
The threshold at which a system becomes self-sustaining.
Where Two-Pizza Teams is cited in the corpus
Essays, field guides, and diagnostics from The Incentives Lab that apply this element.
- EssayGoodhart's Law in the Real World
How measurable proxies capture judgment.
- EssayThe Perverse Incentives Hiding in Your KPIs
Cognitive shortcuts turned into scorecards.
- EssayAI Agents Inherit Your Incentives
How this element propagates into automated systems.
- EssayThe Comp Plan Is the Strategy
Where this element meets compensation design.
- CourseIncentives 101
The free ten-part primer on reading a payoff structure.
- ReferenceThe incentive glossary
Definitions for every mental model, bias, and fallacy in the corpus.
- ReferenceThe Periodic Table of Human Behavior
The full 1,267-element map this page belongs to.
Questions about Two-Pizza Teams
- What is Two-Pizza Teams?
- Two-Pizza Teams is teams small enough to be fed by two pizzas. It sits in the Cognition dimension (COG) of the Human Behavior Taxonomy™ as element HBT-COG-0682, within the Systems family. The core principle: teams small enough to be fed by two pizzas. In incentive terms, it matters because it changes the payoff people perceive before they choose — which means it can be designed for, or exploited.
- What is an example of Two-Pizza Teams?
- Operating cadence and team design. The Incentives Lab catalogs everyday, organizational, and historical instances of this element on its Human Behavior Taxonomy™ page (HBT-COG-0682).
- How is Two-Pizza Teams exploited?
- Operating cadence and team design.
- How do you design around Two-Pizza Teams?
- Audit team sizes quarterly. Split when they balloon.
- Which behavioral dimension does Two-Pizza Teams belong to?
- Two-Pizza Teams is classified in the Cognition dimension (COG) of the Human Behavior Taxonomy™, family "Systems", class "Mental Model". Its permanent identifier is HBT-COG-0682 and its evidence grade is B.