Team of Teams: New Rules of Engagement for a Complex World

Between 2003 and 2008, Stanley McChrystal commanded the American special operations task force hunting Al-Qaeda in Iraq. His troops had the best training, the best technology, and more resources than almost any army in history. On the other side was a network of militants with little money and no visible hierarchy, with no general in charge.

Even so, for a good while, that network was able to move and react faster than a war machine trained precisely to beat that kind of enemy. The explanation McChrystal arrived at wasn't a lack of resources. It was the shape of the organization itself, designed to be efficient, not to adapt quickly.

The book is born from that turning point: instead of copying the enemy's structure, the way out was to take what makes a small team work well, trust and fast decisions at the level of the people who see the problem, and fit that into an organization of thousands. Hence the title, a team of teams.

The book separates two kinds of problems we usually treat as if they were the same. A complicated problem has many parts, but they behave in predictable ways, like an airplane engine: once you understand each part, you can predict the result. A complex system is different. The parts change their behavior depending on what the others do, and you can't predict the result just by looking at each part separately.

Big-city traffic, the weather, and the financial market are complex, full of interdependence, just like a war against a decentralized enemy. The right tool for a complicated problem, detailed planning and standardized process, makes a complex problem worse, because it creates an illusion of control where no control is possible.

Most companies are still organized to deal with the complicated world: a clear chain of command, a defined process. That works as long as the environment is stable. When it becomes complex, with a new competitor, new technology, a customer who changes every week, the same structure that guaranteed efficiency becomes dead weight.

To explain where this way of organizing armies and companies comes from, the book goes back to Frederick Taylor and the early twentieth century, when the assembly line replaced the craftsman who made the whole product with a worker who repeated one small, standardized, timed movement. This efficiency model became known as Taylorism, and industrial productivity shot up so much that it became the reference for almost every large organization afterward.

The problem is that this design rests on a bet: that the world out there is stable enough to make it worthwhile to plan everything in advance and repeat the plan over and over without stopping to reconsider. It works well in a factory with predictable demand, and works poorly when the scene changes completely every week.

McChrystal doesn't dismiss efficiency as a value. He only argues that efficiency and adaptability pull an organization in different directions, and that a good share of companies are still optimized for the first when the world already demands the second.