The Long Game Project · Flavours · The Swarm · TLDR
The Swarm
The Swarm operates through distributed action at scale.
Principles
- Push decisions to the team closest to the situation
- Simple, shared rules outperform complex central plans
- Cover more ground by running many small experiments simultaneously
Blind spots
- Accountability is diffuse - when everyone is responsible, no one is
- Strategic coherence can degrade into incoherent local optimisation
Red lines
- Will not centralise decision-making for efficiency at the cost of local responsiveness
- Will not create bottleneck approval processes that slow the edges
Switch to Normal for the full page, or Deep for the working.
How it works · Flavours · Independent
The Swarm
The Swarm operates through distributed action at scale. There is no single command centre - intelligence and decision-making are pushed to the edges. The Swarm covers enormous ground, adapts locally to conditions, and achieves coherence through shared simple rules rather than central direction. It is powerful in fast-moving, fragmented markets and vulnerable to opponents who can strike at its coordination mechanisms.
Decision principles
- 01
Push decisions to the team closest to the situation
- 02
Simple, shared rules outperform complex central plans
- 03
Cover more ground by running many small experiments simultaneously
- 04
Local adaptation is expected and encouraged - one size fits nobody
- 05
Coordination happens through shared information, not shared managers
- 06
If a node fails, the network adapts - no single point of failure
Blind spots
- Accountability is diffuse - when everyone is responsible, no one is
- Strategic coherence can degrade into incoherent local optimisation
- Quality control is hard when every node operates differently
- Vulnerable to coordination failures in moments that require unified response
Red lines
- Will not centralise decision-making for efficiency at the cost of local responsiveness
- Will not create bottleneck approval processes that slow the edges
- Will not sacrifice network breadth for depth in a single area
- Will not build systems that require a single person to function
Is this you? The free diagnostic matches your organisation to its nearest Flavour in about 18 minutes. To watch the Flavours answer the same pressure side by side, read the scenario vignettes.
The annex · Deep
How this Flavour reads the others, and which Flavours it clashes with.
Relationship postures
Uncertainty
Comfortable. Uncertainty is distributed across many nodes - no single bet is existential.
Conflict
Moderate. The Swarm engages conflict locally but avoids system-wide confrontation.
Process
Allergic. Central process contradicts the Swarm's distributed nature. Only the simplest shared rules.
Success
Moderate. Success spreads through the network as a pattern to replicate, but doesn't transform the system.
Failure
Generative. Failed nodes provide information. The network learns from local failures.
Outsiders
Permeable. The Swarm absorbs external talent, partners, and ideas readily.
Time
Somewhat reactive. The Swarm responds to the present across many fronts. Anticipation requires coordination it resists.
Identity
Fluid. The Swarm's identity is emergent - it is what its nodes collectively do, which changes constantly.
Notable relationships
The Swarm tends to align with The Pirate Ship and The Chameleon. It clashes hardest with The Fortress and The Cathedral. The full pairwise read is part of the product: ally, adversary, productive tension or indifferent, for every pair at the table. It shows up in a wargame when these Flavours share a room.