What I Learned About Power Watching Who Gets Left Out of the Announcement
The announcement itself is rarely where the information is.
By the time something is announced — a restructuring, a leadership change, a reduction in force — the decisions are done. The language has been vetted. The sequence has been choreographed. What you are receiving when you read the all-staff email is not the decision. It is the managed version of the decision, shaped for consumption.
What is not managed as carefully, in most organizations, is who finds out first. Who gets a call before the email goes out. Who learns about the restructuring in time to ask a question that might actually change something. And who reads it at 9 a.m. on a Tuesday alongside everyone else, as if they are an employee in the same way the person who drafted the email is an employee.
That gap between who was already informed and who was not is one of the most reliable maps of organizational power you will ever see.
It is also, when done well, one of the most powerful tools a change communicator has.
The list skilled communicators actually build
When I am managing a significant announcement, I build an explicit pre-inform list. Not a vague sense of who should know before the email goes out. An actual document: who gets informed, in what order, through what channel, and why each of those choices was made.
The sequencing is deliberate down to a level that surprises people when they see it. It is not just "executives first, then managers, then employees." It is: this person needs to know before that person, because when that person finds out, they will immediately go find this person, and if this person does not already know, the information will spread informally before the formal cascade is complete. So we get ahead of it.
That level of granularity requires real knowledge of the organization. You have to understand not just the reporting structure but the actual social architecture — who talks to whom, who goes to whom when they are worried, who will sit quietly with difficult information and who will not. The org chart does not tell you any of that. The people who have been paying attention do.
This is why the quiet architects matter — the people Week 1 of this series described, the ones reading the room long after most people stopped. In a well-run change process, their knowledge is not incidental. It is operational. They know the social map that makes a cascade sequence work.
Why sequence matters more than most organizations think
The instinct in most organizations is to treat the cascade as a communication logistics problem. Get the information to the right levels in the right order before the email goes out. Brief the managers so they can answer questions. Make sure no one finds out from a news article before they hear it internally.
That is the floor, not the ceiling.
The cascade sequence is doing something more significant than managing information flow. It is communicating about standing. Every person who receives a pre-inform is receiving a signal: you matter enough to be protected from surprise. Every person who does not is receiving a different one.
People in organizations read these signals fluently and mostly without discussing them openly. They notice who was briefed before them. They register what that means about how the organization sees them. They calibrate their trust in leadership based not just on what was said but on how the information reached them.
A well-designed cascade accounts for this. It thinks through not just who needs to know for operational reasons, but who needs to know in order to feel appropriately included and who, if left out, will experience the exclusion as a statement about their standing that no amount of thoughtful messaging will undo.
What exclusion reveals when the cascade is not designed carefully
When the pre-inform list is not built deliberately, the gaps are not random. They tend to follow the same patterns: people with informal authority but no formal title get left out because they do not show up in the reporting structure. People who are considered "difficult" — who ask hard questions, who push back, who have institutional memory that complicates the official narrative — get deprioritized because managing them feels like extra work. People in functions that leadership does not regularly interact with find out with everyone else, not because their reaction does not matter but because no one thought carefully enough about whether it did.
The result is a cascade that accurately maps organizational blind spots. Who the organization sees. Who it does not. Which relationships have been tended and which have been allowed to atrophy. These are not secrets inside the organization. People who were left out know they were left out. They draw their own conclusions about what it means.
In my experience, the announcements that go sideways — where confusion spreads faster than the message, where the informal network gets ahead of the formal one, where trust erodes before leadership has a chance to build it — are almost always the ones where the cascade was not designed carefully. The pre-inform list was treated as a checkbox rather than a strategic tool.
The announcements that land well, where people feel informed rather than managed and the questions that surface are genuine rather than hostile, tend to be the ones where someone spent real time on the sequence. An explicit list. A mapped social architecture. Sequencing that accounted for the informal network rather than hoping it would stay quiet long enough for the formal one to catch up.
The social knowledge underneath the list
Building the pre-inform list well requires a specific kind of organizational knowledge that is hard to document and harder to transfer. It is not expertise in communication strategy or change management frameworks. It is knowing that the head of engineering and the VP of product have not been in a good place for six months and need to be informed separately and in a particular order. It is knowing that the team lead in the Boston office has more informal authority over her skip level than the org chart suggests, and that if she finds out late, her reaction will shape how twenty other people process the news. It is knowing who will hold information carefully and who will not.
This knowledge lives with people who have been paying attention. And in organizations where those people are not in the room when the cascade is being designed, the cascade tends to show it.
The best change communicators I know treat the pre-inform list as a piece of organizational intelligence work, not an administrative task. They ask questions, pressure-test sequences, and think through second and third-order effects of the order they have chosen. They build in buffers for the moments where the informal network moves faster than the formal one, because it always does.
What the list tells you
If you are not the one building the cascade, watching it is still instructive. The sequence in which information reaches people during a significant change is a reasonably accurate map of who the organization considers consequential. The omissions are as legible as the inclusions.
And if you are the one building it: the list is worth the time. The sequence is worth the care. The people who find out in what order will remember it not because they are tracking it consciously but because the experience of receiving significant news — how early, through what channel, from whom — shapes how people process everything that follows.
The announcement lands differently depending on how people received it.
That experience is not separate from the message. It is part of it.
