The Difference Between Informing People and Actually Communicating With Them

There is a distinction that most organizations miss during change, and missing it explains a significant share of the resistance, disengagement, and adoption failure that change initiatives produce.

The distinction is this: informing people and communicating with them are not the same thing.

Informing people is one-directional. A message originates from the organization, travels to the employee, and the communication is considered complete. The email was sent. The town hall was held. The intranet post was published. The box is checked.

Communicating with people is two-directional. A message is sent, received, understood, and responded to. Questions are asked. Concerns are raised. Feedback is gathered. The organization adjusts based on what it hears. Understanding, not just transmission, is the measure of success.

Most organizational change communication is informing. The organizations that get the best adoption outcomes are the ones that have figured out how to actually communicate.

Why One-Way Broadcasting Fails

One-way communication during change fails for a predictable reason: it treats all employees as having the same information needs, the same starting level of awareness, and the same capacity to absorb and act on messages delivered through the same channels at the same time.

None of those assumptions are true. Some employees are aware of a change before it's officially announced. Others are encountering it for the first time in the announcement itself. Some are highly affected and have significant concerns. Others are minimally impacted and mostly curious. Some primarily receive communication through email. Others rarely read internal emails and depend on their manager for information. Some are ready to engage immediately. Others need time to process before they can ask the questions that would help them adapt.

One-way broadcasting delivers the same message through the same channel to all of these people and hopes for consistent results. It rarely gets them.

The alternative, and the one that consistently produces better adoption outcomes, is a communication approach that starts with an honest assessment of where different stakeholder groups actually are, designs messages and channels specific to each group's needs, and builds in the mechanisms for those groups to respond, ask questions, and influence the communication going forward.

Listening as a Change Management Tool

The most underutilized tool in change communication is listening.

Most change communication plans are almost entirely composed of outbound activities: announcements, town halls, newsletters, cascades, and campaigns. They devote considerable resources to crafting messages and almost none to receiving them. The result is that organizations don't know what employees are actually hearing, what concerns are most prevalent, or where the communication is failing until those concerns surface as resistance, disengagement, or turnover.

Structured listening during change, through pulse surveys, focus groups, manager feedback loops, open Q&A forums, and change network feedback, provides the information needed to adjust communication in real time rather than discovering months later that a critical message never landed.

It also does something that is hard to achieve through any other mechanism: it signals to employees that their response matters. Employees who feel that their concerns are genuinely heard, even when the answer is "we can't change this particular decision," are significantly more engaged in the transition than those who feel that communication is happening to them rather than with them.

Feedback Loops That Actually Function

Feedback loops in change communication fail in one of two ways: they don't exist, or they exist in name only.

A feedback loop that exists in name only looks like this: the communication plan includes a general email address for questions, a quarterly pulse survey with results reviewed by the project team, and an open comments section on the change portal that nobody checks. Employees quickly learn that feedback sent through these channels produces no visible response, and they stop using them.

A feedback loop that actually functions looks different: questions submitted through a named channel receive a response within a defined timeframe. Pulse survey results are shared with employees, not just with the project team, along with what the organization is doing in response to what it heard. Themes that emerge from manager feedback are addressed in the next communication cycle. Employees can see, in concrete terms, that what they said changed something.

The investment required to build functional feedback loops is not primarily financial. It is primarily attentional: someone has to be responsible for monitoring, synthesizing, and responding to what comes through those channels. That is a change management function, and it is one of the most important ones.

Two-Way Communication in Practice

Building genuine two-way communication into a change effort requires several things that most organizations don't currently have in place:

A structured listening plan alongside the communication plan. Just as the communication plan identifies what messages will be delivered, when, and through which channels, a listening plan identifies what information needs to be gathered, how it will be collected, who will analyze it, and how it will influence future communications.

Response capability. Gathering feedback without the capacity to respond to it is worse than gathering no feedback, because it creates the expectation of response and then fails to deliver it. Building feedback loops requires resourcing the capacity to process and respond to what comes through them.

Transparency about what was heard and what changed. Closing the feedback loop visibly, sharing with employees what was heard and what, if anything, changed as a result, builds the credibility that makes future feedback mechanisms worth using. Employees who see evidence that their input was taken seriously are more likely to engage again.

Differentiation between what can and cannot change. Not all employee feedback will result in a change to the plan. Being honest about that, clearly distinguishing between input that shaped decisions and input that was heard but couldn't be accommodated, maintains credibility even when employees don't get the outcome they wanted. Pretending all feedback influences everything produces distrust when employees eventually notice that nothing has changed.

The OCM Lens: Communication Architecture That Flows Both Ways

Effective OCM designs communication as a system with inbound and outbound flows, not just a message delivery mechanism.

Stakeholder communication preferences. Different stakeholder groups prefer to receive and give information through different channels. Understanding those preferences and designing communication accordingly, rather than defaulting to the channels most convenient for the project team, significantly increases both the reach and the quality of communication in both directions.

Change network as a listening infrastructure. Change champions embedded in teams serve not only as local advocates and sources of support but as listening posts: people who understand both the official change narrative and the informal concerns circulating in their teams. Equipping change champions to gather and report those concerns back through structured channels creates a listening infrastructure that reaches places formal surveys don't.

Communication measurement that includes comprehension, not just reach. Measuring whether an email was opened is not the same as measuring whether it was understood. Building comprehension checks, through brief knowledge checks, manager conversation guides that confirm understanding, or pulse survey questions that test specific message retention, provides a much more accurate picture of whether communication is actually working.

Iteration as a feature, not a failure. Two-way communication produces information that sometimes requires adjusting the plan. Organizations that treat mid-course communication adjustments as a sign of planning failure miss the opportunity to improve adoption in real time. The willingness to adjust based on what is being heard is one of the clearest signals an organization can send that it is actually communicating, not just broadcasting.

Informing people is easy. Communicating with them is harder, and it makes all the difference.

Explore our consulting services or our toolkits and resources to learn how OCMhub designs communication systems that actually work in both directions.