Agility wins in today’s environment, and the organizations that have it run on something better than individual effort: networks of empowered teams working as one. General Stanley McChrystal captured this in Team of Teams — small, autonomous units sharing a common purpose, trust, and the freedom to act without waiting for permission from above. It’s a compelling model, and its core principles are exactly right for a decentralized, fast-moving world. But there’s a gap. Team of Teams describes what a high-performing network looks like; it’s lighter on the day-to-day system that builds and sustains one.
This piece, written with Tom Jackson, makes the case that Lean supplies that missing operating discipline. Where Team of Teams calls for shared consciousness, trust, and empowered execution, Lean offers the proven machinery to produce them — strategy deployment and catchball to align purpose, the obeya and daily huddles to keep teams synchronized, and a tiered problem-solving system that puts the scientific method in everyone’s hands. We include a side-by-side comparison of the two frameworks’ tools, and the pattern is clear: the principles of Team of Teams and the standardized practices of Lean reinforce each other, with Lean filling the precise gaps where the original framework runs thin.
If you’re leading a decentralized or cross-functional organization and want agility that lasts rather than depends on heroics, this is the argument for pairing an inspiring model with a durable operating system. It’s how you turn the idea of empowered teams into a repeatable way of working.