Team of Teams Summary

In 2003, the most sophisticated military intelligence apparatus in the world was losing a war to a loosely organized network of fighters who had never attended military staff college, had no formal command hierarchy, and were making decisions faster than the most advanced special operations forces on the planet could respond to them. The problem was not resources. The US Joint Special Operations Command had more resources, better equipment, and more highly trained personnel than any adversary they had ever faced. The problem was structure. General Stanley McChrystal, who commanded that force, came to understand this in a way that produced one of the most significant organizational transformations in modern military history — and wrote about it in Team of Teams: New Rules of Engagement for a Complex World, published in 2015.

The enemy was Al-Qaeda in Iraq. The conventional military model — hierarchical, siloed, optimized for efficiency through specialization — was generating intelligence and tactical assessments at the pace of days and weeks when the adversary was making decisions at the pace of hours and minutes. Information flowed up through chains of command, was processed by central analysts, and flowed back down as orders that arrived after the tactical situation had already changed. The machine was technically superb and operationally too slow. The adversary, operating as a network of loosely connected cells with distributed decision-making authority, could identify opportunities and act on them faster than the hierarchical machine could even process that opportunities existed.

McChrystal’s solution — what he calls the “team of teams” model — was to restructure the command from a machine optimized for efficiency through specialized, independent units to an organism capable of adaptability through shared consciousness and distributed authority. The transformation required changes to information architecture, command philosophy, and the psychological contracts between teams that most organizations treat as fixed. The story of that transformation, and the organizational principles it illustrates, forms the content of this book. McChrystal’s case is military, but the management literature he draws on and the organizational principles he arrives at apply directly to any organization operating in a complex, rapidly changing environment — which, by 2015 when the book was published, described nearly every significant organization in the world.

What makes this book more than a military memoir is McChrystal’s systematic engagement with the management literature — Taylor, Drucker, complexity theory — that provides the theoretical framework for understanding why the organizational transformation he describes was necessary. He is not just describing what he did; he is explaining why the conventional model fails in complex environments and what it needs to become to succeed in them. That combination of rigorous case evidence and theoretical grounding makes this one of the most intellectually serious organizational management books of its decade.

Key Lessons from Team of Teams

1. The machine model of organization — hierarchical, siloed, specialized, optimized for efficiency — works well in complicated, predictable environments and fails in complex, rapidly changing environments where adaptability matters more than efficiency.
2. Complexity is distinct from complication: complicated systems are difficult but predictable; complex systems are fundamentally unpredictable because their components interact in ways that produce emergent behavior no analysis can fully anticipate.
3. The team of teams model replaces machine-like specialization with organism-like adaptability through two mechanisms: shared consciousness (everyone has access to the same operational information) and empowered execution (decision-making authority at the point of knowledge).
4. Trust, the foundation of team performance, can be extended between teams through deliberate embedding — temporary exchanges where team members spend time in other teams, building personal relationships that allow inter-team coordination to function at speed.
5. The O&I briefing is the specific mechanism McChrystal used to create shared consciousness: a daily all-hands meeting where all relevant information is shared across all units, eliminating information silos at the cost of communication overhead justified by the adaptability it enables.
6. The leader’s role in a team of teams shifts from decision-maker to context-setter and gardener — from making the important decisions to creating the conditions under which others can make good decisions quickly and in alignment with organizational intent.
7. Resilience, not efficiency, is the appropriate optimization target for organizations operating in volatile, uncertain, complex, and ambiguous environments.

The Takeaway on Team of Teams

Team of Teams is one of the most important management books of the last decade, systematically underread by the commercial organizations whose challenges it most directly addresses. McChrystal’s military case provides the kind of high-stakes, high-feedback evidence that management writing typically lacks, and the organizational principles he derives are grounded in that evidence rather than consulting practice or business school theory. The book’s limitation is that it underestimates the difficulty of implementing shared consciousness in organizations without military command authority, and it occasionally overgeneralizes the complexity challenge. But the framework — machine to organism, efficiency to resilience, command to context-setting — is the right framework for thinking about organizational design in complex environments, and this book makes the case for it more compellingly than anything else in the genre.

Machine vs. Organism: The Central Organizational Choice

