Change Communication Plans That People Actually Read

Oct 23 / Marc-André Rochefort

Version française : Construire un plan de communication du changement vraiment lu

Key takeaways

  • A change communication plan people actually read starts from the action each group has to take. It also names the right messenger for each group and a way to check the message landed.
  • A send calendar lists the date, channel, audience and subject line. It says when a message goes out, not what the reader should do next.
  • Segmenting the plan by required behavior rather than by org chart usually produces fewer, more targeted messages.
  • A shift in daily process generally lands better from the direct manager, while the executive sets direction and explains why the change matters.
  • When there's nothing new to announce, send a short holding message. Naming the current phase and dating the next update protects the channel better than silence.
  • Open rates and attendance measure delivery, while manager check-ins and recurring questions show whether people understood what changes in their own task.

A change communication plan built as a send calendar tells you when an email goes out, and that's about all it tells you. It doesn't say what anyone should do differently, who they should hear it from, or what to send when nothing is new. So build the plan around required action instead, and pick the right messenger for each group. Add a way to check the message landed, and you get a different document: one that changes behavior rather than filling inboxes.

Why isn't a send calendar a plan?

Open most templates labeled "communication plan" and you'll find a grid of date, channel, audience and subject line. The grid answers when something gets sent. It doesn't answer what the reader is supposed to do afterward. Once the change needs people to act, that's the only question that matters. You can fill every cell and still fail. Filling cells is different work from deciding what each audience needs to hear before it will move.

Results expose the gap first. Teams report that the newsletter went out and the town hall was well attended, yet adoption still lags. The plan measured activity on the sending side, but it never checked whether the message changed what the reader meant to do next.

Informing people and moving them to act are different jobs

A status update tells people what's happening, but on its own it doesn't tell them what to do differently on Monday morning. Both belong in a plan. Confusing them is where most communication effort gets wasted. Teams spend their budget on frequent, polished status updates and assume that enough information will eventually turn into action.

It won't, not by itself. A message meant to move someone needs a specific ask, framed around what changes in their own workflow. It also needs enough detail that they can act without coming back with a follow-up question. A message meant to inform can be broader and sit further from the reader's daily task. Put both through one channel, in one tone and at one cadence, and the plan ends up doing neither job well.

Segment by what each group has to do differently, not by org chart

The default is to segment by org chart, with one message for leadership, one for managers and one for frontline staff. That follows reporting lines, not what any group is actually being asked to change. Two departments in completely different reporting chains may need the identical message, because the change hits their daily task the same way. Two teams under the same VP may need entirely different ones, because one team's workflow shifts and the other's doesn't.

Start from the action, not the audience. List every distinct behavior the change requires, then group the people who have to perform each one. If you've already done a stakeholder analysis, start from it and add one column for the behavior each group has to change. A team that only needs to know a system has been renamed gets a short notice. A team whose approval workflow is being rebuilt gets specific steps, a date and a named contact for questions. Built this way, the plan usually produces fewer, more targeted messages than the org chart would. It stops treating "everyone in the department" as one audience when only half of them are affected.

Who delivers the message matters more than most plans admit

The messenger changes how a message lands more than almost any wording choice. A shift in daily process generally lands better from the direct manager than from an executive several levels up. That's because the direct manager is the person whose expectations the recipient has to meet day to day. The executive sets direction and explains why the change matters for the organization. The direct manager is the one who can answer "does this apply to me from this week?" credibly and on the spot.

Plans that route every message through the top of the organization are optimizing for the sponsor's visibility, not for the message landing. We'd push action-level messages down to direct managers and keep executive communication for direction and rationale. Where managers need backup, a network of change champions can relay the same message closer to the work. That split tends to produce faster behavior change, because it matches each messenger to the kind of trust the message needs.

Cadence, and the point where people stop reading

Send weekly updates whether or not there's anything new, and you train your audience to stop opening them. Communication fatigue is less about volume than about the ratio of substance to noise. Someone opens three updates in a row and finds nothing that changes their task. They learn, correctly, that the fourth is safe to skip.

Sending less on a fixed schedule doesn't fix that. What works is to tie frequency to whether the audience has something to know or do, not to the calendar. When there genuinely is nothing new, you have two honest options. Skip the send, or send a short, clearly labeled holding message that says so and gives the date of the next real update. Either way, the channel keeps its credibility for the update that matters.

What should you send when there's nothing new to announce?

Most plans have no answer here, because they're written as if milestones will arrive in a steady stream. Real change programs have quiet stretches where a phase is underway, nothing has shipped, and the last message already covered the plan.

In those stretches, a short holding message does more for trust than silence or a padded update dressed up as news. It names the current phase and confirms nothing has changed for the reader's task. It also gives a specific date for the next substantive update. Silence reads as the program losing momentum, even when it isn't. A padded update reads as the program having nothing to say, and that damages the channel for the next real announcement.

How do you know whether the message landed?

Counting sends and opens measures delivery, not comprehension. Open rates and attendance figures tell you the channel worked. They tell you nothing about whether readers understood what changes in their own task, or when. What happens after comprehension, which is actual use, is covered in our piece on the adoption metrics that matter.

Direct managers are usually the quickest way to find out. In a short, structured check-in, the manager asks the team to describe in their own words what's changing and when. Gaps in understanding show up there well before a survey would catch them. A second signal comes from the help channel and from managers. Are the questions arriving there the ones the plan already answered? If the same question keeps recurring after the relevant message went out, the message didn't land. That's worth ruling out before anyone reaches for the resistance to change label or concludes the audience isn't paying attention.

Fitting this into the wider change effort

A communication plan built this way doesn't stand alone. It needs a sponsor visible enough for direction-level messages to carry weight. It also needs a clear list of what the program is actually delivering. That way each message is tied to something specific, not a vague promise of progress. Our articles on sponsor visibility and the sponsor roadmap and on core change management deliverables cover the pieces a communication plan has to plug into.

Practitioners who run plans like this as a core part of the job often formalize the skill through structured education. Leanova Academy's 21-hour self-paced CCMP® training covers communication planning as one of the ACMP® Standard process groups. It pairs with the CCMP® practice exam for candidates preparing their application. The full catalog of self-paced and cohort options is on the all courses page.

This article is also available in French: Construire un plan de communication du changement vraiment lu.

Reviewed September 2026. This article cites no adoption statistics, readership benchmarks or research findings, because we found none that Leanova could verify at the time of writing. CCMP® and ACMP® are registered trademarks of the Association of Change Management Professionals.