Why a new framework.

ADKAR (Prosci) and Kotter's 8 steps are the two frameworks most change practitioners reach for. Both are good. Neither was built for a technology that updates quarterly, spreads through unsanctioned tools, and produces value that is hard to attribute. Kotter's original eight-step model was published in Harvard Business Review's 1995 article "Leading Change", almost three decades before generative AI made change continuous rather than episodic.

An AI change framework keeps the human-transition strength of the classics and adds three things they leave out: continuous workflow redesign, AI-specific governance, and a measurement model that survives a model upgrade. BCG's research on AI value capture consistently shows that the gap between AI leaders and laggards is almost entirely on the people and process side, not the model side.

The seven layers.

Layer 01

Diagnose.

What it delivers: Read across people, process, and platform. Name the three to five places AI is producing measurable value and the three to five places it is producing measurable cost. Write the read; do not just score it.
Failure mode: Maturity-model scoring with no narrative. Everyone agrees the score is roughly right. Nothing changes.

Layer 02

Decide.

What it delivers: Make the explicit bets. Which workflows, teams, and tools you are investing in - and the no list. Connect each bet to a business outcome and at least one customer outcome.
Failure mode: Every team funded. No no list. Investments do not compound.

Layer 03

Redesign.

What it delivers: Rebuild the workflows touched by each bet with AI in the loop. Owner on the keyboard during the redesign, not just in the readout.
Failure mode: AI bolted on top of an unchanged process. Time saved disappears into more rounds of the same work.

Layer 04

Enable.

What it delivers: Move people through the redesigned workflow in pairs. Role-specific fluency, not generic prompt-craft workshops. Leaders model use themselves.
Failure mode: Training programs with no link to the work the trainees do on Monday morning.

Layer 05

Govern.

What it delivers: Sanctioned tool list. One named owner of the AI stack. Policy on data, prompts, and approvals - written in language a director can apply without calling legal.
Failure mode: Either no policy (shadow tools everywhere) or policy so heavy it pushes use back into the shadow stack.

Layer 06

Measure.

What it delivers: Per bet: one adoption metric, one capability metric, one outcome metric. Public to the team. Reviewed quarterly.
Failure mode: Active-user counts only. Vanity metrics. No tie to a business outcome.

Layer 07

Re-read.

What it delivers: Schedule the next diagnosis before finishing the current one. The model landscape will have moved; the framework is a loop, not a line.
Failure mode: Strategy shipped, never re-read. Plan is a year out of date in nine months.

How this maps to ADKAR and Kotter.

Our Enable layer applies the same logic ADKAR (Awareness, Desire, Knowledge, Ability, Reinforcement) is built on: adoption happens one person at a time. Kotter's discipline around sponsorship and momentum shows up in how we run Decide, Enable, and Measure. This framework is not a replacement for the classics and does not repackage them. It adds the AI-specific layers around the ground they cover.

Questions people ask.

What is an AI change management framework?

A repeatable structure for moving an organization from one way of working to a new, AI-included way of working - without losing trust, quality, or people. It covers the human transition (awareness, desire, capability), the workflow redesign, the governance, and the measurement. Classical change frameworks like ADKAR and Kotter cover the first part well; AI-native frameworks add the rest.

Why not just use ADKAR or Kotter?

Use them - but not alone. ADKAR is excellent for the human-side transition. Kotter is excellent for the leadership arc. Neither was designed for the AI-specific failure modes: shadow tool sprawl, prompt-hygiene drift, model updates that change the workflow under your feet, and the always-on cadence of AI rollouts. An AI-native framework adds those.

What is the simplest version that still works?

Three things repeatedly: diagnose where AI is producing value and where it is producing cost; redesign the specific workflows touched; bring the people through those redesigns with named owners and measured outcomes. Re-run the cycle quarterly because the model landscape will have moved.

Where does software fit?

Below the framework, not above it. Adoption platforms, learning platforms, and AI spend trackers all help once you know what you are driving. Buying them first - before the framework - usually wastes the license. See the <a href='/guides/ai-change-management-software-comparison'>software comparison guide</a> for which to buy when.

ADKAR is a registered trademark of Prosci Inc. Kotter's 8-Step Process, Lewin's change model, and the McKinsey 7-S framework remain the work and intellectual property of their respective creators. Average Robot is not affiliated with, certified by, or endorsed by any of these organizations. References here are for comparison and commentary.

An AI change management framework.