Communicating organisational change to your team is a deliberate, multi-channel process of explaining why a change is happening, what it covers and when — before, during and after rollout. Unlike a one-off announcement, good change communication answers “what does this mean for me” as many times as it takes for a team to move from resistance to engagement.
Quick Overview
What you’ll learn:
- Why communicating organisational change to your team determines whether a rollout succeeds
- How the ADKAR model helps you plan communication in stages instead of one announcement
- A 6-step change communication plan — from stakeholder mapping to measuring understanding
- A table comparing change communication channels by reach and depth of message
- The most common mistakes managers make when communicating change to a team
Who this article is for:
- Managers and team leads running an organisational change rollout
- HR and internal communications teams supporting transformations
- Project and change managers responsible for change adoption
Reading time: 6 minutes
Why Communicating Organisational Change to Your Team Determines Rollout Success
Organisational change — a new system, a restructure, a merger, a new process — doesn’t end the moment leadership makes the decision. It ends only once people actually work the new way, day to day. Between those two moments sits communication. McKinsey & Company’s analysis of organisational transformations repeatedly points to a widely cited finding that most large transformation programmes fall short of their targets, and one recurring reason is communication limited to a single announcement rather than an ongoing process. Prosci, a research firm specialising in change management, has for years pointed to active, visible sponsorship by leadership — communicated explicitly and regularly — as the factor most strongly correlated with project success in its recurring “Best Practices in Change Management” reports.
The problem isn’t a lack of a message. It’s the message’s form: a one-off email from leadership doesn’t build understanding, doesn’t address individual teams’ concerns, and leaves no room for questions. A team that doesn’t understand “why” starts filling the gap with its own interpretation — usually worse than reality.
Communicating Organisational Change to Your Team — the ADKAR Model as a Starting Point
The ADKAR model (Awareness, Desire, Knowledge, Ability, Reinforcement), developed by Prosci, describes five stages an individual employee moves through before fully adopting a change. The key consequence for communication: each stage needs a different message, sent at a different moment — one universal email can’t serve all five at once.
| ADKAR stage | Employee’s question | Communication’s role at this stage |
|---|---|---|
| Awareness | Why is this happening? | Explaining business context and the risk of not changing |
| Desire | What does this mean for me? | Showing personal impact, addressing concerns directly |
| Knowledge | How do I do this? | Instructions, training, reference materials |
| Ability | Can I actually apply this? | Coaching, practice, support in the first weeks |
| Reinforcement | Will this stick? | Highlighting early wins, correcting relapses into old habits |
A message sent at the Awareness stage won’t satisfy a need at the Knowledge stage — this is one of the most common reasons teams “know something is changing” but don’t know what, concretely, to do differently come Monday morning.
A 6-Step Change Communication Plan
- Map stakeholders and their questions — before writing the first message, work out which teams the change touches directly, which indirectly, and what questions each group will actually ask.
- Build the “why” narrative before the “what” timeline — people accept difficult changes faster when they understand the business context, even if they disagree with it, than when they receive only a task list.
- Match the channel to the ADKAR stage, not the sender’s convenience — an Awareness announcement can go out by email, but Knowledge needs a workshop or documentation, and Ability needs direct manager support.
- Give room for questions before announcing a rollout date — a one-way message with no feedback channel (Q&A, consultations with team leads) breeds resistance, because people have nowhere to route their concerns.
- Repeat the message at least three times, through different channels — a single announcement gets lost in the daily flood of information; the same message delivered at a town hall, in a follow-up email and in a 1:1 with a team lead together reaches a far larger share of the organisation.
- Measure understanding, not just delivery — a short survey asking “do you know what’s changing and why” after each round of communication shows where the understanding gap still exists, before it turns into resistance on the floor.
The Most Common Change Communication Mistakes
Three mistakes keep coming back in rollouts that end in quiet sabotage instead of adoption. First: communication that comes only from leadership, without involving direct managers — employees trust their team lead more than a corporate announcement, and Prosci consistently identifies the direct manager as the preferred source of information about changes to day-to-day work. Second: focusing on the “what” (the new system, the new process) while skipping the “why” — Kotter’s classic “Leading Change” describes building and communicating a clear vision of change as one of the eight critical steps of transformation, and skipping it is one of the most common reasons transformations fail. Third: silence after the first announcement — a communication gap between the decision and the rollout creates a vacuum a team fills with rumours.
Read Also
- The ADKAR Model for Organisational Change Management: Where to Start From Zero — the full ADKAR model step by step, not just in a communication context
- Organizational Culture: How to Understand and Shape It — how change communication fits into a broader organisational culture context
Build Your Skills
This topic connects to the Adaptation in the project - strategies for effective change management course. Check the program and sign up to build your skills with EITT’s experts.
Frequently Asked Questions (FAQ)
Who should communicate change to a team — leadership or the direct manager?
Both, in different roles. Leadership communicates the business context and the decision (the Awareness stage), while the direct manager explains what the change concretely means for that specific team and provides support at the Knowledge and Ability stages. Leaving the direct manager out of the communication chain is one of the most common mistakes.
How many times does a change message need to be repeated to land?
In practice, at least three times, through different channels and in different formats — a single announcement gets lost in the daily flood of information. A town hall, a follow-up email and a 1:1 with a team lead together reach a far larger share of the organisation than any single channel alone.
How do you measure whether change communication actually worked?
With a short survey after each round of communication that checks not just delivery but real understanding: does the employee know what’s changing, why, and what to do differently. The gap between “I heard about the change” and “I understand what I need to do differently” is the most common point where communication stops too early.
Does change communication end on rollout day?
No — the Reinforcement stage of the ADKAR model calls for communication that continues after go-live: highlighting early wins and correcting relapses into old habits. Teams that stop communicating on rollout day most often see a slow drift back to the old way of working within a few weeks.