McChrystal borrows the machine-organism distinction from organizational theory and applies it with the specificity that comes from actually managing a transformation between the two states. The machine metaphor describes an organization optimized for efficient execution of predictable tasks: specialized units that do specific things very well, clear interfaces between units, hierarchical decision-making that ensures consistency and accountability. Frederick Winslow Taylor’s scientific management is the machine model in its purest form, and it genuinely works for repeatable, well-understood operations in stable environments where what good output looks like can be defined in advance and maintained over time.

The organism metaphor describes an organization capable of adaptive response to novel challenges: units generalist enough to respond to unexpected demands, information flowing freely across boundaries rather than being filtered through hierarchical channels, decision-making authority residing with the person who has the most relevant knowledge regardless of hierarchical position. The organism is less efficient than the machine in stable conditions precisely because it maintains the redundancy and information-sharing overhead that enables adaptability. In volatile conditions, that overhead becomes the competitive advantage that allows the organism to respond to changes the machine cannot anticipate.

The JSOC transformation was from a highly efficient machine — specialized teams that were individually excellent but collectively slow — to a team of teams that sacrificed some individual unit efficiency to gain collective adaptability. The daily O&I briefing, which consumed significant time that units could have spent on their specific missions, was the primary operational cost. The benefit was that every unit had enough context about every other unit’s activities that they could act on opportunities without waiting for central coordination that would have arrived too late to be useful.

The machine-to-organism transition is not a one-time decision but an ongoing organizational practice. Organizations tend to drift back toward machine characteristics — hierarchical decision-making, information silos, efficiency metrics — because the machine model is familiar and its benefits are real and visible. Maintaining the team of teams model requires deliberate, sustained leadership attention to the practices that sustain it: the regular shared consciousness briefings, the cross-team relationship investments, the commander’s intent articulation, and the resistance to the centralization impulses that arise whenever performance pressure is high.

Complexity vs. Complication: Why Standard Management Tools Fail

The intellectual centerpiece of Team of Teams is the distinction between complicated and complex systems. A complicated system — an airplane engine, a supply chain, a software codebase — has many interacting parts and is difficult, but its behavior is predictable because the interactions follow understandable rules. Given enough analysis, the airplane engine can be fully understood and its behavior predicted with high accuracy. Expert engineers can take the system apart, understand each component, and reassemble it. Complexity, in this sense, is solvable through expertise and sufficient analysis time.

A complex system — an insurgency, an ecosystem, an economy, an organizational culture — is not just difficult. It is fundamentally unpredictable because the interactions between its components generate emergent behavior that cannot be predicted from knowledge of the individual components. The insurgency that McChrystal faced adapted to JSOC’s tactics faster than JSOC’s analysis cycles could track, because each JSOC action changed the context in which the insurgency operated, changing the optimal insurgency tactics, which changed the context for the next JSOC action in a continuous feedback loop that produced behavior no static analysis could anticipate.

This distinction has direct implications for organizational management. Most management tools — strategic planning, budgeting, performance metrics, organizational design — were developed for complicated environments and assume that the future is predictable enough that plans made today will still be relevant when executed. In complex environments, the future is not predictable, plans become obsolete faster than they can be implemented, and the organization’s most important capability is not efficient execution of correct plans but rapid adaptation to information that arrives after the plan was made. The machine was designed for complicated environments. Complex environments require the organism — which is why organizations that perform well in stable conditions frequently fail catastrophically when conditions become volatile, even though their capabilities have not declined.

Shared Consciousness: Information Architecture as Strategy

The most operationally concrete element of the team of teams model is shared consciousness — the condition in which all units have access to the same information about the overall situation, other units’ activities, and the commander’s intent. McChrystal created shared consciousness primarily through the O&I briefing: a daily televised meeting that included every unit in the command, where intelligence analysts presented current situational awareness, unit commanders described their recent activities and planned operations, and the commander provided context about overarching priorities. The briefing was resisted initially by units that saw it as time taken from their specific missions, but over time became valued rather than merely required as the cross-unit coordination benefits accumulated.

The O&I briefing served a secondary function equally important to the information-sharing function: it created a shared narrative about the operation and the organization’s identity that gave everyone in the command a sense of being part of a unified effort rather than isolated specialists. This narrative function — the “why” beyond the “what” of operational status updates — is what allowed operators who had never met to trust each other’s intentions when cross-unit coordination was required. You can share information with people you do not trust and still not benefit from the sharing because the information is discounted or hoarded.

Trust is what converts information sharing into actual coordination, and shared narrative is one of the most powerful trust-building mechanisms available at organizational scale.

