Team of Teams: New Rules of Engagement for a Complex World
McChrystal commanded US special operations in Iraq and the book is his account of discovering that his enemy — decentralised, networked, fast — was organised for the problem his traditional hierarchy was not.
The solution was to rebuild the US force as a "team of teams" — small autonomous units connected by shared information and shared purpose rather than by command.
For product direction the transfer is direct: modern product organisations face a structurally similar problem, and McChrystal's specific description of how a hierarchy makes the shift is more useful than the abstract "empowered teams" literature.
Read alongside Cagan's Empowered and Skelton's Team Topologies for complementary views. A book that survives its self-seriousness.
Central argument
McChrystal argues that the hierarchical command structures optimised for efficiency in predictable environments become a liability when facing adaptive, decentralised adversaries operating at networked speed. His central finding, drawn from the Joint Special Operations Command in Iraq, is that top-down coordination cannot process information fast enough to respond to emergent, complex threats — and that the solution is not simply faster hierarchy but a structural transformation: small, high-trust teams connected by radical transparency and shared consciousness, empowered to act without waiting for authorisation from above. The 'team of teams' model replaces command with alignment, and control with context.
Critique
The book's argument rests heavily on a single, exceptional case — a uniquely resourced military organisation fighting a specific asymmetric conflict — and McChrystal does not fully reckon with how much the transformation depended on his personal authority as commander to impose it top-down, a power most product leaders do not hold. The model also assumes that shared information reliably produces shared purpose, which glosses over the political and incentive dynamics that cause organisations to resist transparency even when the infrastructure for it exists. Readers should be cautious about treating a wartime reorganisation, driven by existential pressure and unified command, as a directly transferable blueprint for corporate product organisations.
Why it matters for product
The book's specific account of how centralised information-sharing — McChrystal's 'giant operations centre' and daily cross-unit briefings — enabled decentralised autonomous action maps directly onto one of the hardest problems in product organisation: how to let teams own decisions locally without creating strategy fragmentation or duplicated effort. For a CPO managing multiple product squads, the 'shared consciousness' mechanism offers a more concrete model than generic empowerment frameworks — it implies that the infrastructure enabling autonomy is not org chart design but deliberate, high-frequency, cross-team visibility into what every unit knows and is doing. It also reframes the CPO role itself: less as decision-maker, more as architect of the conditions under which good decisions propagate without escalation.