Change updates are often loud, polished, and forgettable. The real impact happens when leaders stop announcing and start explaining.
A lot of change communication reads like a press release.
Polished. Controlled. Carefully managed.
But safety isn’t what builds trust during transformation. And the language that protects reputation in a media statement quietly destroys credibility in an internal announcement — because it signals exactly the wrong thing to exactly the wrong audience.
Change doesn’t fail because people resist it. It fails because the message never felt real.
Why organizations default to press release tone
The press release reflex is understandable. When something significant is changing — especially something that affects jobs, structures, or ways of working — the instinct is to control the message. To make it sound authoritative, considered, and complete. To avoid saying anything that could be misinterpreted, challenged, or used against leadership later.
So the legal team reviews it. The PR function shapes it. Senior leaders approve it. And by the time the message reaches employees, it has been processed into something that sounds more like a quarterly earnings statement than a genuine explanation of what’s happening to people’s working lives.
The organizational dynamics that produce this are real. Legal exposure, reputation management, the desire to avoid premature commitment — these are legitimate concerns. But the language designed to manage those concerns was designed for external audiences: media, investors, regulators. When it gets applied to internal communication, it lands completely differently. External audiences expect carefully managed language. Internal audiences — people who work there, who trust or distrust the organization based on accumulated daily experience — read the same careful management as evasion.
This is one of the fastest ways narrative drift develops. When the press release version of the change goes out first, every leader who subsequently tries to communicate more humanly creates a perceived inconsistency with the official announcement. The polished message becomes the reference point — and anything warmer or more specific sounds like a departure from it. (For more on how narrative drift compounds, read From Noise to Narrative.)
What press release language actually sounds like
The phrases are familiar because they’re everywhere:
“We’re pleased to announce…”
“Effective immediately…”
“We’re optimizing our processes…”
“This change will drive alignment across functions…”
“Stakeholders will be notified of updates…”
None of these are inherently dishonest. But they all share the same problem: they describe the change from the organization’s perspective without ever addressing the employee’s. They answer “what are we doing?” without answering “what does this mean for you?” They manage perception instead of creating understanding.
The result is communication that sounds rehearsed — because it was. And rehearsed communication signals control, not care.
What people actually hear
This is the most important section of this article — and the one most communicators never think about.
The gap between what leaders write and what employees hear is almost never about comprehension. It’s about inference. Employees are experienced organizational readers. They’ve received enough carefully managed communication to have developed sophisticated pattern recognition for what corporate language is actually signaling.
When leaders say “we’re optimizing workflows,” people often hear: “my job might be changing — or disappearing.”
When they read “we’re realigning to drive efficiency,” they quietly assume: “we’ll be expected to do more with less.”
When they see “this transformation will position us for future growth,” they think: “something difficult is coming and leadership doesn’t want to say what it is yet.”
When they receive “stakeholders will be kept informed,” they conclude: “I’m not part of the decision and I won’t get real information until it’s too late to do anything about it.”
When a message says “we’re excited to share this strategic initiative,” employees who have received dozens of such messages know: “this is going to be disruptive and leadership is trying to frame it positively.”
This isn’t cynicism. It’s experience. And it’s entirely predictable — because press release language asks people to trust without giving them anything concrete to trust. It creates exactly the kind of information vacuum that signal fatigue fills with assumption. (For the psychology behind this, read Change Fatigue: The Psychology Behind It.)
The damage compounds when different leaders use slightly different press release language to describe the same change. Each version sounds official. Each version is subtly different. Employees don’t reconcile the differences — they read them as contradictions and distrust all versions equally.
The clarity standard test
Here’s the diagnostic I use when reviewing change communication:
If your message could run on a newswire, it’s not clear enough for your team.
Press releases are designed to be understood by people who have no context for your organization — journalists, investors, the general public. They’re written to be surface-readable by strangers. If your internal change communication passes the newswire test — if a journalist could pick it up and publish it without any additional context — it almost certainly fails the employee test, because employees don’t need broadcast language. They need translation.
Change communication isn’t about announcing. It’s about anchoring — giving people something solid enough to stand on while everything around them is shifting.
The second test is simpler. Ask three people who received the message to explain it back to you in their own words, without looking at it. If their versions are materially consistent and personal — if they can explain what it means for them specifically — the message cleared the clarity standard. If they fall back on the official language without being able to translate it, or if their versions diverge, the message failed. (For more on this diagnostic, read The Clarity Gap.)
From press release to clarity
Here’s how the same ideas sound when written for understanding rather than perception management:
| Press Release Phrase | Clarity Rewrite |
|---|---|
| “We’re pleased to announce the implementation of a new system.” | “Starting next month, we’ll introduce a new system designed to make your daily work faster and simpler.” |
| “This change will optimize performance and streamline operations.” | “The new process removes steps that slow teams down — you’ll see quicker approvals and fewer bottlenecks.” |
| “We’re driving alignment across functions.” | “We’re connecting teams so decisions move faster and feel more consistent.” |
| “Stakeholders will be notified of updates.” | “We’ll keep teams and partners updated weekly so everyone stays on the same page.” |
The difference isn’t just tone. It’s audience. Press release language addresses the message to an abstract organizational entity. Clarity language addresses it to the specific human reading it. Every rewrite in the right column answers — at least implicitly — “what does this mean for you?”
How to write change messages people believe
The shift from press release to clarity requires reorienting around five principles — each one a direct inversion of what press release writing does by default.
Start with purpose, not announcement. Press releases lead with what is happening. Clear change communication leads with why it matters now — the problem being solved, the opportunity being addressed, the reason the timing is what it is. Purpose is what converts an announcement into a story people can locate themselves inside.
Write for conversation, not broadcast. The test: would you say this out loud to someone on your team, without reading from a document? If the answer is no — if the written version is more formal, more hedged, or more corporate than the spoken version would be — rewrite until they match.
Acknowledge impact before explaining rationale. Press releases protect the organization’s position by leading with the logic of the decision. Clear change communication acknowledges the human experience of the decision first — “we know this creates uncertainty,” “we understand this affects how you work” — before explaining the reasoning. That sequencing matters enormously. (For the full treatment of this, read How to Communicate Bad News Without Losing Trust.)
Answer the question people are actually asking. Not “what are we doing?” — employees can figure that out. The question is “what does this mean for me?” Every effective change message has a specific, concrete answer to that question for its specific audience. If the message could be sent unchanged to every employee at every level, it hasn’t been written for any of them.
End with direction, not closure. Press releases end with boilerplate contact information or forward-looking statements. Clear change messages end with one specific next step and one specific place to go for more information. Direction — even minimal direction — interrupts the anxiety spiral that ambiguity produces.
What this looks like in practice
I reviewed a system implementation announcement before it went out to 1,300 employees. It had been approved by legal, shaped by PR, and reviewed by four senior leaders. It was technically accurate, professionally formatted, and completely unreadable as human communication.
The opening paragraph announced the system. The second paragraph explained the business rationale. The third paragraph described the implementation timeline. Nowhere — in four paragraphs — did it mention what employees would experience, what would change about their daily work, or what they needed to do next.
We rewrote it in 45 minutes. Same information. Different audience orientation. The new version opened with what employees would notice first — a new login page the following Monday. It explained in plain language what the system would replace and why that was worth the disruption. It named the three things that wouldn’t change. And it ended with one specific action and one specific person to contact.
The difference in employee response was measurable. Follow-up questions dropped by more than half in the first week. The communications team said it was the most positive reception to a system announcement they could remember.
The information was identical. The language had changed from press release to human.
Final thought
The best change communicators don’t announce change. They translate it.
They turn abstract strategy into language people can see themselves in. They write for understanding, not applause. They resist the press release reflex — the organizational pull toward careful, controlled, managed language — because they know that what protects reputation in a media statement destroys trust in an internal announcement.
Because clarity isn’t corporate. It’s human.
And it’s the only language that actually moves people.
FAQs: Change communication writing
Because press release language was designed for external audiences — media, investors, regulators — who expect carefully managed language. Internal audiences read the same careful management as evasion. Press releases protect perception. Change communication needs to create understanding. Those are different jobs requiring different language — and using one for the other signals to employees that they’re being managed rather than informed.
A clear statement of purpose — why this change is happening now, not just what is changing. Acknowledgment of the impact on employees before the explanation of rationale. Plain language that answers “what does this mean for me?” specifically. One concrete next step. And a specific place to go for updates. These five elements are the difference between an announcement and a communication.
Two tests. First: if it could run on a newswire — if a journalist could publish it without any additional context — it’s not human enough for internal communication. Second: ask three people who received it to explain it back to you in their own words. If their versions are consistent and personal — if they can explain what it means for them — it passed. If they fall back on the official language or their versions diverge, simplify and try again.
Legal review, PR involvement, senior leader approval cycles, and the desire to avoid premature commitment or misinterpretation. These are all legitimate concerns — but the language designed to manage them was designed for external audiences. When applied internally, it produces the opposite of its intended effect: instead of managing perception, it creates distrust. The fix is not to remove legal or PR involvement but to separate the internal communication process from the external one.
When a press release version goes out first, it becomes the official reference point. Every leader who subsequently tries to communicate more humanly creates a perceived inconsistency with that reference. Employees read the inconsistency as contradiction rather than clarification, and distrust both versions. Starting with human language at the leadership level — before anything official goes out — prevents this dynamic.
The Clarity Framework reorients communication around understanding rather than perception management. The diagnose principle identifies where press release thinking is creating confusion. The define principle replaces managed messaging with a core story written for employees. The deliver principle explicitly addresses the human experience of the change rather than the organizational logic of it. And the measure principle tests whether people understood — not whether the message was approved.
Announcing describes what the organization is doing. Translating explains what that means for the specific human reading the message. Press releases announce. Effective change communication translates. The shift requires a complete reorientation of audience — from abstract organizational entity to specific person with specific concerns about how their working life is about to change.

If your organization is navigating change and you’re not sure why communication isn’t landing, that’s often where the work begins.
I’m Ana Magana, a change communications and change management consultant based in Calgary, Alberta. I help leaders cut through complexity with structure, empathy, and storytelling.
Work with me →
Read: The Language of Change: Words That Build Trust | How to Write a Change Message People Actually Read | The Clarity Gap: Why Leaders Think They’re Being Clear