For commercial organizations, the O&I briefing principle translates to any mechanism that makes information broadly available across organizational boundaries rather than siloed within functional units. The specific mechanism matters less than the consistent practice of making information flow across the boundaries that organizational structure typically maintains as barriers. A weekly all-hands with genuine information sharing — teams sharing what they are learning and doing — is the most direct commercial equivalent, but shared dashboards, cross-functional project reviews, and deliberate knowledge-sharing practices all contribute to the shared consciousness infrastructure.

Empowered Execution: Authority at the Speed of Relevance

Shared consciousness is one half of the team of teams model. Empowered execution is the other. Sharing information without distributing authority produces an organization where everyone knows what is happening but decisions still bottleneck at the top of the hierarchy. The power of shared consciousness comes from combining it with the authority to act on that shared knowledge at the level where the relevant information is most current and the response can be most rapid.

McChrystal’s formulation of empowered execution draws on the German military concept of Auftragstaktik — mission tactics — in which senior commanders specify the intent and objective but delegate the specific method of achieving it to unit commanders closest to the situation. The field commander who understands the commander’s intent can respond to unexpected developments without waiting for approval of each specific tactical decision. This is not autonomy without alignment — it is aligned autonomy, enabled by the clarity of intent that makes independent decision-making predictably consistent with organizational direction.

The critical insight is that empowered execution only works in combination with shared consciousness. The unit commander who has authority but lacks situational awareness will make locally optimal decisions that are globally disastrous. Shared consciousness first, empowered execution second. The order is not reversible. This sequence is also what distinguishes genuine empowerment from the more common organizational practice of giving people authority without giving them the information and context needed to exercise it well — which produces not empowerment but delegation of blame for the inevitable poor decisions that result from inadequate context.

The Gardener Leader: When Command Means Enabling

McChrystal describes the transformation of his own leadership role with unusual honesty. As the commander of a conventional hierarchical force, his value was cognitive: he processed information, made decisions, transmitted orders. His intelligence, experience, and judgment were the bottleneck through which all major decisions passed. In the team of teams model, his role shifted to what he calls the “gardener” — creating the conditions in which the rest of the organization could grow and perform, rather than being the primary performer himself.

Concretely, this meant spending a substantial part of each day on the O&I briefing and other shared consciousness activities that a purely operational focus would have eliminated. It meant articulating and re-articulating the commander’s intent in terms clear enough that subordinates could make aligned decisions without requesting guidance. The gardener-leader is less visibly central than the command-leader. Their contribution shows up in the organization’s collective performance rather than in identifiable individual decisions — a form of leadership contribution that is both more difficult to perform and less immediately recognized than the decisive command decision that everyone in the room can point to.

McChrystal acknowledges the psychological difficulty of this transition explicitly and honestly, describing his own discomfort with a role where his individual contribution was less visible. This honesty makes his account more useful than typical leadership transformation narratives that describe the new model as straightforwardly more satisfying without acknowledging what the leader actually loses in making the transition. Leaders who are considering this shift should know that it feels like a demotion before it feels like a promotion, and that the discomfort is the evidence that it is real rather than nominal.

What Team of Teams Gets Right

The complexity versus complication distinction is the most important conceptual contribution and resolves a confusion that pervades organizational management thinking. The insight that management tools developed for complicated systems do not work in complex systems explains large-organization performance failures that conventional management analysis consistently fails to account for. The large organization with excellent strategy and talented people that nevertheless fails to respond to competitive disruption is not experiencing a strategy or talent failure. It is experiencing a structural failure: the machine that worked brilliantly in a stable environment has become a liability in a volatile one.

The embedding mechanism for building inter-team trust is also concrete and immediately applicable. Organizations that implement systematic rotation programs, joint project assignments, and deliberate cross-team exposure consistently produce better information sharing than organizations that mandate collaboration without addressing the relationship foundation. The specific mechanism of embedding — having someone actually work alongside another team, not just meet with them — is more effective than any formal coordination process at the same cost, because it builds the personal trust that makes information sharing genuine rather than merely procedural.

What Team of Teams Gets Wrong

The book underestimates the difficulty of creating genuine shared consciousness in commercial organizations where command authority does not exist. McChrystal could mandate the O&I briefing. Commercial leaders can rarely mandate equivalent information-sharing mechanisms without generating the kind of resistance that undermines the sharing the mechanism is intended to produce. Without mandate, information sharing across organizational boundaries tends to revert to the siloed default because sharing information has real costs while the benefits are diffuse and accrue to the organization rather than to the sharing unit.

