Accelerate: Building Strategic Agility for a Faster-Moving World
Kotter's argument is that large organisations cannot both run reliable operations at scale and respond to rapid external change using a single hierarchical structure — the fix is a "dual operating system" of hierarchy alongside a volunteer network.
The book extends his earlier work on change management into a structural argument about organisational design.
For product direction the dual-system idea is a useful diagnostic: much of the friction between product teams and the rest of a large organisation is the mismatch between the two operating modes, and Kotter's vocabulary for naming it helps.
Read alongside McChrystal's Team of Teams for a military-origin version of the same argument.
Central argument
Kotter argues that large organisations are structurally incapable of being simultaneously reliable and adaptive because a single hierarchy optimised for efficiency will always suppress the fast, experimental responses that volatile environments demand. His proposed fix is a 'dual operating system': a permanent, volunteer-driven network that runs alongside the formal hierarchy rather than replacing it. This is not a change programme with an end date but a standing architectural feature of how the organisation operates.
Critique
The volunteer network premise quietly assumes a discretionary labour supply — that motivated employees will contribute to the network on top of their existing hierarchical obligations. In practice, particularly in cost-pressured or headcount-constrained organisations, this becomes an unfunded mandate that falls disproportionately on already-stretched senior individual contributors. Kotter offers little structural guidance on how the two systems adjudicate conflicts over resources, priorities, or authority when they inevitably collide.
Why it matters for product
For a CPO, the dual operating system is a precise diagnostic for a recurring problem: product teams are structurally part of the network-mode but are embedded in, funded by, and measured against the hierarchy-mode, which explains why roadmap governance, headcount approvals, and OKR cycles so often neutralise discovery work before it can act on what it finds. Naming this as a structural mismatch rather than a cultural or personnel failure changes the conversation with the CEO and CFO about why product velocity degrades at scale.