Team of Teams

In 2003, General Stanley McChrystal took command of the Joint Special Operations Command in Iraq and discovered that the most capable military force in history was losing to an enemy it should have destroyed in weeks. Al-Qaeda in Iraq was not better trained, better equipped, or better funded. It was faster. A decentralised network of semi-autonomous cells could observe a situation, decide on a response, and act before McChrystal's hierarchical command structure could process the intelligence, route it through approval chains, and issue orders. The problem was not competence. It was architecture. A hierarchy optimised for efficiency was being outrun by a network optimised for adaptability.

McChrystal's solution — documented in his 2015 book Team of Teams — was to transform his 7,000-person task force from a traditional command hierarchy into a network of small, autonomous teams connected by shared information and mutual trust. The unit of performance was still the small team. Special operations had always known that a tight-knit squad of twelve operators, bonded by shared purpose and extreme interdependence, could accomplish what a conventional battalion could not. The insight was that this team-level cohesion could be extended across teams — not by merging them into a single large unit (which would destroy the trust and speed that made small teams effective) but by connecting them into a network where every team understood the broader context well enough to act without waiting for orders from above.

McChrystal called the two enabling conditions "shared consciousness" and "empowered execution." Shared consciousness meant radical transparency: every piece of intelligence was shared across the entire task force through a daily Operations & Intelligence briefing that connected 7,000 people across multiple time zones. The briefing was not a status update. It was a mechanism for ensuring that every team had the context required to make autonomous decisions that aligned with the broader mission. Empowered execution meant pushing decision authority to the lowest competent level — letting the team on the ground act on the intelligence they received without routing every decision through the command chain. The combination produced a task force that could operate at the speed of a network while maintaining the coherence of a hierarchy.

The connecting tissue between teams was deliberately engineered. McChrystal embedded liaison officers — members of one team physically placed inside another — to create trust across team boundaries. The liaisons were not coordinators. They were trust bridges: people who understood both teams well enough to translate context, anticipate needs, and resolve conflicts before they escalated. The technique worked because trust, McChrystal observed, does not scale through hierarchy. It scales through relationships. A thousand people cannot all trust each other directly. But if each team trusts the liaison from the adjacent team, and each liaison trusts both their teams, the network achieves functional trust at a scale that no hierarchy can match.

The model translates to business with striking precision. Spotify's squad model — autonomous teams of six to twelve people, each responsible for a specific product area, connected through "chapters" (discipline-based guilds) and "tribes" (collections of related squads) — is a commercial implementation of the team-of-teams architecture. Amazon's two-pizza teams, mandated by Jeff Bezos, are autonomous units connected not through liaison officers but through well-defined APIs: each team owns a service, exposes an interface, and communicates with other teams only through that interface. The most radical implementation is Haier's "rendanheyi" model, created by CEO Zhang Ruimin: the Chinese appliance manufacturer reorganised its 80,000 employees into over 4,000 microenterprises, each operating as an autonomous business unit with its own P&L, connected to each other and to external partners through a platform that replaces hierarchy with market mechanisms.

What unites these implementations is the structural insight that sits at the core of McChrystal's framework: the optimal unit of execution is the small team, and the optimal architecture for connecting small teams is a network, not a hierarchy. Hierarchies excel at efficiency — routing predictable work through standardised processes. Networks excel at adaptability — responding to novel situations through distributed decision-making. In environments where the rate of change exceeds the hierarchy's processing speed — modern warfare, software development, consumer markets — the network wins. The team-of-teams model is how you build an organisation that captures the speed and trust of small teams at the scale of an enterprise.