Team of Teams

The case is an argument from participant experience

Team of Teams was published by Portfolio in 2015 and credits Stanley McChrystal, Tantum Collins, David Silverman, and Chris Fussell. Its central case comes from McChrystal's command of the U.S. special-operations task force in Iraq, so the work is both a management argument and a senior participant's retrospective.¹

The authors describe highly capable units whose compartmentalized hierarchy could not act on information as quickly as al-Qaeda in Iraq's network. They say the task force responded by widening information exchange and moving more decisions toward operational teams, naming the two requirements shared consciousness and empowered execution.¹² The design proposition is relational: local authority without common context can fragment, while common context without authority can produce informed waiting.

Simon Reese's journal review calls the book a practitioner illustration of organizational learning and notes that it does not offer the detailed theoretical references or conceptual development typical of that literature.³ The mechanisms are unusually concrete; the causal theory is not a controlled evaluation.

Complexity is a diagnosis, not a permission slip

The book distinguishes complicated systems, whose parts can remain predictable with sufficient expertise, from complex systems, whose interactions generate less predictable outcomes. It uses that contrast to argue that increasing planning precision cannot answer every kind of uncertainty and that an organization may instead need faster updating and adaptation.¹

That argument belongs beside strategy, competition, and adaptation and executive attention, information, and organizational sensing. Calling a problem complex does not by itself prove that forecasting is futile or that a network is the right response. Better measurement and engineering can make some uncertainties tractable; the label should sharpen an operating test, not excuse weak analysis or accountability.

Shared consciousness is an engineered information practice

The authors describe expanding the Operations and Intelligence briefing from a restricted update into a daily, distributed forum, sharing status, intelligence, and strategic context across units and partner agencies. They also describe embedding personnel and exchanging liaison officers so that cross-unit relationships could carry information and trust.¹²

Patrick Bury's peer-reviewed reassessment corroborates those mechanisms but changes their interpretation. He describes the joint interagency task force and the briefing as centralized management and integration tools that supported decentralized operational decisions. On that evidence, Task Force 714 became a hybrid of hierarchy and network, not a pure bottom-up network.⁴

The practical aim was not universal expertise. It was enough shared context for people to interpret local evidence and anticipate other teams' needs—a specific form of coordination, communication, and common understanding. Yet a common picture is still selected and governed: widening access among cleared participants is not the same as equal standing for everyone affected by the operation.⁴

Broader research supports caution in transfer. An integrative review defines a multiteam system as interdependent teams coordinating toward proximal and distal goals, then finds that coordination, leadership, and emergent states vary with organizational boundaries, distance, and goal type.⁵ A meta-analysis of 36 randomized laboratory or field experiments found that team development interventions improved shared mental models on average (g = 0.61, 95% CI [0.41, 0.82]), but rated the evidence low-certainty and reported a wide prediction interval (-0.66 to 1.89).⁶ Shared mental models are conceptually adjacent to shared consciousness, not a direct test of the book's practice or the Iraq case.

Empowered execution delegates decisions under purpose

McChrystal describes an “eyes on, hands off” posture: leaders remain engaged in the information system while allowing capable subordinates to act within a common intent. The book presents this as a shift in decision rights, not the disappearance of command; senior leaders still set purpose, construct the information environment, select personnel, allocate resources, and retain the power to intervene.¹

Bury's account reinforces that boundary. The Operations and Intelligence forum maintained central direction even as subordinate task forces gained tactical authority, and he characterizes the overall transformation as top-down innovation coupled with decentralized execution.⁴ This makes the work a useful companion to delegation, decentralization, and responsibility and Turn the Ship Around!. Authority, context, resources, and accountability have to move together; speed alone is not empowerment.

Operational tempo is not a complete outcome

In a 2015 essay promoting the framework, the four authors report that the task force moved from 15 to 300 operations per month over four years, with little increase in personnel or resources, and also claim a rising success rate and the degradation of AQI.² Richard Shultz's later professional-military evaluation uses a slightly different measure: 18 raids in August 2004 and 300 in August 2006, sustained into 2009. It reports task-force evidence that AQI networks were degraded, while acknowledging that precise attrition was difficult to estimate.⁷

Shultz does not attribute Iraq's wider decline in violence to the task force alone. He identifies the counterinsurgency strategy, the 30,000-troop surge, the Awakening movement, and Task Force 714 operations as contributors, and concludes that counterterrorism and counterinsurgency could not substitute for political reconciliation and reconstruction.⁷ Bury likewise warns against turning a tightly bounded counterterrorism mission into proof of a new, fully networked form of warfare.⁴ The evidence is strongest for an organizational transformation and higher operating tempo, weaker for isolating its contribution to strategic outcomes.

Mission and affected people belong inside the evaluation

Faster target cycles are a means, not a moral verdict. A 2006 Human Rights Watch investigation assembled interviews with U.S. military personnel, declassified memoranda, and sworn statements concerning Task Force 20/121/6-26/145 at Camp Nama and near Balad. It reported beatings, stress positions, sleep deprivation, extreme temperatures, threats, and other mistreatment of detainees.⁸ A Senate Armed Services Committee inquiry later concluded that detainee abuse occurred during Special Mission Unit task-force interrogations in Iraq in September 2003, traced aggressive techniques into task-force policies, and criticized task-force leadership and Central Command oversight.⁹

Those findings concern the wider special-operations campaign environment and precede much of the reorganization; they do not show that shared consciousness or delegated execution caused the abuse.¹⁸⁹ They do show why an appraisal cannot end with speed, information flow, or target disruption.

The available public accounts do not provide a task-force-specific civilian casualty series or a systematic record of Iraqi civilian and detainee testimony. That is an evidence gap, not evidence that no harm or testimony exists.¹⁰ The companion history of Joint Special Operations Command and the team-of-teams experiment keeps the institutional setting visible.

Transfer to civilian organizations needs a new authority and consequence map. A company does not gain permission for permanent urgency, intrusive monitoring, or broad secrecy because leaders call its market complex. Empowered execution answers how people may act within a purpose; it does not decide whether affected people helped choose that purpose, can challenge it, or can refuse the work.

Relations and reading route

Organizational intelligence is a conceptual-lens relation: it asks how information, judgment, coordination, and adaptation become a system rather than isolated team virtues. Benefit for all life is an ethical-evaluation relation: it tests the framework against the standing, voice, and consequences of everyone affected, not only mission performance. These relations are editorial comparisons, not evidence of causal influence or institutional descent.

The reading dependencies are also comparisons. On War: Selected Books supplies mission-and-command context; The Fifth Discipline develops systems and shared-model questions; Turn the Ship Around! examines distributed authority within a single command; and The Command of the Ocean offers a historical contrast in coordination across distance. None is a documented source of the framework unless a cited history establishes that lineage.

A disciplined use test

Separate the participant history, the complexity argument, and the design recommendations. Then ask:

• What decision moved, from whom to whom, and under whose purpose?
• Which information became shareable, who remained outside the forum, and who could correct the common picture?
• Did authority move with competence, resources, stopping power, and accountability?
• Which outcomes improved: tempo, tactical accuracy, strategic conditions, worker experience, or effects on people outside the organization?
• What evidence would show that the practice failed or caused unacceptable harm?

The durable lesson is not that hierarchy should become a network. It is that local judgment and shared context must be designed together—and evaluated against the mission's full consequences.