What a communication plan is for
A communication plan for a change sets out who needs to hear what, from whom, when and through which channel, and how the project team will hear back. It is a modest document, often a table, but it forces decisions that would otherwise be made in a hurry: who tells the affected teams first, what is said when details are still uncertain, and where questions go.
Without a plan, information tends to leak out unevenly. Some people learn of a restructuring from a hallway conversation, others from an email sent to the wrong list, and managers find out at the same time as their teams. A plan will not remove every awkward moment, but it makes the main ones less likely.
Start with audiences
Different groups need different things, and lumping them together produces messages that suit nobody. A typical breakdown includes:
- Sponsors and senior leaders, who need progress, risks and decisions.
- Middle managers, who need advance notice and enough detail to answer questions from their teams.
- Directly affected staff, who want to know what changes in their work and when.
- Indirectly affected staff, who interact with the changed area and may notice effects without being told.
- Customers, suppliers or partners, where the change touches them.
- Support and technical teams, who will field problems.
Identifying these groups is easier after stakeholder mapping, which also reveals who is likely to be anxious and who has influence over how the message is received. Each audience can then be given its own entry in the plan.
Decide what to say at each stage
Messages usually fall into stages, and the content shifts as the change progresses.
Before the announcement. Prepare the reasons for the change, the facts that are settled, and the questions that are still open. A message that explains the reasons honestly, as discussed in building an honest change case, is easier to defend later than one that only lists benefits.
At the announcement. Say what is happening, why, what it means for each group, what is still undecided, and where to ask questions. Avoid promising things that are not yet confirmed.
During preparation and rollout. Provide steady, brief updates: what has been done, what is next, what people need to do and by when. Regular updates are useful even when the news is that nothing has changed, because silence is often interpreted as a problem.
At go-live. Give practical information: how to get help, what to do if something fails, which known issues exist. This is the point at which the help desk experience matters most, so support staff should hear the message before everyone else.
After launch. Share what is being learned, what is being fixed and what has been decided in response to feedback. Showing that earlier input led to a visible change is one of the better ways to keep people engaged.
Choose channels with care
No channel suits every purpose. Rough guidance:
| Purpose | Often suitable channels |
|---|---|
| Sensitive news about roles or reporting lines | Face-to-face or direct conversation, led by the line manager, followed by written confirmation |
| Factual updates and dates | Email, intranet page, short newsletter |
| Explaining a new process | Demonstrations, short videos, written guides |
| Questions and discussion | Team meetings, drop-in sessions, a shared question board |
| Urgent operational notices | A channel people already watch during work, such as an agreed messaging tool |
Two principles are worth keeping in mind. First, important messages usually need repeating through more than one route, since people miss emails and forget meetings. Second, news that affects someone’s job should not be delivered by a mass message before they have heard it personally. Where managers are the messengers, they need to be briefed in advance, which ties communication closely to supporting managers through restructuring.
Build in two-way feedback
A plan that only broadcasts is incomplete. Feedback gives the project team an early view of misunderstandings, practical problems and morale. Options include:
- a dedicated mailbox or form for questions, with a promise about response time;
- regular question-and-answer sessions with project leads;
- short pulse surveys at agreed points, kept brief and focused on a few questions;
- reports from change champions who hear informal views;
- reviewing support requests for patterns that suggest confusion.
Feedback only helps if something happens to it. Decide who reads it, how often, and who can act. Publishing the common questions with answers is a simple and effective step; it reduces repeated queries and shows that questions are taken seriously. If a concern cannot be addressed, say so and explain why, rather than leaving it unanswered. Unanswered questions often return later as change resistance.
Timing and frequency
There is no formula for how often to communicate, but a few habits help.
- Set a regular rhythm, such as a short update every two weeks, and keep to it. A predictable pattern is easier to follow than occasional bursts.
- Increase the frequency near the points of greatest disruption, such as just before and after go-live.
- Avoid overloading people. If every minor milestone triggers an email, important messages get lost.
- Tell people about delays or changed plans promptly, not when they find out for themselves.
Dates quoted in communications should be ones the team is reasonably confident in. If a date might shift, say so and explain what it depends on.
Roles and approvals
A plan should name who writes each message, who approves it, and who sends it. Without this, messages are delayed by uncertainty over sign-off, or inconsistent versions circulate. For sensitive items, agree in advance who may speak to which topics so that different leaders do not give conflicting answers. A short list of approved key messages and answers to likely questions helps keep wording consistent without making everything sound scripted.
Checking that it works
Communication cannot be judged by how much was sent. More useful checks include asking a sample of affected people to describe, in their own words, what is changing and what they need to do; looking at whether the same questions keep recurring; and noticing whether managers feel prepared. These are informal measures, but they reveal gaps more quickly than counting emails. Longer-running signals such as employee engagement survey results can also show whether people feel informed, although they are influenced by many factors besides communication. Where the plan is not working, change it. A communication plan is a working document and is expected to be revised as the change develops and as people respond.
Common mistakes
- Treating a single launch announcement as the whole plan.
- Using jargon from the project team that the audience does not share.
- Telling managers last.
- Sending reassurance that later turns out to be wrong.
- Ignoring questions that are awkward to answer.
- Stopping communication after go-live, just when new users are most likely to struggle.
A plan that avoids these will not guarantee smooth acceptance, but it gives people a fair chance to understand what is happening and to be heard.