ADKAR Is Not Enough: Why Change Management Needs a Motivation Layer

I watched a £3 million digital transformation project fail last month. The ADKAR model was executed perfectly. Awareness sessions? Tick. Desire building workshops? Tick. Knowledge transfer programmes? Tick. Ability assessments? Tick. Reinforcement mechanisms? Double tick.

Six months later, adoption sat at 23%.

The problem was not that ADKAR is wrong. It is that ADKAR assumes motivation works like a light switch. Build awareness, create desire, job done. But motivation is not binary. It is a complex system that needs constant feeding.

Where ADKAR Goes Wrong

ADKAR treats desire as a single hurdle to clear early in the process. You run some workshops, explain the vision, get people nodded up, then move on to training. But real motivation operates on three levels simultaneously: autonomy, competence, and purpose.

When we worked with ING on their agile transformation, the initial ADKAR approach created plenty of awareness. People understood why they needed to work differently. They even wanted to try. But the moment they hit their first sprint retrospective, motivation collapsed.

Why? Because knowing you should do something and feeling motivated to keep doing it when it gets hard are completely different beasts.

The Missing Layer: Intrinsic Motivation Design

Self-Determination Theory tells us that sustainable motivation requires three psychological needs: autonomy (feeling in control), competence (feeling capable), and relatedness (feeling connected to others and purpose).

ADKAR's "Desire" phase hits relatedness through vision alignment. But it barely touches autonomy and competence. And those two are what keep people going when the novelty wears off.

At American Express, we overlaid a motivation layer on their customer service transformation. Instead of just training people on new processes, we designed choice architecture into the change itself.

Customer service reps could choose which new techniques to try first. They could customise their workspace setup. They had input on team goals. Small things, but they shifted the psychological experience from "this is being done to me" to "I am choosing to do this."

Adoption jumped from 31% to 78% in the same timeframe.

Three Ways to Add the Motivation Layer

1. Build Choice Into the Change

Even small choices create ownership. Let people decide the order they tackle new skills. Give them options for how they structure their workspace or schedule. When Disney rolled out new guest experience protocols, they let each team choose their implementation timeline within a six-week window. Engagement scores doubled.

2. Create Competence Loops

ADKAR measures ability once and moves on. Sustainable motivation requires ongoing competence building. Set up micro-wins that happen weekly, not quarterly. At NatWest, we created "Friday wins" where teams shared one small improvement they had made using new processes. The social recognition created a feedback loop that kept motivation alive.

3. Make Progress Visible

People need to see that they are getting better, not just that the project is on track. Create individual dashboards that show skill development, not just compliance metrics. When NASA implemented new collaboration tools, they tracked "collaboration confidence scores" alongside usage rates. Confidence went up, usage followed.

The Integration Challenge

The temptation is to bolt motivation strategies onto existing ADKAR frameworks. That creates more complexity without more results.

Instead, weave motivation design into each ADKAR phase. In Awareness, include choice architecture. In Desire, build competence indicators. In Knowledge, create autonomy opportunities. In Ability, design visible progress loops. In Reinforcement, celebrate growth, not just compliance.

This is not about replacing ADKAR. It is about recognising that change management without motivation psychology is project management in disguise. You might hit your milestones, but you will not change behaviour.

The companies that get this right do not just manage change. They design motivation systems that make people want to keep changing long after the project team has moved on.

Change without motivation is just expensive training.