The book also overgeneralizes the complexity challenge. Not all commercial environments are genuinely complex in McChrystal’s sense — many organizations operate in environments that are complicated rather than complex, technically demanding but fundamentally predictable. For those organizations, the machine model’s efficiency advantages remain real and the team of teams model’s overhead costs are not justified by the adaptability benefits. Careful diagnosis of your specific environment type should precede any decision to invest in the team of teams transformation.

The Team of Teams Protocol

1. Diagnose your environment honestly: is adaptability or efficiency the binding constraint on your performance? If adaptability is the constraint, the team of teams investment is justified and overdue.
2. Map your information silos: which teams or functions have information that other teams need but do not currently access? Quantify the cost of these gaps in delayed decisions and missed opportunities.
3. Implement a regular all-hands information sharing session. Make it genuinely informational — teams sharing what they are learning and doing — not a management communications exercise.
4. Build inter-team trust through embedding: create structured opportunities for team members to spend time in other teams. Even a single day embedded in another team builds more trust than a dozen cross-functional meetings.
5. Clarify your commander’s intent. State the organizational goals, priorities, and values clearly enough that the people you are empowering could make decisions you would endorse without consulting you first.
6. Push decision authority to the level where the relevant knowledge resides. Identify decisions currently requiring your approval where someone else has better information, and explicitly delegate them with clear intent and accountability.
7. Track the leading indicators of team of teams success: frequency of cross-unit actions without central coordination, decision speed on novel challenges, inter-team knowledge application in your organization’s actual work.

Books Similar to Team of Teams

David Marquet’s Turn the Ship Around! covers complementary territory from a smaller-scale command perspective with more emphasis on the specific linguistic and authority mechanisms for implementing distributed decision-making. Frederic Laloux’s Reinventing Organizations extends the team of teams logic to full organizational redesign with extensive case studies of organizations implementing distributed authority at the whole-enterprise level. Nassim Taleb’s Antifragile is the philosophical companion, analyzing why systems that benefit from volatility outperform systems optimized for stability — the intellectual foundation for the resilience-over-efficiency argument. Patrick Lencioni’s The Five Dysfunctions of a Team addresses the team-level trust that must precede the team-of-teams scaling that McChrystal describes.

Who Should Read Team of Teams

Essential for leaders of organizations in rapidly changing environments finding that their hierarchical structures are too slow for competitive and environmental change. Particularly relevant for technology companies, professional services firms, healthcare organizations, and any organization where adaptability is the primary competitive advantage. Less relevant for organizations in genuinely stable, highly regulated environments where operational efficiency remains the dominant value driver. For anyone who has felt the frustration of watching an organization fail to respond to change despite having highly capable people, this book provides the clearest diagnosis of the structural root cause.

Integration

The most immediately applicable insight is the shared consciousness audit. Before attempting structural change, spend a week mapping the information flows in your organization: who knows what, who needs to know what, and where the critical gaps are. The map reveals specific silos limiting adaptability more precisely than any organizational survey. Design targeted, low-overhead mechanisms to close the highest-impact gaps first. The structural changes follow from that diagnostic — they are not the starting point, and attempting them without the diagnostic produces generic interventions that address the wrong gaps.

“The temptation to lead as a chess master, controlling each move of the organization, must give way to an approach as a gardener, enabling rather than directing.” — Stanley McChrystal

FAQ

How does a commercial organization create the equivalent of the O&I briefing? Match the format and frequency to the pace of change in your environment. In fast-moving environments, a daily thirty-minute all-hands where each team shares current status and recent learnings may be appropriate. In slower-moving environments, weekly suffices. The key design principle is genuine information sharing — teams sharing what they are learning and doing — not management communications. Building the habit requires demonstrating its value repeatedly until the reciprocal benefits become self-evident.

Won’t empowered execution produce inconsistent decisions? It produces more diverse decisions than centralized decision-making, which is different from inconsistent in the problematic sense. Diverse decisions made by people with better local information are often better aligned with actual conditions than consistent decisions made centrally with staler information. The goal of shared consciousness is to ensure that the diversity of decentralized decisions is aligned with organizational intent — not that every decision is identical to what a central authority would have decided.

