← Patterns

Peloton Theory

Pattern · engineering-culture

Core Concept

Three properties of effective small teams, named after the cycling peloton — a tight pack that moves faster together than any individual rider could alone:

1. Presence — Everyone is engaged and accounted for. No passengers, no ghosts. Each person’s contribution is visible to the group.
2. Density — The team is tightly packed in terms of communication and shared context. Low distance between any two members. Information travels instantly.
3. Intensity — The pace is high and sustained. The group pushes each other forward through mutual accountability and shared momentum.

The metaphor works because in a cycling peloton, all three properties are physical: riders are present (in the pack), dense (inches apart), and intense (racing pace). Remove any one and the peloton breaks apart — stragglers fall off, gaps open, and the drafting advantage disappears.

For teams: remove presence and you get disengagement. Remove density and you get silos. Remove intensity and you get coasting.

Why It Matters to Me

This came from the Bloc era — a framework for what made our best teams work. It’s a useful diagnostic: when a team feels “off,” ask which of the three properties is missing. Usually it’s one specific property, not everything at once.

Where I’ve Seen It

• Bloc — originated here, where the best squads had all three properties naturally
• A later small in-house team — had presence and intensity but struggled with density due to platform silos (iOS vs Android engineering split across separate codebases)

Related Patterns

• Parallel Projects Sequential Tasks — density requires sequential focus; too many parallel workstreams dilute it
• Alignment on Check-Ins — daily check-ins are a density mechanism

Cross-References