You’re probably here because you’ve heard the buzzword. "Agility." It’s everywhere. But honestly, most people talking about it have never actually been in a situation where a lack of agility results in a body bag. Stanley McChrystal has. When he took over the Joint Special Operations Task Force in Iraq back in 2003, he had the best tech, the best soldiers, and the most funding in human history. He was still losing. He was losing to a decentralized, ragtag insurgency that didn't have a HR department or a five-year plan. That’s the core tension of the Team of Teams book. It isn't just a management manual; it’s a confession from a four-star general that his rigid, traditional way of thinking was obsolete.
The world changed. It got "complex."
Most leaders confuse "complicated" with "complex." A car engine is complicated. It has thousands of parts, but if you're a genius mechanic, you can predict exactly how it works. You turn a key; the piston fires. Complex systems, like the weather or a global market or a guerrilla war, are different. They change as you interact with them. You can't "manage" a complex system in the old-school, Taylorist sense. You have to adapt to it. This realization is what forced the creation of a new organizational model.
Efficiency is a Trap
For a century, we worshipped at the altar of efficiency. Frederick Winslow Taylor, the father of scientific management, taught us that there is one "best way" to do any task. You break the job down, you time it with a stopwatch, and you make the worker a cog. It worked great for making Ford Model Ts. It works horribly for 21st-century software development or global logistics.
In the Team of Teams book, McChrystal argues that we’ve reached the limit of efficiency. If you optimize for efficiency, you sacrifice resilience. Think about it. A highly efficient supply chain has zero waste, which means it has zero "slack." When a ship gets stuck in the Suez Canal or a pandemic hits, that "efficient" system shatters because it has no buffer.
The Task Force in Iraq was efficient. They could execute a raid with surgical precision. But they were "doing the wrong things right." They were winning individual battles but losing the war because the information moved too slowly up the chain of command. By the time a request for intelligence went up to headquarters and a decision came back down, the target was gone. The "enemy" didn't have a chain of command. They had a network.
The Silo Problem Is Killing Your Culture
You’ve seen this in your own office. Marketing hates Sales. Engineering thinks Product is delusional. Everyone sits in their little "functional silo" and guards their data like a dragon guarding gold.
In the Task Force, the SEALS didn't trust the CIA. The CIA didn't want to share files with the Army. It was a mess of tribalism. McChrystal’s solution wasn't to get rid of the teams—you still need specialized experts—but to create "Shared Consciousness."
👉 See also: Wall Street Lays an Egg: The Truth About the Most Famous Headline in History
Basically, he realized that if everyone doesn't see the whole "map," they can't make smart decisions. He started a daily briefing called the O&I (Operations and Intelligence). It wasn't a boring meeting. It was a massive, 90-minute video conference with thousands of people. Everyone heard everything. The goal was to give the person at the very edge of the organization the same context as the guy at the top.
Transparency isn't just a "nice to have" anymore. It's a survival mechanism. If your team has to wait for a manager's approval for every little thing, you're already dead in the water. You need "Empowered Execution." This means letting the people who are closest to the problem make the decisions.
Wait.
Doesn't that lead to chaos?
Kinda. But only if you don't have that shared consciousness first. You can only delegate authority when everyone is singing from the same songbook. If the team knows the mission and has the same data you have, they’ll usually make the right call. If they don't have the data, they’re just guessing.
It’s About Gardening, Not Chess
This is the best metaphor in the whole book. Traditionally, we think of a leader as a chess master. You move the pieces. You control the board. You are the "Great Man" with the plan.
McChrystal says that's garbage.
✨ Don't miss: 121 GBP to USD: Why Your Bank Is Probably Ripping You Off
A modern leader should be a gardener. A gardener doesn't actually "grow" the plants. The plants grow themselves. The gardener’s job is to create the environment where the plants can grow. You pull the weeds. You water the soil. You clear the obstacles. You deal with the "white space" between the teams.
It's a huge ego blow for most executives. They want to be the hero. They want to be the one who saves the day. But in a Team of Teams model, the leader’s job is mostly about communication and culture. It’s about building trust.
Trust is the Only Currency That Matters
You can't have a network without trust. In the SEALS, trust is built through shared hardship. You can't exactly simulate "Hell Week" in a corporate HR department (though some tech startups try).
So how do you build trust between teams that have never met?
The book suggests a "liaison" program. They took their best people—not the ones they could spare, but the ones they couldn't afford to lose—and sent them to live and work with other teams. A SEAL would go live with an intelligence unit. A CIA analyst would go out on a mission with the Rangers.
Suddenly, the "other" has a face. You aren't just sending an email to "the guys in accounting." You’re sending it to Mike, who you had a beer with last week and who helped you out when your laptop crashed. These "horizontal" links are what make the network strong. They are the glue that holds the Team of Teams book philosophy together.
Why Most Companies Fail to Implement This
Honestly? It's scary.
🔗 Read more: Yangshan Deep Water Port: The Engineering Gamble That Keeps Global Shipping From Collapsing
Most CEOs say they want a "Team of Teams," but they aren't willing to give up control. They aren't willing to be "gardeners." They still want to micromanage the chess pieces.
Also, it’s hard to measure. How do you put "Shared Consciousness" on a spreadsheet? You can't. It’s a qualitative shift, not a quantitative one. It requires a level of radical transparency that makes legal departments and middle managers break out in hives. If you tell everyone everything, some of that info might leak. That’s the risk. But McChrystal’s point is that the risk of not sharing is much higher.
Real-World Nuance: The Military Isn't Business
We have to be careful here. There’s a limit to the military-to-corporate analogy. In the military, everyone has the same ultimate goal: survival and mission success. In a company, people have competing incentives. A salesperson might be incentivized to close a deal that the engineering team can't actually build.
The Team of Teams book acknowledges that structural changes aren't enough. You have to change the incentive structures too. If you want people to work as one team, you can't rank them against each other on a curve. You can't have "bonus pools" that pit departments against one another.
The model also requires a massive amount of time. Those daily O&I briefings took up a huge chunk of the day. For a struggling startup or a lean manufacturing plant, that "overhead" feels like a waste. But McChrystal argues it’s an investment in speed. You spend time on the front end to save time on the back end.
How to Start Using Team of Teams Today
Don't go out and fire all your managers tomorrow. That’s a recipe for a disaster. Instead, look for the friction points. Where is information getting stuck? Where are people waiting for "permission" to do something they already know how to do?
- Identify your "silos." Pick two departments that usually butt heads. Force them to swap one person for a month. Not a low-level intern. Someone who actually matters.
- Open the floodgates of info. Start a "Read-Out" or a shared document where every team posts what they’re working on and what they’re struggling with. Make it public to the whole company.
- Kill the "Need to Know" culture. Unless it’s literally illegal or a massive privacy violation, default to sharing.
- Redefine the "Lead." If you’re a manager, ask yourself: "Am I moving a chess piece right now, or am I watering the garden?" If you’re making a decision that someone closer to the work could make, stop.
- Build "Resonant" Relationships. Focus on the links between the circles on your org chart, not just the circles themselves.
The Team of Teams book isn't a silver bullet. It’s a challenge to the way we’ve been taught to work since the Industrial Revolution. It’s messy, it’s loud, and it’s often uncomfortable. But in a world that’s only getting more complex, the "command and control" model is a relic. You can either adapt your leadership style to match the speed of the world, or you can watch a more "agile" competitor eat your lunch while you’re still waiting for a memo to be approved.
The Task Force didn't change because they wanted to. They changed because they had to. Most businesses today are in the same boat; they just haven't realized the water is rising yet.