What is the biggest mistake organizations make when implementing this model? Implementing structural elements — information sharing mechanisms, authority delegation protocols — without the cultural prerequisites of trust and clarity. The O&I briefing will not produce shared consciousness in an organization where teams do not trust each other’s information or intentions. Empowered execution will not produce aligned decisions where the commander’s intent is not genuinely clear and shared. Structure follows culture. The investment in trust-building and intent clarification must precede the structural changes.

How long does the transformation typically take? McChrystal describes the JSOC transformation as taking approximately eighteen months from the decision to change the model to the point where the new model was functioning reliably. Commercial organizations vary widely, but eighteen to thirty-six months is a reasonable expectation for an organization seriously committed to the transformation. The early months produce resistance and the appearance of reduced efficiency as the information-sharing overhead is absorbed but the adaptability benefits have not yet accumulated. Sustaining commitment through this period requires the leading indicator metrics that show the transformation is on track even before the lagging performance metrics respond.

McChrystal’s solution — what he calls the “team of teams” model — was to restructure the command from a machine optimized for efficiency through specialized, independent units to an organism capable of adaptability through shared consciousness and distributed authority. The transformation required changes to information architecture, command philosophy, and the psychological contracts between teams that most organizations treat as fixed. The story of that transformation, and the organizational principles it illustrates, forms the content of this book. McChrystal’s case is military, but the management literature he draws on and the organizational principles he arrives at apply directly to any organization operating in a complex, rapidly changing environment — which, by 2015 when the book was published, described nearly every significant organization in the world.

Key Lessons from Team of Teams

1. The machine model of organization — hierarchical, siloed, specialized, optimized for efficiency — works well in complicated, predictable environments and fails in complex, rapidly changing environments where adaptability matters more than efficiency.
2. The team of teams model replaces machine-like specialization with organism-like adaptability through two mechanisms: shared consciousness (everyone has access to the same operational information) and empowered execution (decision-making authority pushed to the person closest to the situation).
3. Traditional management creates effective silos — highly efficient units that optimize for their own sub-objectives — and these silos become organizational liabilities in complex environments where coordination between units determines overall performance.
4. Trust, the foundation of team performance, can be extended between teams through deliberate embedding — temporary exchanges where team members spend time in other teams, building the personal relationships that allow inter-team trust to function at speed.
5. The O&I briefing (Operations and Intelligence) is the specific mechanism McChrystal used to create shared consciousness: a daily all-hands meeting where all relevant information is shared across all units, eliminating information silos at the cost of communication overhead that is justified by the adaptability it enables.
6. The leader’s role in a team of teams shifts from decision-maker to context-setter — from making the important decisions to creating the conditions under which others can make good decisions quickly and in alignment with organizational intent.
7. Resilience, not efficiency, is the appropriate optimization target for organizations operating in volatile, uncertain, complex, and ambiguous environments.

The Takeaway on Team of Teams

Team of Teams is one of the most important management books of the last decade, and one that is systematically underread by the commercial organizations whose challenges it most directly addresses. McChrystal’s military case provides the kind of high-stakes, high-feedback evidence that management writing typically lacks, and the organizational principles he derives from it are grounded in that evidence rather than in consulting practice or business school theory. The book’s limitation is that it is occasionally repetitive and sometimes underestimates the difficulty of implementing shared consciousness in organizations without the command authority that McChrystal had to mandate it. But the framework — machine to organism, efficiency to resilience, command to context-setting — is the right framework for thinking about organizational design in complex environments.

Machine vs. Organism: The Central Organizational Choice

McChrystal borrows the machine-organism distinction from organizational theory, but he applies it with the specificity that comes from actually managing the transformation. The machine metaphor describes an organization optimized for efficient execution of predictable tasks: specialized units that do specific things very well, clear interfaces between units, hierarchical decision-making that ensures consistency and accountability, and performance metrics that measure output against the defined specification. Frederick Winslow Taylor’s scientific management — the foundational theory of modern organizational design — is the machine model in its purest form, and it genuinely works for repeatable, well-understood operations in stable environments.

The organism metaphor describes an organization capable of adaptive response to novel challenges: units that are generalist enough to respond to unexpected demands, information that flows freely across boundaries, decision-making authority that resides with the person who has the most relevant knowledge regardless of hierarchical position, and performance metrics that measure adaptability and resilience rather than just output efficiency. The organism is less efficient than the machine in stable conditions precisely because it maintains the redundancy and information-sharing overhead that enables adaptability. In volatile conditions, that overhead is the competitive advantage.

