Why Change Communications Get Ignored
People don't ignore change communications because they're too busy.
They ignore them because past experience has taught them that reading carefully doesn't change outcomes.
The Pattern Recognition Problem
After a few change initiatives, people develop pattern recognition:
"This email means something's changing but I don't need to do anything yet."
"This town hall means they want me to feel included but decisions are already made."
"This FAQ means they anticipated my questions but the answers won't actually help."
They're not being cynical. They're being efficient. They've learned which communications require attention and which are just organizational theater.
You can't undo this pattern by making communications longer, more frequent, or more emotional. You have to break the pattern by making communications actually useful.
The Utility Test
People engage with communications that help them do something they need to do.
"Need to do" might mean:
Prepare their team for what's coming
Make a decision about their own role or priorities
Answer questions they're already getting
Avoid a mistake or problem
If your communication doesn't pass this test, it gets ignored—no matter how well-written it is.
The Timing Problem
Most change communications arrive too early or too late.
Too early: "This might affect you eventually, but you can't do anything about it now, and the details will probably change anyway."
Too late: "This takes effect Monday. Here's a 40-page guide you should have read last week."
Both create the same response: ignore now, hope someone follows up when it actually matters.
Effective communication arrives when people can actually use it...not when it's organizationally convenient to send it.
The Specificity Gap
"We're moving to a new system" is not specific enough to be useful.
"We're moving to a new expense reporting system; you'll need to re-enter your standing approvals by March 15" is specific enough to act on.
Generic communications get ignored because they don't tell people what to do. Specific communications get read because they make clear what's required.
The specificity gap is why organizational announcements get ignored while team-level translations get attention.
What Gets Read
Communications get read when they:
Arrive at the moment people need them
Contain information people can't get elsewhere
Make clear what's required (not just what's changing)
Come from sources people trust to know the details that matter
This means different audiences need different communications at different times.
Sending everyone the same message at the same time guarantees most of it gets ignored.
The Redesign Question
If your change communications consistently get ignored, the problem isn't audience engagement.
The problem is that you're designing communications for organizational coverage instead of individual utility.
Before drafting the next announcement, ask: "What does each audience need to do with this information, and when do they need to do it?"
Then design backwards from that.
The DANCE System teaches how to design communication sequences that deliver the right information to the right people at the moment they can actually use it. Learn more
