Your Employees Don't Hate Change. They Hate Surprises.

Here is something that gets misdiagnosed constantly in organizations going through change: the resistance you're seeing from employees isn't about the change itself. It's about how they found out about it.

Change management practitioners hear it all the time. A major system migration is announced on a Friday afternoon email. A restructuring is revealed in an all-hands meeting with no prior signal. A new process goes live on Monday that nobody knew was coming on Thursday. And then leadership is genuinely surprised when employees are frustrated, disengaged, or actively resistant.

The frustration isn't irrational. It's a completely predictable response to feeling like decisions are being made about you without you, and you're the last to know.

The Organizational Announcement Problem

Most organizational announcements are written to inform leadership, not to serve employees. They lead with the business rationale, the executive sponsor's name, and the implementation timeline. They bury, or leave out entirely, the information employees actually need: what this means for my day-to-day work, whether my role is changing, and what I'm supposed to do differently starting Monday.

The result is that employees receive an announcement, read it carefully, and come away with more questions than they started with. They fill in the blanks with assumptions, which are almost always more alarming than the reality. And they start talking to each other, which means the informal communication network, the rumor mill, picks up the story before the official channels have had a chance to tell it clearly.

From an OCM perspective, an organizational announcement is not a communication plan. It is a single data point in what needs to be a sustained, multi-channel communication effort. An announcement tells people something happened. A communication plan builds understanding over time across every affected stakeholder group.

Last-Minute Communications and the Trust They Destroy

Nothing signals to an employee that they are an afterthought in an organizational change faster than receiving critical information at the last possible moment.

Last-minute communications happen for predictable reasons: decisions take longer than expected, leadership isn't confident in the message until the implementation date is close, or the communication workstream simply wasn't built into the project plan with enough lead time. None of those reasons feel like adequate justification to an employee who had no warning that their workflow was about to change significantly.

The damage from last-minute communications goes beyond the immediate frustration. It erodes the trust that future change communications will depend on. Once employees learn that the organization communicates change at the last minute, they stop believing early reassurances. Every subsequent "we'll keep you informed" message is filtered through the memory of the time they weren't.

Rebuilding that trust requires sustained, consistent follow-through over multiple change cycles, which makes the investment in early, thoughtful communication at the beginning of a change effort far cheaper than the cost of repairing credibility afterward.

Poor Leadership Visibility During Change

Employees look to their leaders during change. Not just for information, but for signals about how seriously the organization is taking the transition, whether leadership is confident, and whether the people responsible for the change actually believe in it.

When leaders go silent during a change effort, employees notice. When the CEO sends a single email and then disappears from the conversation, employees notice. When managers are visibly uninformed about a change they're supposed to be implementing, employees notice that too, and they draw their own conclusions.

Effective leadership visibility during change is not just about showing up at all-hands meetings. It means leaders being able to answer basic questions about the change in their own words, modeling the new behaviors the change requires, and staying engaged through the full adoption cycle rather than moving on to the next priority once the announcement has been made.

From an OCM standpoint, leadership communication coaching is one of the highest-leverage investments in a change effort. A leader who can articulate why the change is happening, what it means for the team, and what their commitment to the transition looks like is worth more than any number of well-designed communication templates.

Hidden Decisions and the Silence That Fills the Gap

Perhaps the most damaging communication failure in organizational change is the hidden decision: a significant choice that was made somewhere above the employees it affects, not communicated until it's too late for any input, and framed as already final when employees first hear about it.

Hidden decisions don't stay hidden. They leak, through managers who know and tell their teams informally, through hallway conversations, through documents accidentally shared too widely. And when employees find out through informal channels before official ones, the damage is twofold: they're surprised by the decision, and they've lost any remaining confidence that the organization intends to communicate with them honestly.

The antidote to hidden decisions is not necessarily earlier announcement of unfinished decisions. It is creating communication structures that signal, early and credibly, that important decisions are being worked through, that there is a plan for sharing information as it becomes available, and that employees will have the opportunity to ask questions and receive real answers.

That signal, even without the specific decision details, reduces the anxiety that makes silence so damaging. People can tolerate uncertainty better when they trust that they won't be the last to know.

The OCM Lens: Communication Is a System, Not a Series of Announcements

Effective change communication requires a structured approach that most organizations don't have in place.

A communication plan that precedes deployment. The communication workstream for any significant change effort should begin when the change begins to be planned, not when the implementation date is set. Early planning allows for stakeholder mapping, message development, channel selection, and timing that serves employees rather than simply documenting what leadership decided.

Stakeholder-segmented messaging. Different stakeholder groups need different information at different times. A frontline employee needs to know how their daily workflow is changing. A manager needs to know how to answer their team's questions. A senior leader needs to know how to frame the change strategically. A single message that tries to serve all of these audiences typically serves none of them well.

Cadence and consistency. Employees who receive regular, predictable communication about a change in progress, even when the message is "here's where we are and what we're still figuring out," feel significantly less anxious than those who receive communications sporadically. Predictable cadence builds trust regardless of the specific content.

Two-way channels. Communication that only flows downward is broadcasting, not communicating. Effective change communication creates structured opportunities for employees to ask questions, raise concerns, and receive real answers, not just access to a general mailbox that nobody monitors.

Reinforcement beyond launch. Change communication that stops at go-live treats the announcement as the end of the communication effort. Effective communication continues through the full adoption cycle, addressing the questions that emerge in practice, celebrating early wins, and maintaining leadership visibility through the period when adoption is still fragile.

Your employees don't hate change. They hate being surprised by it, informed too late, and left without the visibility they need to feel confident in what's coming. Fix the communication, and most of the resistance takes care of itself.

Explore our consulting services or our toolkits and resources to learn how OCMhub builds communication frameworks that actually work.