Change communication that survives the fourth email
Every transformation programme has a communication plan. Most of them fail in the same place: the fourth message, when people have stopped opening the ones before it.
Why change communication fades halfway through
The plan is rarely the problem. The channel is.
Announcement fatigue is real
By the third project email, open rates collapse. The programme is still running but its communication has effectively stopped, and no one notices until adoption figures come in.
Everyone gets the same message
A migration affects different teams on different dates. A single all-staff email is either too early for some or too late for others, and irrelevant for most.
Deadlines slip quietly
"Move your files before Friday" sent once, ten days ahead, is not a deadline. It becomes one when the reminder appears on the screen the day before.
A rhythm, not a broadcast
Change communication works when it is sequenced by audience and repeated without becoming noise.
Sequence by wave, not by company
Target the OU or machine group being migrated this week. The next wave gets the same message on its own date, from the same saved template.
Alternate insistence and presence
The announcement is a pop-up. The countdown to the deadline is a ticker running all week. The final reminder is a pop-up again, with acknowledgement.
See who is actually following
Acknowledgement rates per group tell you which teams read the instruction and which need a floor visit — before the migration weekend, not after.
A deadline reminder that does not interrupt
A ticker anchored at the bottom of the screen: present all week, never in the way.
The sequence that works
Four messages, four formats, one saved template set.
- Announcement
- Pop-up to the wave concerned, with the date, the reason and the one thing they must do. No attachment, no forty-line email.
- Weekly countdown
- Ticker running for the duration, three passes a day. It keeps the deadline present without a fifth email.
- Final reminder
- Pop-up with mandatory acknowledgement, the day before. This is the one that produces the last-minute compliance.
- Go-live and support
- Ticker on the morning itself with the helpdesk number, then a short pop-up confirming the change is complete.
Frequently asked questions
How is this different from just sending more emails?
Frequency is not the problem; visibility is. A ticker sits on the screen without requiring an inbox visit, and a pop-up cannot be scrolled past. You send fewer messages, not more.
Can different sites get the message on different dates?
Yes. Schedule the same template several times, each targeted at the group migrating that week. The wording stays consistent while the timing follows the plan.
Can the communications team send without IT doing it for them?
Yes. Rights are scoped by team, so a change manager can prepare and send to their own perimeter, optionally through a validation step, without an administrator account.
See Nuntivo on your own screens
15-day free trial, no credit card. 10 PCs included.