Andrew Luxem

2-Pizza Team: Create a small team with a clear outcome and manageable dependencies

A cross-functional team is formed around a topic, but ownership, decision rights, interfaces, and the outcome remain distributed. This brief defines the output, failure check, and adoption test.

Andrew Luxem
Andrew Luxem
CRM, Lifecycle & AI Strategy

2 min read
The argument
A cross-functional team is formed around a topic, but ownership, decision rights, interfaces, and the outcome remain distributed.
The skill should create a small team with a clear outcome and manageable dependencies.
Run the charter for six weeks. Track decision latency, external handoffs, unresolved dependencies, and movement against the outcome.

A cross-functional team is formed around a topic, but ownership, decision rights, interfaces, and the outcome remain distributed.

The useful response is a mechanism that can create a small team with a clear outcome and manageable dependencies.

What the skill produces

The 2-Pizza Team skill turns supplied context into a small-team charter with purpose, owner, members, decision rights, interfaces, measures, and cadence. It should label missing evidence rather than inventing it. The free skill packages this mechanism for explicit use. It does not fetch remote instructions, and the accountable human remains responsible for facts and decisions.

Run the mechanism

  1. Define one durable outcome and accountable owner.
  2. Select the minimum capabilities needed to own the work.
  3. Document dependencies, interfaces, measures, and review cadence.

The responsible owner reviews the artifact against the source evidence and applicable policy before it is used. Unknowns remain visible, especially when they affect people, customers, or a consequential decision.

Failure check

Team size is not the mechanism. A small team still fails when authority and dependencies remain outside the charter.

Attribution boundary

The two-pizza-team idea is associated with Amazon and should be attributed when used publicly.

Adoption test

Run the charter for six weeks. Track decision latency, external handoffs, unresolved dependencies, and movement against the outcome.

Keep the skill only if it improves consistency, decision quality, or reviewability against that baseline. Revise the mechanism when the same failure survives another cycle.

Infographic

A SMALL TEAM IS NOT AN OWNED TEAM infographic
Andrew Luxem
20 years building CRM and lifecycle programs at Amazon, Ancestry, and Stanley Black & Decker.