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.
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.
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.
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’ve done it well when: every affected group has its own adoption move and no group is left on the default plan.
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.
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.
Output / Takeaways
Important rules
Planning to facilitate this activity? Access the resources below to get started.