A change rollout is everything a manager does between the decision to change something and the day people work the new way without being reminded. Most of that work sits before the announcement and after the launch. The announcement itself is the shortest part of the sequence, and the part that absorbs almost all the attention.
Quick Overview
What you’ll learn:
- How to map the people a change will affect before anyone hears about it
- Which group needs your attention first, and which needs almost none
- Where the individual side of change is covered, and why this article does not repeat it
- What a communication calendar looks like when it is written down in advance
- How to pick an early, visible win that buys you attention
- Which levers hold a change in place once the novelty wears off
Who this article is for:
- Managers announcing a change they did not design
- Team leads who have to make an all-hands message concrete
- Project leads answerable for adoption rather than for delivery
Reading time: 8 minutes
Map the Ground Before You Announce Anything
Before you say anything about a planned change, do the work of a strategist and understand the human terrain you are about to operate in. Every change splits an organisation into camps — enthusiasts, sceptics, open opponents — and the split rarely follows the org chart. Acting without knowing where those lines fall is how a well-designed change dies in its first week.
The tool for this is a stakeholder map drawn on two axes. On the vertical axis put a person’s influence in the organisation, from low to high. On the horizontal axis put their likely attitude to this specific change, from firm opponent to committed supporter. Place every key member of your own team and of the teams next to yours.
Two habits make the map useful rather than decorative. Name individuals, not functions: “finance” has no attitude, but the person who owns the monthly close does. And write it down, because a map held in your head quietly rearranges itself to match what you hope will happen.
The choice of axis matters. A map built on power and interest — the version most project methods teach, set out in the article on stakeholder management in IT projects — answers a different question: who needs which reporting cadence. Attitude is what you need here, because what you owe an opponent is not what you owe someone merely uninformed.
The Four Groups, and What Each One Needs
The map produces four quadrants, and each one takes a different kind of effort.
High influence, in favour — your promoters. Bring them in before the announcement, not after it. Ask for their reaction to the plan and change something in response to it; a person who has altered a decision defends it afterwards. These are the people who carry the change into rooms you are not in.
High influence, against — your critics. This is the real risk, and the instinct to route around them is the wrong one. Meet them one to one and let them talk first. The goal of that conversation is not agreement by the end of it; it is a critic who can say their objection was heard and answered. An objection that never got a hearing comes back later dressed as a process problem.
Low influence, in favour — your allies. Keep them well informed and slightly ahead of everyone else. An early look at what the change fixes costs nothing and turns quiet approval into visible approval, which is what shifts the mood of a room.
Low influence, against — your sceptics. Spend the least time here. Their complaints are real and their leverage is not, and ordinary communication plus visibly enthusiastic colleagues moves most of them without a dedicated conversation. Attention spent here is attention taken from the critics.
Read the map as a plan for where your attention goes, not as a scoreboard. People move between quadrants as the change proceeds, and the ones who move are the useful signal: a promoter who has gone quiet has learned something you have not.
Where the Individual Side of the Change Sits
The map tells you who to talk to and in what order. It does not tell you what each of those people has to go through, and that is a separate question with a well-established answer.
The Prosci ADKAR Model describes that journey as five sequential stages, and it works as a diagnostic as much as a plan: when someone is stuck, the stage they are stuck at determines what would help. This article deliberately does not restate it — the stages, the diagnostic question for each of them, and where to begin are set out in the article on the ADKAR model and where to start from zero.
What follows here is the rest of the job: the sequencing and communication work a manager does around that journey.
The Communication Calendar
Communication in a change is a campaign, not a message. Its job is to get people to the point where they understand why the change is happening and want it to succeed; everything after that depends on training and practice. A campaign nobody wrote down in advance turns into a sequence of reactions to whatever leaked first.
For example, a ten-day sequence around an announcement:
- Day -7, brief the promoters. They hear it first and in private, and they are asked for input rather than for support.
- Day -2, brief every manager. They need the message, the answers to the hard questions, and enough time to stop being surprised by it in front of their own teams.
- Day 0, announce it. An all-hands led by the sponsor rather than by you, followed the same day by a written summary and a place where questions can be asked.
- Day 1, team meetings. This is your part. You translate the organisational message into what it means for these people and this work, and you take the questions nobody asked at the all-hands.
- Day 3 to 5, open sessions. Scheduled time when you and other leaders are available for whatever is unresolved.
- Day 10, first progress report. Show that the change is already happening, starting with the first thing that has visibly improved.
The ordering carries the principle. Nobody should learn about a change affecting their own work from a crowded all-hands, and no manager should be asked to explain a decision they heard about the same morning. Practical patterns for running the campaign itself are covered in the guide to communicating organisational change to your team.
Find One Visible Win Early
A change usually arrives as an abstraction: a new system, a new structure, a new process, none of which anyone has touched yet. Abstractions are easy to resent. The counter is to put one concrete, small improvement in front of people while the announcement is still fresh — roughly the first seventy-two hours, before opinions have set.
The way to find it is to ask which small, genuinely irritating thing this change removes. A report somebody compiles by hand every week. An approval that takes longer than the decision is worth. A form asking for information the system already holds. Whatever it is, sequence it first, even when it is not the most valuable part of the change.
What a quick win buys is attention, not agreement. It gets people to treat the change as something that might help them rather than something being done to them, and that is the condition for the training and practice that come next. Teams that skip it spend the same effort later, arguing about whether the change was worth starting. The mechanics of leading that first phase are the subject of dedicated work on change and change management.
Making It Stick: Four Levers
Reinforcement is the phase managers forget, and it is the one that decides whether the change survives. Novelty fades, old habits are strong, and a change nobody actively holds in place drifts back. Four levers do most of that holding.
Recognition, specific and public. Notice the new behaviour out loud. When someone uses the new process well, say so at the time; when someone reports a result they got from it, stop the meeting and name it. Catching people doing the right thing is unglamorous, and it is the cheapest instrument available to you.
Milestones worth marking. Do not wait for a finish line at the end of the programme. Break the rollout into stages people can actually reach, and mark each one when it arrives, because a sense of progress is what carries a team through the unrewarding middle of a change.
Removing the old path. This is the strongest lever and the least used. Make the new way objectively easier than the old one: switch the old system off, stop accepting the previous report format, close the workaround. Every door left open to the earlier habit is an invitation to walk back through it, and somebody will.
Aligning the formal systems. Check what the organisation actually rewards. If objectives, bonuses and appraisal criteria still measure the old behaviour, people will follow the incentive rather than the announcement, and they will be right to. A change that contradicts its own reward system loses to it.
The order is deliberate: the first two hold attention, the last two remove the option of going back. Managers reliably do the first two and skip the last two, which is why so many changes survive a quarter and not a year. A fuller treatment of moving a team from resistance to engagement is in the article on change management from resistance to engagement.
Build Your Skills
Running a change well is a sequence of ordinary decisions made in the right order, which means it is learnable rather than innate. Our trainers work through it on the changes your organisation is actually about to make.
➡️ Change Management for Managers and Leaders — EITT training
Frequently Asked Questions (FAQ)
Who should announce the change, the manager or the sponsor?
The sponsor announces it and the manager makes it concrete. A decision of organisational weight delivered by a team lead reads as a decision nobody senior wants to own, and the questions that matter get asked in the team meeting the next day anyway.
What do you do with a critic who will not move?
The objective shifts from persuasion to containment. A critic whose objection has been heard, answered and visibly considered rarely campaigns against the change; a critic who was routed around does. You are buying neutrality, not enthusiasm.
Does this apply to small changes, or only to transformations?
The same sequence applies and simply compresses. A new tool in one team runs through the same stages as a restructuring, only faster. The mistake is skipping stages because the change feels too small to warrant them.
How is this different from Kotter’s model?
Kotter Inc. sets out The 8 Steps for Leading Change as the sequence an organisation moves through. What this article covers is the manager’s part of that sequence, and ADKAR covers the individual’s. The three are complementary rather than competing.
What should you look at when a change stalls after the first month?
Look at which lever is missing rather than at people’s attitude. A stall almost always traces back to the old path still being open, or to a reward system that still measures the previous behaviour. Neither is fixed by more communication.