Team of Teams Model
Scale the trust and adaptability of small teams across an entire organization by networking teams together
The Team of Teams model replaces rigid hierarchical command with a networked structure where the relationships between constituent teams mirror the trust and common purpose found within a single small team. Rather than trying to build one massive team (impossible beyond roughly 150 people), the model connects existing teams through liaison officers, shared information, and common purpose. Each team maintains its internal cohesion while developing trust-based relationships with every other team in the network. The result is an organization that preserves the adaptability of small units while operating at enterprise scale.
- Every individual does not need to know every other individual; each team needs someone who knows someone on every other team
- The relationships between teams must resemble the trust and purpose found between individuals on a single team
- Teams that traditionally resided in separate silos must become fused via trust and common purpose
- Liaison and embedding programs create the human connective tissue between teams
- Organizational adaptability matters more than individual team excellence when facing complex environments
- A command of teams is more flexible than a conventional command but still not adaptable enough for the twenty-first century
- The goal is not one massive team but a network of teams that can sense and respond as one organism
- Acknowledge the Limits of CommandRecognize that your existing command structure, no matter how capable its individual teams, cannot match a networked adversary or complex environment. A command of teams is still a hierarchy that routes decisions and information through bottlenecks. Map where decisions stall, where information gets trapped in silos, and where teams compete rather than cooperate.Pro tipThe first sign you need this transformation is when your teams are individually excellent but collectively slow. If your best operators are waiting on approvals or missing connections to adjacent teams, you have a command-of-teams problem.
- Establish Cross-Team Trust Through EmbeddingCreate a liaison and embedding program that places members of each team inside other teams for extended periods. These individuals become the human bridges that connect teams with trust rather than bureaucracy. When operators sit with intelligence analysts and analysts deploy with operators, both sides develop the personal relationships and mutual understanding that replace tribal rivalry with shared purpose.Pro tipEmbedding is initially resisted by both sides. Operators see analysts as outsiders; analysts feel exposed. Mandate it long enough for results to speak for themselves, then it becomes self-sustaining as teams compete to participate.WarningDo not treat embedding as a short rotation or courtesy visit. The embedded person must stay long enough to earn trust and contribute meaningfully.
- Build Common Purpose Across TeamsReplace the tribal identity of individual teams with a shared strategic narrative. Every team must understand not just their own tactical mission but how their work connects to the larger fight. When a SEAL team in Mosul understands how their raid connects to an intelligence thread in Tikrit and a diplomatic effort in Baghdad, they make better decisions and coordinate naturally.WarningCommon purpose cannot be mandated through a memo. It must be demonstrated daily through shared information, shared risk, and shared credit.
- Create Gravitational Pull Through ResultsShare information and resources generously, even with partner organizations you cannot directly command. When external agencies see that participating in your network produces better intelligence, faster results, and greater impact, they will voluntarily increase their commitment. Success becomes its own recruiting tool.Pro tipStart by giving more than you receive. The Task Force shared top-secret intelligence freely with partner agencies, which initially felt risky but created a gravitational pull as agencies saw the value of participation.
- Sustain the Network Through Rhythm and MaintenanceThe network requires constant tending. Establish a battle rhythm of regular forums, information-sharing practices, and leadership touchpoints that keep the connections alive. Without active maintenance, the natural centrifugal forces of bureaucracy and tribalism will pull teams back into silos.WarningThe network is never finished. The moment you stop investing in cross-team relationships, entropy begins.
McChrystal's Task Force in Iraq transformed from a traditional command of elite teams into a networked team of teams by embedding liaison officers across units, sharing intelligence freely, and building a daily battle rhythm through the O&I forum. SEALs, Rangers, Army Special Forces, CIA, NSA, and FBI personnel were fused into an integrated network.
NASA faced a similar challenge integrating hundreds of contractors and agencies toward the moon landing. No single entity could understand the entire system. NASA created systems engineering roles and shared information across organizational boundaries, ensuring that a change in one subsystem was understood by all affected parties.
When McChrystal took command of Joint Special Operations in Iraq in 2003, he led the most elite military force in history but was losing to Al Qaeda in Iraq. AQI was a decentralized network that moved faster than his command-of-teams hierarchy could respond. Despite having superior resources, technology, and training, the Task Force could only execute about ten raids per month. McChrystal realized that defeating a network required becoming a network. The resulting transformation turned the Task Force into a team of teams that eventually executed three hundred raids per month with minimal increases in personnel.