The correct answer is D. Kotter's Dual Operating System emphasizes the need to run transformation through a second, more agile network alongside the traditional hierarchy. One of its principles is a ''get-to'' mindset rather than a ''have-to'' mindset. This means people participate because they are emotionally and intellectually committed to the opportunity, not simply because management has mandated compliance.

This is highly relevant to DevOps leadership because sustainable change cannot be achieved only through policy, structure, or tool adoption. Teams must understand the purpose of the transformation and feel motivated to contribute to better flow, faster feedback, improved resilience, and customer value. A ''get-to'' mindset creates voluntary energy, ownership, and momentum.

The other options are incorrect. Kotter does not advocate more management or simply enhancing hierarchy. Nor is transformation only ''head driven''; successful change engages both head and heart. Relevant study guide references: Maintaining Energy and Momentum; DevOps and Transformational Leadership; Articulating and Socializing Vision.

==============