The Memo No One Read and the Hallway Conversation Everyone Repeated
There is a version of organizational communication that lives on the intranet, gets filed in a shared drive, and earns a send rate that no one discusses in the debrief. And there is a version that travels through the building without any official distribution — through the walk from the parking garage, the Slack DM, the Tuesday standup that goes seven minutes long. These two versions of the same announcement often carry entirely different information. Not because one is more accurate, but because one was designed for humans and one was designed for compliance.
This is not a technology problem. It is not a channel strategy problem. It is a signal problem. When official communication fails to carry the information people actually need, people build their own circuits.
Why the Memo Doesn't Travel
Organizations approach written communication during change as a documentation task. The announcement needs to say the right things, satisfy legal review, reach everyone simultaneously, and create a record. These are legitimate requirements. None of them are communication requirements.
A communication requirement asks: will this land? Will the person reading it understand what is happening, what it means for them, and what happens next? Will it reduce uncertainty, or will it produce questions that have nowhere to go?
A memo built for compliance can satisfy every documentation requirement and still fail every communication requirement. It speaks in passive constructions and hedged language because legal needs the passive constructions and the hedged language. It lists what is happening without explaining why. It tells people to "reach out to HR with questions" and HR has fifty questions per person and four people to answer them.
The memo is not wrong. It is just not doing the thing that people actually need it to do.
What the Hallway Conversation Does Differently
The hallway conversation is not constrained by legal review. It operates in first person, present tense. The person delivering it has a face and a relationship. When it carries something false or incomplete, it can be corrected in real time. When the person asking has a question, someone answers it now, in plain language, in a way that accounts for who is asking.
None of this is accidental. The hallway conversation is not better engineered. It is better matched to how people process high-stakes information. It is immediate, personal, bidirectional, and legible. It does not begin with "As we continue our commitment to transformation."
And critically: the hallway conversation carries affect. The person speaking it has a read on the situation. They are not performing neutrality. Their tone tells you something real — whether they are worried, whether they think this is going to be okay, whether there is more coming. People are extraordinarily good at extracting that signal. They do it without being aware they are doing it. And they carry it forward.
The Practitioner's Actual Problem
Change communications practitioners are often handed the memo and asked to make it better. Sometimes they can. They can push for active voice, fight for a FAQ, add a leader video that sounds like a person rather than a transcript. These are real improvements.
But the more important work is understanding why the hallway conversation exists and what it is filling in for. When informal communication networks light up during a change, they are not evidence of a workforce that needs better communication. They are evidence of an information vacuum. People are filling in what the official communication failed to provide.
The practitioner's job is not to compete with the hallway conversation. It is to understand what the hallway conversation is carrying and design official communication that carries it first. That means asking different questions before the announcement goes out.
Not: does this meet legal requirements?
Not: have all the right people approved this?
But: what are the three things people will want to know that this memo does not tell them? What will they ask each other in the first twenty minutes? If someone's manager reads this and then has a one-on-one with a direct report, what will the direct report need that the manager will not have?
Those questions produce different communication. Not longer. Not more hedged. Different in structure, in what it says explicitly, in the permissions it gives managers to speak with authority, in the acknowledgment of what is not yet known.
Designing for How Information Actually Travels
The signal problem in organizational communication is not that people ignore official channels. It is that official channels are often not designed to carry signal — only to carry content. Content is what the announcement says. Signal is what it means, what it implies about what is coming, whether the people delivering it understand what they are asking of the people receiving it.
Signal travels through specificity. Through a leader who names the thing that is hard rather than the thing that is good. Through a manager who says "I don't know yet, and I'll tell you as soon as I do" rather than directing people back to the shared drive. Through a communication that accounts for the fact that people are not reading it in a neutral state, and that the first question they are asking is not what does this say but am I going to be okay.
Build the System That Does the Job
The hallway conversation is not a problem to be solved. It is a signal to be read. When informal networks light up during a change, they are telling you exactly what the official communication failed to provide. That information is useful. It tells you what to fix, what to add, what to say plainly that the approved language danced around.
The goal is not to eliminate informal communication or to out-pace it. The goal is to design official communication that earns the same trust — that carries real information in a form people can use, that speaks to what people are actually afraid of rather than what the organization needs to have said, that gives managers something to work with when a direct report asks a question the FAQ does not answer.
That is a design problem, and it has a design solution. Not a longer memo. Not a faster distribution cadence. A different set of questions asked before anything goes out — and a willingness to let the answers change what gets written.
