Communicating Change: How to Announce It So People Hear It

Most change announcements are written to be sent, not heard. A careful memo goes out, a slide deck gets presented once, and leaders are surprised a month later when people are still asking what is happening and why.

The gap is rarely about polish. People listening to news of a change are trying to answer a handful of personal questions, and if the message doesn't answer them, they fill in the blanks from rumor. This guide covers what those questions are, how to sequence an announcement, what to do when you can't share everything, and how to keep communication going after the first message.

Answer the questions people are silently asking

In a 2009 article in the Journal of Change Management, researchers Achilles Armenakis and Stanley Harris looked back on about 30 years of their work on organizational change. They describe five beliefs that underlie people's motivation to support a change:

• Discrepancy: a change is needed, because there is a real gap between where the organization is and where it should be.
• Appropriateness: this specific change is the right response to that gap.
• Efficacy: we, and I, can actually pull it off.
• Principal support: leaders are committed and it is not going to be another passing fad or "program of the month."
• Valence: there is something in it for me.

Those five beliefs make a practical checklist for any announcement. A message that explains the problem but never shows why this particular solution was chosen leaves people doubting appropriateness. A message full of enthusiasm with no plan for training leaves them doubting efficacy. A message that only talks about company benefits skips valence entirely.

A U.S. General Accounting Office report on mergers and organizational transformations (GAO-03-669, July 2003) makes the same point in plainer words: communication has to address the immediate and natural question, "what's in it for me?" Employees want to know whether their jobs might be affected, what their rights and protections are and how their responsibilities might change.

Sequence it: managers first, then everyone, then the details

How people hear news shapes how they judge it. The GAO report cites Deloitte & Touche's recommendation that information be "prereleased" to line managers whenever possible, so employees hear it from inside the organization first and have a chance to ask questions. It also stresses consistency of message, because when different groups hear different versions, people assume someone else is getting the "real" story.

A workable sequence for most changes:

1. Brief the managers who will field questions, shortly before the announcement. Give them the reasons, the plan, what is still undecided and a short list of likely questions with honest answers.
2. Announce to everyone affected at about the same time, ideally live, so people can react and ask.
3. Follow quickly with team-level conversations led by direct managers, focused on what the change means for that team's work.
4. Put the core facts in writing somewhere people can find them again.

For example, imagine a hypothetical regional clinic group switching to a new scheduling system. The front-desk supervisors get a briefing the day before. The next morning, the operations director explains the change at a short all-staff call. That afternoon, each supervisor meets with their team to walk through what changes at check-in, when training starts and who to ask for help.

Tailor the message to each group

One message rarely fits everyone. The GAO report notes that groups with different interests need different information: people with technical skills may want to know whether their skills will remain valued, while administrative staff may want details on new systems and work processes.

Before you announce, list the groups affected and write one or two sentences for each on what changes for them, what stays the same and where they can get help. If you can't write those sentences yet, you are not ready to announce.

Be honest about what you don't know yet

Leaders often delay communicating because the details aren't settled. Silence rarely reads as neutral; it tends to read as bad news. The GAO report notes that even when details can't be shared for legal or security reasons, organizations can still share alternative types of information: status reports on progress, the exact time specific details will be available and responses to rumors or news reports.

In practice that sounds like: "We have decided to consolidate the two warehouses. We have not decided which roles will change. We will share that by March 15, and here is how we will decide." A specific date you keep builds more trust than a vague promise to "share more soon."

Make it two-way

The GAO report puts it directly: communication "is not about just 'pushing the message out.'" It describes the value of creating chances for employees to raise concerns and of using that feedback to adjust the implementation, citing a U.S. Mint plant where employees voted on options for an alternative work schedule at a town hall meeting.

Armenakis and Harris go further. They note that persuasive communication, such as speeches and memos, may not be as effective as active participation, because discovering something for yourself is so powerful. In practice, pair announcements with ways for people to shape the "how": pilot groups, working sessions on the details, open question channels and a visible record of what changed because someone raised it.

Name what's ending

Change messages tend to focus on the bright future. People, meanwhile, are thinking about what they're losing. The Bridges Transition Model, developed by William Bridges and used by leaders and consultants for more than thirty years, puts it this way: transition starts with an ending, as people identify what they are losing and learn how to manage those losses, whether relationships, processes, team members or locations.

Acknowledging the loss directly ("Many of you built the old process, and it served us well for years") costs nothing and signals that leaders understand what they're asking.

Plan to repeat yourself

A single announcement is not a communication plan. The GAO report records one forum participant's observation that successful communication will require twice the time and effort first planned, no matter how ambitious the original plan was. Build in regular updates through rollout, use the same core message each time and report progress against the timeline you gave.

Key takeaways

• Check every change message against five beliefs: the change is needed, it is the right change, we can do it, leaders mean it and there is something in it for the people affected.
• Brief managers first, announce to everyone consistently, then follow with team-level conversations.
• When details aren't settled, say what is decided, what isn't and exactly when you'll share more.
• Make communication two-way and show what changed because of feedback.
• Acknowledge what people are losing, and plan to communicate far more often than feels necessary.

Sources

• Achilles A. Armenakis and Stanley G. Harris, Reflections: our Journey in Organizational Change Research and Practice, Journal of Change Management (2009)
• U.S. General Accounting Office, Results-Oriented Cultures: Implementation Steps to Assist Mergers and Organizational Transformations, GAO-03-669 (July 2003)
• William Bridges Associates, Bridges Transition Model