Use this whenYou’re about to roll out a new system, process, or way of working, and you need people to actually adopt it.

Inspired by Prosci’s ADKAR model. I use its five outcomes as the spine and add the pieces I’ve seen decide whether a rollout sticks, a readiness check before anything starts, an executive who visibly drives it, and communication treated like a launch.

Why it exists

Most rollouts are planned around the system, not the people. The project hits its go-live date, the kickoff goes well, and six months later half the organization is still on the old spreadsheet. Change happens one person at a time, and each person has to get through the same few outcomes in order. Skip one and the rest don’t hold.

The framework

  1. Step 1AwarenessDo people know why this is changing?
  2. Step 2DesireDo they want to be part of it?
  3. Step 3KnowledgeDo they know how?
  4. Step 4AbilityCan they do it in their real work?
  5. Step 5ReinforcementWhat keeps it from sliding back?
  1. Awareness

    Do people know why this is changing?

    Not what is changing, why. People need to see the problem the change solves, in terms that matter to their own work. This is where the burning platform and early communication do their job.

  2. Desire

    Do they want to be part of it?

    Knowing why doesn’t mean wanting to. Desire comes from leaders who visibly back the change, from seeing peers succeed, and from a reason that is personal. Gamification and recognition help here.

  3. Knowledge

    Do they know how?

    The steps, the tools, and where to get help. Knowledge is the part most rollouts overinvest in, through kickoffs and seminars, and it fades fast without practice.

  4. Ability

    Can they do it in their real work?

    Knowing how in a training room isn’t doing it on a busy Tuesday. Ability comes from hands-on practice, office hours, and a trainer down the hall. Train the trainer lives here.

  5. Reinforcement

    What keeps it from sliding back?

    Recognition, visible measures, leaders who keep asking, and retiring the old way so there is nothing to slide back to. The leaderboard lives here.

How to use it

  1. Run a change readiness assessment before you plan anything else. If the organization can’t absorb the change right now, the plan won’t fix that.
  2. Name the executive sponsor and agree on what they will visibly do, not just approve.
  3. Build the communication plan at the same time as the project plan, not after it.
  4. For each group affected, ask which of the five outcomes they have reached. Start where they are stuck, not where the project is.
  5. Choose how you will create motivation, the burning platform, gamification, or both.
  6. Teach through practice and through trainers inside each team, then reinforce until the old way is gone.

Two things that run the whole way

  • An executive sponsor who keeps showing up. Early on they explain why. Later they ask how it’s going, in their own staff meetings, by name.
  • Communication. It starts before the first decision is announced and keeps going well after go-live.

Where rollouts usually stall

  • Jumping straight to knowledge. Training people who don’t yet see why is the most common waste in change management.
  • Declaring victory at go-live. Reinforcement is the step most often skipped, and the one that decides whether the change lasts.
  • Treating the organization as one audience. Different teams will be stuck at different outcomes.

What it looks like

Picture a company replacing its project tracking spreadsheets with a shared system. A readiness check shows two other rollouts landing the same quarter, so the launch moves back a month. The COO records a short video on why the spreadsheets are costing them, and opens every staff meeting with the adoption numbers. Each team gets a trainer from its own ranks, office hours run weekly, and the spreadsheets go read-only on a date everyone knows in advance.

Where it breaks down

The five outcomes describe what has to happen inside each person. They don’t tell you how long it takes, and they don’t replace knowing your people. Large changes can have people at every stage at once. The model also assumes the change is worth making. If it isn’t, no amount of change management will save it.

Try it with AI

Help me plan the people side of a change I'm rolling out. Use five outcomes, in order.

1. Awareness. Do people know why this is changing?
2. Desire. Do they want to be part of it?
3. Knowledge. Do they know how?
4. Ability. Can they do it in their real work?
5. Reinforcement. What keeps it from sliding back?

Ask me one question at a time about the change, who it affects, and who is sponsoring it. Then tell me, group by group, which outcome each is likely stuck on and what to do about it. Flag anything that suggests we should run a readiness check before going further.

Related