Communications Containers
What Holds People During Change
When a significant organizational change is announced, the most common communication failure is not saying the wrong thing. It is failing to create any structure for what comes next. The announcement goes out. The questions start. And people are left holding their anxiety in whatever vessel happens to be nearby — the Slack channel, the parking lot, the group chat no one officially sanctioned.
This is a design failure. Not an empathy failure, not a messaging failure — a design failure. Organizations tend to treat communication during change as a series of content problems: what do we say, when do we say it, how do we frame it. But the more consequential question is structural: what are we building that will hold people while this unfolds?
That structure is what practitioners call a communication container. And most organizations have never deliberately built one.
What a container actually is
A communication container is not a communication plan. A plan specifies content and cadence — what will be sent, to whom, on what timeline. A container is something different. It is the architecture of predictability that allows people to tolerate uncertainty without fragmenting.
Think about what people need when they do not yet have answers. They need to know when they will hear something next. They need a place to put their questions that does not feel like shouting into a void. They need some signal — however small — that someone is paying attention to the shape of their experience and not just managing the message. A container provides the form that holds the process. The content can change; the container remains.
In practice, a container might look like a standing weekly touchpoint with a consistent structure. It might look like a dedicated FAQ channel that gets updated on a regular, published schedule rather than when it is convenient. It might look like a leader who shows up at the same time each week, not to announce anything, but specifically to receive questions. The content of each of those containers will vary. The container itself is the commitment.
What makes it a container rather than just a meeting or a channel is the quality of consistency and intention behind it. People learn, over time, whether a structure is real. Whether the all-hands actually allows hard questions or runs out the clock on safe ones. Whether the update cadence holds when things get complicated or goes quiet exactly when silence is most costly. A container is only as functional as its reliability under pressure.
What happens without one
When organizations fail to build containers, people build their own. This is not a failure of the workforce — it is a predictable human response to environmental uncertainty. If there is no official place where questions get answered, people will create unofficial places. If there is no structured channel for concerns, concerns will find unstructured ones. If leadership does not provide a cadence, the rumor cycle will fill the gap with its own.
The informal containers that emerge in the absence of official ones are not neutral. They tend to amplify anxiety rather than metabolize it, because they operate on the wrong inputs — speculation rather than information, fear rather than fact. And once an informal container is established and trusted, it is very difficult for official communication to displace it. People do not abandon a structure that has been reliable for them in favor of one that has not yet proven itself.
This is why organizations that go silent during change — that hold information until they have certainty, or that reduce communication in the interest of avoiding difficult conversations — often find that the communication environment is harder to recover than anticipated. The silence was not neutral. It was information. People read it as a signal of something being withheld, of leadership that cannot be trusted to tell the truth under pressure. The container they built in response to that silence is now the operative reality. Releasing a well-crafted announcement into that environment is not a fresh start. It is content dropped into a container someone else designed.
What good containers are made of
The materials for a good communication container are not complicated. They are consistency, access, and honesty about what is not yet known.
Consistency means showing up on the schedule you committed to, even when you have nothing new to say. "We don't have an update this week, and we'll be back next Friday" is not a failure of communication. It is the container doing exactly what it is supposed to do: demonstrating that the structure is real and that silence will be named rather than practiced.
Access means creating a genuine path for questions to reach the people who can answer them — and closing the loop. Not a suggestion box that gets reviewed once a quarter. Not a town hall that fields the safe questions and runs out of time before the real ones. A form, a channel, a person — whatever the mechanism, people need evidence that their questions are received, even when the answer is still "we don't know."
Honesty about what is not yet known is the hardest element to build in, because it requires leaders to say things that feel incomplete and open-ended in a professional context where completeness and certainty are the expected register. But "we haven't decided yet, and here is what we're working through" is one of the most stabilizing things a leader can say during a period of uncertainty. It names the reality rather than performing a confidence that no one believes. And it treats the people receiving the information as adults who can hold ambiguity alongside someone in authority, rather than as an audience that needs to be managed into acceptance.
Why this is a design problem, not a communications problem
Practitioners who work in change communication often inherit the symptom — the anxious workforce, the rumor cycle in full motion, the leader who has lost credibility — rather than the structural condition that produced it. The treatment at that point is harder than it needs to be, and it cannot fully undo the pattern already set.
The better intervention happens earlier, before the change is announced, at the design phase. Before the first communication goes out, someone needs to ask: what are we building that will hold people for the duration of this? Not just what are we saying on day one, but what is the architecture for the weeks and months that follow? Who has access to what, when? Where does uncertainty go? What does the cadence look like, and how do we sustain it?
These are not communications questions in the traditional sense. They are organizational design questions. And answering them well is how you create the conditions for communication to actually do its job — not just deliver information, but build enough trust that people can tolerate what they do not yet know.
