Contrary to the belief of many in the Agile and DevOps communities, change management is not optional in a transformation. This path shows what it actually contributes — and equips practitioners with tools from Prosci, Kotter, and the University of California toolkit, not just one.
Too many Agile and DevOps transformations neglect change management entirely — and then wonder why the cultural and behavioral change never arrives. This path corrects that gap, with a full toolkit drawn from multiple frameworks, not just one.
Contrary to the belief of many in the Agile and DevOps communities, change management is an integral part of any transformation — not a soft discipline to be skipped in favor of faster delivery cycles.
During all too many transformations, practitioners neglect the integral part that change management plays. The assumption — common in Agile and DevOps communities — is that good delivery practices will drive cultural change on their own. They do not. Culture changes when behavior changes, and behavior changes when the change is managed — not when it is announced.
The result is transformations that produce new process artifacts and certified practitioners, but leave the organizational culture and leadership behaviors entirely unchanged. The new way of working exists in the backlog, not in how the organization actually works.
During discussions with practitioners, we often discuss the role of an executive sponsor and are surprised to discover that there is no clearly defined role for the sponsor. The sponsor is listed in the program documentation, presented in the kickoff deck, and then left undefined — with no clarity on what they are expected to do, when, and toward what outcome.
This is exactly where change management plays a critical role. Change management lays out a clear plan for the role the sponsor will take in the transformation — specific accountabilities, specific moments, and specific escalation authorities — not a ceremonial title on a slide.
Most change management programs pick a framework — Prosci's ADKAR model, or Kotter's 8-Step Process — and apply it consistently regardless of organizational context. We disagree with that approach. Different transformations, different cultures, and different resistance patterns call for different tools.
In this path, we draw from three distinct toolkits, and we teach practitioners how to select the right tool for the situation in front of them rather than defaulting to the one they were certified in.
We also believe change management's most valuable contribution is before the transformation starts — identifying the resistance, behaviors, and impediments the organization is likely to face before they become crises, and building a response plan that can be adjusted as the transformation progresses.
Prosci's ADKAR model provides a structured framework for understanding change at the individual level — the five sequential building blocks that every person in an organization must work through before behavioral change becomes permanent. It is particularly powerful for diagnosing where individual resistance is occurring and designing targeted interventions at that specific stage.
Kotter's 8-Step Process operates at the organizational and leadership level — creating the conditions in which change can take root and persist. It is especially effective for large-scale transformations where leadership alignment, cultural shift, and the embedding of change into institutional norms are the primary challenges. The 8 steps are not sequential ceremonies; they are a framework for building the organizational will to change.
The University of California's change management toolkit offers a practitioner-level set of operational tools that complement both Prosci and Kotter — stakeholder analysis templates, resistance mapping exercises, communication planning guides, and organizational readiness assessments. These are the tools that allow change managers to move from framework theory into daily practice. We integrate the UC toolkit precisely because it fills the gap that both ADKAR and Kotter leave: the specific, repeatable instruments practitioners need to execute a change plan, not just design one.
Change management helps organizations before the transformation starts by surfacing the resistance, behaviors, and impediments they are likely to face — so a response plan can be built before those obstacles derail the work. It does not wait for resistance to appear and then respond. It maps resistance proactively and designs interventions in advance.
It then continues through the transformation as an active monitoring and adjustment discipline — continuously checking whether the plan is producing the expected behavioral outcomes, and adjusting when it is not. This is the ongoing, iterative role that change management plays, and it is the function most organizations drop as soon as the kick-off is over.
And critically, it defines exactly what the executive sponsor does — not as a general statement of visible support, but as a specific set of accountabilities with timing, escalation authority, and behavioral expectations.
Active, visible leadership — not passive endorsement. The sponsor makes the case for the transformation in their own words, in real conversations, at real moments — not by lending their name to a communications deck that others wrote.
Resistance management at the leadership level. When peer executives resist the transformation, the sponsor is the one who addresses it — not the change practitioner, not the program manager. Change management defines when and how the sponsor intervenes at the leadership level.
Escalation authority and decision rights. The sponsor has the authority to unblock impediments that exceed the program team's authority — and change management defines which decisions require sponsor intervention, so that authority is exercised at the right moment rather than invoked after the damage is done.
Reinforcement of the new behaviors. The sponsor actively recognizes and reinforces the behaviors the transformation is trying to embed — not once at the kick-off, but continuously, because reinforcement is what makes behavioral change permanent rather than temporary.
Why change management is not a soft add-on to transformation — and how its absence explains the pattern of transformations that produce new processes but leave organizational culture unchanged.
How to draw from Prosci (ADKAR), Kotter's 8-Step Process, and the University of California toolkit — and how to select the right tool for the resistance pattern and organizational context in front of you.
How to surface the resistance, behaviors, and impediments a transformation is likely to face before it starts — building a response plan that can be monitored and adjusted continuously as the transformation progresses.
How to design a clearly defined executive sponsor role — specific accountabilities, timing, escalation authority, and behavioral expectations — so the sponsor knows exactly what they are being asked to do and when.
The specific change management tools that address organizational culture and behavior — stakeholder analysis, communication planning, readiness assessment, and the reinforcement mechanisms that make behavioral change permanent.
How to build the monitoring cadence that keeps change management active throughout the transformation — continuously checking whether the plan is producing the expected outcomes, and adjusting the approach when it is not.
This path is taught immersively, in cohort groups — practitioners applying change management tools to the resistance patterns in their actual transformations, not studying framework theory in isolation. It is one of twelve ADAPT© Learning Paths built around outcomes, not frameworks.
Start with a free 30-minute Capability Readiness Review — a clear, honest read on where your change management gaps are and which path fits best.