Change Adoption Lab

Plan a change rollout that every team will actually support.

Change Adoption Lab

What this fixes

Different teams experience the same change in different ways. A single rollout, sent to everyone the same way, leaves some teams behind and creates resistance you didn’t expect.

The rollout doesn’t fail because people dislike the change. It fails because different groups needed different things to adopt it, and everyone received the same rollout.

How this works

Your company introduces a new AI development workflow. Engineering teams welcome it because it removes repetitive work. Security teams worry about compliance. Delivery managers fear short-term productivity will fall during adoption. HR wants everyone trained before launch. Announce the change the same way to all of them, and adoption slows - because each group needs something different.

In this activity, you plan the rollout one group at a time: how each group experiences the change, where they’ll resist, what they need before they’ll support it, and the one adoption move that will help them get there. You finish with one rollout plan built from many.

Create one column for every group affected by the change. Work through each group completely - how they’ll experience the change, where they’ll resist, what they’ll need, and the adoption move that addresses it. When every group is complete, read the grid across to create one rollout plan.

Team: one person acts as the facilitator - they run the activity using the Facilitator Guide while everyone else takes part.

Time required

Solo ✓    Team ✓

Solo: 45–60 minutes.    Team: 60–90 minutes.

The time required is indicative and will depend on the nature of the problem and the size of the team.

The facilitator should read the short facilitation guide first - about 10 minutes. It’s a downloadable PDF on this page.

When to use

Bring one real change you’re about to roll out - a reorganisation, a new system, a new process, a new way of working. The tool works best on a live rollout, not a hypothetical one.

Use it whenever:

  • you’re planning a change that several different teams will have to adopt
  • a past rollout stalled because some groups never got on board
  • you can already sense some teams will take the change harder than others
  • you’re about to send one announcement to everyone and want to be sure it’s received the way you intend

What you get

  • A rollout plan with a different adoption strategy for every affected group
  • The likely resistance from each group, named in advance
  • One specific adoption move per group

You’ve done it well when: every affected group has its own adoption move and no group is left on the default plan.

What you’ll notice

  • The “one change” was really several different changes
  • Resistance starts to look predictable, not personal
  • The plan gets sharper as it gets more specific

Why this works

The same change creates different gains, losses and uncertainties for different groups. Planning one rollout for everyone assumes they all need the same thing. They don’t. Planning each group separately makes adoption much more likely.

What you need

A change brief. A short, plain statement of the change you are rolling out. Write it before you start.

The group grid. A worksheet or a whiteboard with one column for each affected group.

A few markers. For filling in the grid.

Capture space. To record the finished rollout plan.

Roles - Team only: a facilitator and participants.    Solo: you run it yourself from this page.

Steps

  1. Set up. Team: appoint a facilitator first - they run the activity from the Facilitator Guide. Solo: just begin. Draw the grid and write your change brief at the top.
  2. Name the groups (5–10 min). List every group the change affects - by team, role or function. One column each. Be specific: “front-line support”, not “staff”. Don’t combine groups that experience the change differently.
  3. See it through their eyes (10–15 min). For each group, write how the change will actually be received - what they gain, what they lose, what they have to do differently. Do one group completely before the next.
  4. Name the most likely resistance (8–12 min). For each group, write the most likely reason they will resist.
  5. Identify the adoption need (8–12 min). For each group, write what would have to be true for them to support the change - the proof, support or involvement they would need.
  6. Design the adoption move (10–15 min). For each group, create the smallest adoption move that directly addresses that group’s biggest need - who does it, and when. One move per group, minimum.
  7. Assemble and commit (5–10 min). Read the grid across as one rollout plan. Give every adoption move an owner and a date. If two groups receive exactly the same adoption move, check whether you’ve understood their needs well enough. Photograph it and send it to everyone before you leave.

Output / Takeaways

  • A differentiated rollout plan - one approach per group, written down
  • Every adoption move has a named owner and a date
  • A record you can work from as the rollout unfolds - and what you’ll do differently from the last one

Important rules

  • One column per group - never plan for “everyone”
  • Finish one group before starting the next
  • Every group gets at least one adoption move
  • No move leaves the room without an owner and a date
  • Different needs deserve different rollout moves - if every column looks the same, start again

Planning to facilitate this activity? Access the resources below to get started.

MIndn
Execution must be smooth. Not chaotic or stressful.
Built by Witmer.