Marcus Andrey Study
Ler em português Library

Framework · Influence & change · 3 min read

ADKAR

Individual change runs through Awareness, Desire, Knowledge, Ability and Reinforcement; use it to diagnose where someone is stuck and pick the right fix.

  1. AAwareness

    Needs: to know why the change is happening.

    Lead action: explain the problem it solves.
  2. DDesire

    Needs: a personal reason to take part.

    Lead action: show what is in it for them.
  3. KKnowledge

    Needs: to know how to do the new thing.

    Lead action: train and give clear guides.
  4. AAbility

    Needs: to do it in real work, not only in theory.

    Lead action: practise together with support.
  5. RReinforcement

    Needs: reasons to keep doing it.

    Lead action: recognise it and make it the default.
ADKAR shows the five things a person needs, in order, before a change sticks; find the first one that is missing.

Use it when

  • A team keeps "resisting" the design system and you need to know why before you plan the next step.
  • You are rolling out a new tool, process or way of working and want to check each group is ready for it.
  • A change was launched, people used it for a few weeks and then slipped back to the old way.

How to use it

  1. Name the change and who it affects. Write one sentence for what changes, and list the people or teams who must work differently. ADKAR is about individuals, so think person by person or small group by small group. Output: the change in one sentence and a list of who it affects.
  2. Check each stage in order. For each person or group, ask: do they know why (Awareness)? Do they want to (Desire)? Do they know how (Knowledge)? Can they do it in real work (Ability)? Is anything keeping it going (Reinforcement)? Use what they say and do, not what you assume. Output: a yes / partly / no for each stage.
  3. Find the first gap. The first "no" in the order is where they are stuck. Later stages don't matter yet. Output: one blocking stage per person or group.
  4. Pick the fix for that stage. No awareness: explain the problem it solves. No desire: show the benefits for them. No knowledge: train. No ability: practise with support. No reinforcement: recognise it and make it the default. Output: one or two actions per gap, with an owner.
  5. Check again after a few weeks. Run the same check. When one gap closes, the next stage becomes the work. Output: an updated diagnosis and the next action.

Worked example

On an internal operations platform with 6 product teams, the design system team opens a contribution process: product teams can propose new components instead of building one-offs. After two months, one team is openly sceptical and has sent nothing. The lead runs a short ADKAR check with that team.

Stage What the lead found Status Action
Awareness They know the process exists and why it was set up. Yes None
Desire They believe a proposal takes weeks and blocks their sprint. "Faster to build it ourselves." No Show a real proposal that was accepted in a week. Agree a review time limit with the design system team.
Knowledge Not sure what a proposal must include. Partly Wait. Share the guide once Desire moves.
Ability Not tested yet. Unknown Pair a designer with the design system team on the first proposal.
Reinforcement No one sees contributions being credited. No Later: name contributors in the release notes.

The team is stuck at Desire. Another training session would address Knowledge and miss the real problem. The lead starts with the benefit and the review time limit, and plans the guide and pairing for when the team agrees to try.

Watch out for

  • Training as the default fix. Workshops are easy to organise, so they get used for every gap. Often the real gap is Desire, and training does not fix it.
  • Diagnosing the whole organisation as one. Different teams get stuck at different stages. One plan for everyone will be wrong for most of them.
  • Stopping at launch. Without Reinforcement, people slide back to the old way within weeks. Plan how the change becomes the default.
  • Guessing instead of asking. Your own view of where people are is often wrong. Ask them, and watch what they do.

Template

Copy this for each team or person and fill it in after you have talked to them.

Change:                          Team / person:              Date:

Stage           | Evidence (what they say and do) | Yes / Partly / No | Action | Owner
----------------|---------------------------------|-------------------|--------|------
Awareness       |                                 |                   |        |
Desire          |                                 |                   |        |
Knowledge       |                                 |                   |        |
Ability         |                                 |                   |        |
Reinforcement   |                                 |                   |        |

First gap (where they are stuck):
Check again on:
Source
Prosci
Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close