The JSOC transformation McChrystal describes was from a highly efficient machine — specialized teams (SEAL Team 6, Delta Force, intelligence analysts in their own silo, support functions in theirs) that were individually excellent but collectively slow — to a team of teams that sacrificed some individual unit efficiency to gain collective adaptability. The daily O&I briefing, which consumed significant time that units could have spent on their specific missions, was the main operational cost. The benefit was that every unit had enough context about every other unit’s activities and the overall operational situation that they could act on opportunities without waiting for central coordination that would have arrived too late.

Complexity vs. Complication: Why the Old Tools Fail

The intellectual centerpiece of Team of Teams is the distinction between complicated and complex systems, which McChrystal uses to explain why the management tools that worked for twentieth-century organizations fail in twenty-first-century environments. A complicated system — an airplane engine, a supply chain, a software codebase — has many interacting parts and is difficult, but its behavior is predictable because the interactions follow understandable rules that can be mapped and modeled. Given enough analysis, the airplane engine can be fully understood and its behavior can be predicted with high accuracy. Complexity, in this sense, is solvable through expertise and analysis.

A complex system — an insurgency, an ecosystem, an economy, an organizational culture — is not just difficult. It is fundamentally unpredictable because the interactions between its components generate emergent behavior that cannot be predicted from knowledge of the individual components. The insurgency that McChrystal faced adapted to JSOC’s tactics faster than JSOC’s analysis cycles could track, because each JSOC action changed the context in which the insurgency operated, changing the optimal insurgency tactics, which changed the context for the next JSOC action in a continuous feedback loop that produced behavior no static analysis could anticipate. In complex systems, the analysis tools that work for complicated systems produce the illusion of understanding without its substance.

This distinction has direct implications for organizational management. Most management tools — strategic planning, budgeting, performance metrics, organizational design — were developed for complicated environments and assume that the future is predictable enough that plans made today will still be relevant when executed. In complex environments, the future is not predictable, plans become obsolete faster than they can be implemented, and the organization’s most important capability is not efficient execution of correct plans but rapid adaptation to information that arrives after the plan was made. The machine model was designed for complicated environments. Complex environments require the organism model — which is why organizations that are performing well in stable conditions frequently fail catastrophically when conditions become volatile, even though their capabilities have not declined.

Shared Consciousness: Information Architecture as Strategy

The most operationally concrete element of the team of teams model is shared consciousness — the condition in which all units have access to the same information about the overall situation, other units’ activities, and the commander’s intent. McChrystal created shared consciousness primarily through the O&I briefing: a daily televised meeting that included every unit in the command, where intelligence analysts presented current situational awareness, unit commanders described their recent activities and planned operations, and the commander provided context about overarching priorities and decisions.

The briefing was initially resisted by units that saw it as time they could have spent on their specific missions. The resistance was rational from each unit’s individual perspective: the time cost was immediate and certain, and the benefit (the ability to act on information from other units) was indirect and probabilistic. McChrystal’s response was to make the briefing non-optional and to consistently demonstrate the value of cross-unit information through cases where shared knowledge had enabled faster, better action. Over time the briefing became valued rather than merely required — which is the transition from compliance to genuine shared consciousness.

For commercial organizations, the O&I briefing principle translates to any mechanism that makes information broadly available across organizational boundaries rather than siloed within functional units. This might be a weekly all-hands with genuine information sharing rather than management messaging, a shared data environment where relevant metrics are accessible across teams, or a communication culture where units proactively share what they are learning rather than hoarding information as a form of organizational currency. The specific mechanism matters less than the consistent practice of making information flow across boundaries that organizational structure typically maintains as barriers.

Empowered Execution: Authority at the Point of Knowledge

Shared consciousness is one half of the team of teams model. Empowered execution is the other. Sharing information without distributing authority produces an organization in which everyone knows what is happening but decisions still bottleneck at the top of the hierarchy. The power of shared consciousness comes from combining it with the authority to act on that shared knowledge — at the level where the relevant information is most current and the response can be most rapid.

