Question 1

Why does Kotter argue that a single hierarchical structure can't handle both operational efficiency and rapid change?

Accepted Answer

Kotter contends that large organisations face an inherent tension: hierarchies excel at running reliable operations at scale, but they're too slow to respond to external change. His solution is a "dual operating system" that pairs the traditional hierarchy with a volunteer network, allowing each to do what it does best without forcing the other to compromise.

Question 2

How can product leaders use Kotter's dual operating system concept to diagnose friction within their organization?

Accepted Answer

Much of the friction between product teams and the broader organisation stems from misaligned operating modes—product teams often operate in agile, network-like structures while the rest of the company runs on hierarchy. Kotter's vocabulary for naming this structural mismatch provides a diagnostic tool to identify whether conflicts are cultural or genuinely systemic.

Question 3

How does this book extend Kotter's earlier change management work?

Accepted Answer

While Kotter's earlier work focused on managing change as a process within existing structures, *Accelerate* argues that change requires structural redesign. He moves from "how do we execute change" to "what organisational architecture actually enables continuous adaptation," making it a more foundational argument about design rather than execution.