Did They Understand It? How to Tell a Change Message Landed

The announcement went out on time, the town hall happened, and the FAQ is posted. Then a leader asks, "Did people get it?" Most communicators answer from instinct, a sense of how the room felt or how quiet the inbox has been, and instinct is a poor witness when a reorg is on the line.

You can have a better answer within two days. Run four checks in the first 48 hours (who received the message, who read it, who acknowledged it, and what they asked) and you will know which audiences the message reached and which it missed. Linjuan Rita Men told Ragan in a piece on helping employees make sense of change that "Employees embrace change when they understand it and have a voice in it." Understanding decides whether the change sticks, so it deserves evidence.

Why change communication needs evidence

Gartner research reported in Harvard Business Review found that in 2022 the average employee experienced 10 planned enterprise changes, up from two in 2016. Your announcement lands on people who have heard plenty of them and blurs into the rest.

The usual dashboards won't tell you whether it blurred. Katie Hickman, writing for Ragan about communicating change to frontline employees who don't read email, warns that interaction metrics "can tell you whether people interacted with something," and that "they don't necessarily tell you whether employees understand what is changing." Prosci makes the same argument in its piece on telling versus communicating, where it says, "You need to evaluate if your audience is hearing and properly interpreting the messages you send."

Treat reads as the leading indicator of understanding and the floor you measure first, since no one understands a message they never opened. A read proves that the message was in front of someone, and the three checks after it show what they took from it.

Four checks that show whether a change message landed

Run these in order, since a gap early in the chain makes every later check unreliable.

Received: did it reach every affected audience?

Compare the send list to the roster of people the change affects, site by site and shift by shift. The "all employees" list drifts away from that roster every time the org chart moves, and no read rate rescues a reorg message that skipped the people being reorganized.

Deskless and frontline groups need their own line in this check. Hickman notes of the field-based colleagues in her program that "their workday wasn't organized around checking email or visiting the intranet." For those groups, record which channel reached them, such as a shift huddle or a supervisor, and confirm it happened at every site.

Read: who read it, by audience?

One company-wide read rate hides more than it shows. Break reads out by the audiences the change touches, such as office against frontline and affected against unaffected. A healthy overall number can sit on top of a warehouse shift where almost nobody read a word, and that is often the shift the change hits hardest. Send tools that report reads by audience, including tools like Cerkl Broadcast, make this a quick check you can repeat at hour 24 and hour 48.

A poster or a huddle gives you no read signal. Use a manager confirmation as the stand-in and log it in the same place, so the frontline shows up in your data with a number beside it.

Acknowledged: who confirmed they've seen it?

Some changes carry action or compliance weight, such as a new policy or a benefits enrollment deadline. For those, ask for an explicit acknowledgment, a single click or reply that says "I've seen this," and track it by audience the same way you track reads.

Frontline teams acknowledge through the supervisor, who confirms in the huddle and logs it. Prosci's guidance on change management communication supports that route, noting that "for personal change messages, employees want to hear from their immediate supervisor."

Asked: what questions came back?

Questions are the best comprehension signal you will get. Log every one by theme and audience, whatever channel it came through. If the same question comes from many people, the message failed at that point, and you know which sentence to fix.

Silence from an affected group counts as a signal too. Men describes change communication in the Ragan piece as "helping them make sense of the change and inviting them into the conversation." If nobody in a team that lost its manager this week has asked anything, nobody has started that conversation with them yet.

A 48-hour change communication check after a reorg or policy announcement

Copy this verification window into your change calendar alongside the send plan.

Hours 0 to 4. Check delivery against the affected roster. Fix bounces and missing groups, then confirm the non-email channels went out at every site.

Hour 24. Pull reads by audience with manager confirmations from frontline sites folded in, and sort the first questions into themes.

Hour 48. Report the acknowledgment rate where one is required, and list the audiences still dark or confused alongside the questions each keeps asking. Then hold the result up against Hickman's test, "Do employees understand what they need to do differently?" If you can't answer yes for each affected audience, you aren't done.

Close the gaps before you assume the message landed

If people never received it, fix the list or switch to the channel that group relies on. If they received it and didn't read it, send a second touch through the supervisor or another channel, aimed at the audiences still dark.

A short, direct ask with a deadline closes most acknowledgment gaps, with supervisor follow-up on the frontline. Confusion takes more work. Answer the repeated question in public with the unclear point rewritten, and give managers a one-line version of it so the supervisor conversation carries the same answer. Ask a silent group about the change in the team huddle or with a two-question pulse, and keep that group on your open list until they answer.

What "landed" means for change communication

A change message has landed when every affected audience received it, read it, confirmed it where confirmation matters, and got answers to the questions it raised. Anything short of that is a work list. The next time a leader asks whether people got it, answer with the four checks, audience by audience, plus a list of what you're fixing before Friday.