McChrystal’s formulation of empowered execution draws on the German military concept of Auftragstaktik — mission tactics — in which senior commanders specify the intent and objective but delegate the specific method of achieving it to the unit commanders who are closest to the situation. The field commander who understands the commander’s intent can respond to unexpected developments without waiting for approval of each specific tactical decision. The specific tactics can change as the situation changes; the intent remains constant. This is not autonomy without alignment — it is aligned autonomy, enabled by the clarity of intent that makes independent decision-making predictably consistent with organizational direction.

The critical prerequisite for empowered execution is shared consciousness. A unit commander who does not have accurate situational awareness of the broader context will make locally optimal decisions that are globally inconsistent with organizational intent. The two elements are mutually enabling: shared consciousness makes empowered execution safe by ensuring that the person with the authority has the contextual understanding to exercise it in alignment with the organization’s goals. Empowered execution makes shared consciousness valuable by ensuring that the information people are sharing is actually being used to make faster, better decisions rather than accumulating in databases that nobody acts on.

The Gardener Leader: What the Command Role Becomes

McChrystal describes the transformation of his own role with unusual honesty. As the commander of a conventional hierarchical force, his value was cognitive: he processed information from across the command, made decisions, and transmitted orders. His intelligence, experience, and judgment were the bottleneck through which all major decisions passed. This model maximized the impact of his individual capability while limiting the organization’s total capability to what he could personally process and decide.

In the team of teams model, his role shifted to what he calls the “gardener” — creating the conditions in which the rest of the organization could grow and perform, rather than being the primary performer himself. Concretely, this meant spending a substantial part of each day on the O&I briefing and other shared consciousness activities that a purely operational focus would have cut in favor of more “productive” uses of time. It meant articulating and re-articulating the commander’s intent in terms clear enough that subordinates could make aligned decisions without requesting guidance. It meant managing the organizational culture and trust architecture that enabled the information sharing and authority delegation the model required.

This role change is psychologically difficult for leaders who have built their careers on individual competence. The gardener-leader is less visibly central than the command-leader. Their contribution is often invisible in the short term — the conditions they create, the trust they build, the clarity they provide show up in the organization’s collective performance rather than in identifiable individual decisions. McChrystal acknowledges this explicitly, which makes his account more credible than most leadership transformation narratives that describe the transition as straightforwardly desirable without acknowledging what the leader actually loses by making it.

What Team of Teams Gets Right

The complexity versus complication distinction is McChrystal’s most important conceptual contribution, and it resolves a confusion that pervades organizational management thinking. The management tools developed for complicated systems do not work in complex systems, and applying them there produces the JSOC experience: an organization that is technically brilliant and operationally overmatched by a less sophisticated but more adaptable adversary. This diagnosis applies to most large commercial organizations operating in markets that have become genuinely complex — technology markets, media markets, financial markets — and it explains patterns of large-organization performance failure that conventional management analysis consistently fails to account for.

The embedding mechanism for building inter-team trust is also concrete and immediately applicable. The insight that personal relationships are the foundation of inter-team information sharing, and that those relationships can be deliberately built through structured exposure, is more specific and more actionable than most prescriptions for improving cross-functional collaboration. Organizations that implement systematic rotation programs, joint project assignments, and deliberate cross-team exposure typically produce significantly better information sharing than organizations that mandate collaboration without addressing the relationship foundation.

What Team of Teams Gets Wrong

The book underestimates the difficulty of creating genuine shared consciousness in commercial organizations where command authority does not exist. McChrystal could mandate the O&I briefing. Commercial leaders can rarely mandate the equivalent. Without the mandate, information sharing across organizational boundaries tends to revert to the siloed default because sharing information has costs while the benefits are diffuse. The book provides the what with great clarity; the how do you make it happen without military command authority receives less thorough treatment.

The book also somewhat overstates the universality of the team of teams model. Not all commercial environments are genuinely complex in McChrystal’s sense. Many organizations operate in environments that are complicated rather than complex — technically demanding, but fundamentally predictable — and for those organizations the machine model’s efficiency advantages still outweigh its adaptability costs. The reader who applies the team of teams model to an organization in a stable environment will incur the information-sharing and redundancy costs without capturing the adaptability benefits that justify those costs in complex environments.

The Team of Teams Protocol

