Insights / Article / Change management and implementation training
ArticleCommunicating change so people listen
Good change communication answers four questions: why, what, when and what it means for me. Most announcements only answer the second.
Most change announcements are written by the people who designed the change. They describe what is happening in detail, often with enthusiasm, and assume that understanding will follow. Then the project team is surprised when people seem confused, anxious or quietly resistant.
The problem is usually not the change but the communication. Good change communication answers four questions: why are we doing this, what exactly is changing, when will it happen and what does it mean for me. Most announcements answer the second question well and the others poorly, if at all.
Start with why
People accept difficult change more readily when they understand the reason. Without a reason, change looks arbitrary, and arbitrary change invites suspicion. With a clear reason, even unwelcome change can feel fair.
The reason needs to be specific and honest. Improving efficiency is not a reason people can relate to. Our current system will no longer be supported after next year, and we cannot risk running finance on it, is. So is: customers are waiting too long for quotes, and we are losing orders to competitors who respond faster. A specific reason gives people something to evaluate, and most will accept it if it is true.
Be honest about costs
If a change will make some jobs harder, at least for a while, say so. People notice the costs anyway, and acknowledging them openly builds more trust than a message that only lists benefits.
Make it personal: what it means for me
The question every person asks, whether or not they voice it, is what this means for them. Will my job change? Will I need to learn something new? Will I still have a job? Until that question is answered, people struggle to hear anything else.
Answering it requires knowing how the change affects each group, which is why a change impact map by role is so useful. With one in hand, you can tailor messages: for this team, the main change is a new approval screen; for that team, the way you receive orders will change completely, and here is the support you will get.
Where the answer is not yet known, say so, and say when it will be. We have not finalised the new team structure; we will share it by the end of next month, is far better than silence, which people fill with rumour.
Be clear about what and when
Once the why and the personal impact are clear, the detail of what and when lands more easily. Keep it concrete. Describe what will be different on a typical day, show the new screen or form, and give dates that people can plan around.
- Use a simple timeline with the few milestones that affect people directly: training, go-live, the end of the old way.
- Distinguish firm dates from estimates, and update people promptly when dates move.
- Avoid project jargon; describe changes in the language people use for their work.
- Repeat key messages. People need to hear important information several times before it sticks.
Use several channels, each for what it does best
No single channel does the whole job. Combine leaders’ voice, team meetings, written notes and demonstrations, and use each for what it does best.
- Senior leaders explain why and show commitment. Their visible support signals that the change matters.
- Line managers translate the change for their team and answer questions. Most people trust their direct manager more than any other source.
- Written notes and an intranet page give a reference people can return to.
- Demonstrations and short videos show what the change looks like in practice, which reduces anxiety about the unknown.
Line managers deserve particular attention. They are often expected to cascade messages they have only just heard themselves, with no chance to ask questions first. Brief them before their teams, give them a short pack with the key messages and likely questions, and tell them what to do when they do not know an answer.
Get the sequence right
Who hears what, and in what order, shapes how a message is received. People who learn about a change affecting them from a colleague, a rumour or an external source feel bypassed, and that feeling colours everything that follows. A simple sequence avoids most of these problems.
- The leadership team agrees the core messages and the answers to the hardest questions.
- Line managers and team leaders are briefed, with time to ask their own questions.
- The groups most affected hear directly from their manager, ideally in person, before any wider announcement.
- The wider organisation receives the general announcement and the reference material.
- External parties, such as customers, suppliers or partners, are told once employees know.
Keep the gap between steps short, ideally within the same day or two, so the news does not leak out of order. For sensitive changes involving roles or locations, take advice on any consultation obligations before the sequence begins.
Listen and respond
Communication is a conversation, not a broadcast. Collect questions and answer them openly. Set up simple ways for people to ask: a shared inbox, a question slot in team meetings, drop-in sessions with the project team or an anonymous form for the questions people are reluctant to ask in public.
Publish answers where everyone can see them, grouped by theme and updated regularly. When the same question comes up repeatedly, it usually means a message has not landed and needs to be explained differently. When a question reveals a genuine flaw in the plan, fix it and say so. Few things build credibility faster than visible evidence that feedback changed something.
The turning point was when we published every question we had received, with answers, including the awkward ones. People stopped assuming we were hiding things.
HR director, professional services client
A simple plan to start with
Before your next change announcement, write one paragraph for each of the four questions. Brief line managers a day before their teams hear the news. Plan at least three channels and a way for people to ask questions. Then check after two weeks what people have understood, and adjust the messages that have not landed.
Source: Intelliversal analysis.