1. Diagnose your environment: is your primary challenge efficiency (doing known tasks faster) or adaptability (responding to novel and changing demands)? If adaptability, the machine model is limiting you and the team of teams investment is justified.
2. Map your information silos: which teams or functions have information that other teams need but do not currently access? These gaps are your shared consciousness deficits.
3. Implement a regular all-hands information sharing session. Make it genuinely informational — teams sharing what they are learning and doing — not a management communications session.
4. Build inter-team trust through embedding: create regular opportunities for team members to spend time in other teams, not as project assignments but as relationship-building exposure.
5. Clarify your commander’s intent. State the organizational goals and values so clearly that the people you are empowering could make decisions you would endorse without asking you first.
6. Push decision authority to the level where the relevant knowledge resides. Identify the decisions that currently require your approval but where someone else has better information, and explicitly delegate them.
7. Shift your personal leadership investment from deciding to enabling. The measure of your leadership is not the quality of the decisions you make but the quality of the decisions the organization makes when you are not present.

Books Similar to Team of Teams

David Marquet’s Turn the Ship Around! covers complementary territory from a smaller-scale command perspective, with more emphasis on the leader-leader authority model and the specific linguistic mechanisms for delegating authority. Frederic Laloux’s Reinventing Organizations extends the team of teams logic to full organizational redesign with extensive case studies of organizations that have implemented distributed authority at the whole-enterprise level. Nassim Taleb’s Antifragile is the philosophical companion, analyzing why systems that benefit from volatility outperform systems optimized for efficiency in stable conditions. For the trust dimension specifically, Patrick Lencioni’s The Five Dysfunctions of a Team provides the framework for building the team-level trust that the team of teams model requires before scaling.

Who Should Read Team of Teams

This book is essential for leaders of organizations operating in rapidly changing environments who are finding that their traditional hierarchical structures are too slow to keep pace with competitive and environmental change. It is particularly relevant for technology companies, professional services firms, and any organization where adaptability is the primary competitive advantage. It is less relevant for organizations in stable, highly regulated environments where operational efficiency remains the dominant value driver. The military context may initially seem distant from commercial application, but the organizational principles are among the most rigorously tested in management literature precisely because the feedback environment was so unambiguous: the model either worked or people died.

Integration

The most immediately applicable insight from this book is the shared consciousness audit. Before attempting any structural change, spend a week mapping the information flows in your organization: who knows what, who needs to know what, and where the critical gaps are. The map you produce will reveal the specific silos that are limiting your organization’s adaptability more precisely than any organizational survey or consultant diagnostic. Design targeted interventions to close the highest-impact gaps first. The structural changes follow from that diagnostic — they are not the starting point.

“The temptation to lead as a chess master, controlling each move of the organization, must give way to an approach as a gardener, enabling rather than directing.” — Stanley McChrystal

FAQ

How does a commercial organization create the equivalent of the O&I briefing? The format should match the pace of change in your environment. In fast-moving environments, a daily thirty-minute all-hands where each team shares its current status and recent learnings may be appropriate. In slower-moving environments, weekly or biweekly may suffice. The key design principle is genuine information sharing rather than management reporting: teams share what they are learning and what they are doing, not just what management wants to communicate.

Won’t empowered execution produce inconsistent decisions? It will produce more diverse decisions than centralized decision-making, which is different from inconsistent. Diverse decisions made by people with better local information are often better aligned with actual conditions than consistent decisions made centrally with staler information. The goal of shared consciousness is to ensure that the diversity of decentralized decisions is aligned with organizational intent, not that it is identical to what a central authority would have decided.

How do you build inter-team trust without formal rotation programs? McChrystal’s embedding mechanism can be scaled down significantly. Even a single half-day where a team member works alongside another team, attends their meetings, and understands their challenges produces meaningful trust compared to purely transactional inter-team interactions. The investment is modest; the returns in information-sharing quality compound over time as the relationships create the channels through which informal knowledge flows between teams.

What is the first sign that the team of teams transformation is working? McChrystal identifies the specific leading indicator: the frequency with which units act on information from other units without requesting central coordination. In the conventional machine model, cross-unit action requires central approval or at minimum central coordination. In the team of teams model, units act directly on cross-unit information when their shared consciousness and empowered execution authority allow it. The frequency of these direct cross-unit actions, without central coordination, is the most sensitive early indicator of whether the shared consciousness and empowered execution mechanisms are actually working.

Related: The Speed of Trust Summary

Related: Peak Performance Summary

References

• NIAMS Musculoskeletal Health
• Team of Teams on Goodreads

Editorial StandardsCorrectionsMedical DisclaimerAbout Our ContentAffiliate DisclosureSite Map