The first major restructuring I had to communicate about caught me entirely unprepared — not for the restructuring itself, which I'd helped design, but for the communication gap that had formed without my noticing. We had been working on the plan for six weeks. Senior leadership had been deeply involved. HR, finance, and the relevant business unit heads all knew the direction. And in those six weeks, we had said essentially nothing to the hundred and forty people whose roles were being significantly altered.
We had reasons, of course. The plan wasn't final. Legal had questions about the sequencing of certain announcements. We were concerned about competitive sensitivity. All of these were real constraints. But the practical effect of six weeks of silence at the top was that a different narrative had formed in the organization — pieced together from who had been called into which meetings, whose projects had been quietly paused, which external consultants had appeared on campus. By the time we were ready to communicate officially, we weren't introducing new information. We were competing with a story the organization had already written.
The story they had written was worse than the reality. It was more threatening, more uncertain, more indiscriminate about who would be affected. The silence we had maintained for six weeks had not protected people from anxiety — it had given their anxiety no accurate information to organize around, so they'd organized it around whatever signals were available. The signals were alarming.
That experience crystallized something I've tried to practice consistently since: the instinct to wait until you have the complete picture before communicating about change is almost always wrong. Not always — there are genuine constraints that legitimately delay communication. But "we're not ready yet" is, most of the time, a description of leader comfort rather than a description of organizational necessity.
Why the instinct to wait feels right — and what it actually produces
The case for waiting seems rational on its face. If you communicate before the plan is complete, you might share information that turns out to be wrong — and then you have to walk it back, which damages credibility. If you communicate about something uncertain, you'll generate questions you can't answer — which might amplify anxiety rather than reduce it. And there's a practical leadership argument: the person who communicates change thoughtfully and with a complete picture looks more competent than the person who communicates change in fragments, updating as they go.
Each of these concerns has some validity. Each of them also tends to be significantly outweighed by the costs of silence.
The credibility risk is real but overstated. Leaders who communicate honestly about evolving information — who say "here's what we know, here's what we don't know yet, and here's when we expect to have more clarity" — don't lose credibility when subsequent communications update the picture. What damages credibility is not updating information; it's information that turns out to have been managed, withheld, or spun. The person who said "everything is fine" before announcing a restructuring loses more credibility than the person who said "we're working through significant changes and I'll have more to tell you in two weeks."
The amplified anxiety concern is mostly empirically false. The anxiety is already there — organizations are remarkably good at detecting when significant decisions are being made, even when those decisions aren't discussed openly. The question isn't whether to activate anxiety; the anxiety has already been activated by the signals available in the environment. The question is whether that anxiety gets accurate information to organize around or inaccurate information.
And the competence signaling concern gets it backwards. The leader who communicates a complete, polished plan at the end of a process looks decisive and thorough. The leader who communicates honest, provisional information throughout a process looks trustworthy and respectful. Both forms of credibility matter. Only one of them is available when the plan is still forming.
What the information vacuum actually produces
In the absence of official communication, organizations don't remain in a state of neutral uncertainty. They construct narratives from whatever signals are available — personnel patterns, resource allocation shifts, the body language of senior leaders in hallway conversations, the cancellation or absence of certain regular meetings. These signals are real data points, but they're data points without interpretive context. The narratives they produce are therefore speculative, and speculation about threatening things tends toward the worst plausible interpretation rather than the most likely one.
I've watched this play out across enough change processes to be confident about the pattern. When significant change is in progress and communication is delayed, the informal narrative that forms is almost always more threatening than the reality. People are losing jobs that they're not actually losing. The change is global when it's actually regional. Key leaders are departing who aren't departing. The organization is being sold when it isn't.
What's notable is that these aren't irrational inferences. Given the signals available and the absence of accurate information, many of these conclusions are actually reasonable. The people constructing these narratives aren't paranoid or poorly calibrated. They're doing the best they can with the information available. The leader who delays communication is the one who has failed to give them better information to work with.
The downstream costs of a well-developed informal narrative are significant and often underappreciated. The best performers — the ones with options — start looking at the market rather than waiting to see how the uncertainty resolves. The team members who have been doing excellent work in silence start to wonder if they should have been building external visibility. The managers who needed to retain their people's full engagement during a period of organizational stress instead find themselves managing a talent risk that good early communication might have prevented.
What early change communication actually looks like
Communicating before you're ready doesn't mean communicating before you have anything to say. It means communicating with what you have, honestly, including being explicit about what you don't yet know. The structure that works is not complicated.
Start with what's true about the situation — the business reality, the external pressure, the strategic imperative, the performance gap — that is creating the need for change. Don't manage this; say it directly. People who receive a sanitized or softened version of the "why" tend to sense the sanitization, which reduces trust in everything that follows.
Then describe the direction you're considering, not as a decided course but as an honest account of your current thinking. "We're seriously exploring X" is different from "we haven't decided anything" — it gives people something real to orient around while being accurate about the state of the decision.
Then be explicit about what you don't know. Name the specific uncertainties: what's not yet decided, what's being worked through, what external factors will affect the final shape. Leaders who do this are sometimes worried it will amplify anxiety. In practice, it almost always reduces it. Vague uncertainty is more anxiety-producing than bounded uncertainty. "We don't yet know the timeline for the restructuring" is worse than "we're targeting a decision by the end of Q3, with implementation beginning in Q4." The first is open-ended; the second is bounded. Bounded uncertainty is much more manageable.
Finally, commit to a cadence. Tell people when they will next hear from you, and what kind of information that communication will cover. This is, in my experience, one of the most underestimated elements of change communication. The commitment to a regular cadence — "I will give you an update every two weeks throughout this process, and I'll always tell you what I know and what I don't" — converts open-ended anxiety into bounded waiting. It's the difference between not knowing when something will happen and knowing it won't happen until Thursday. Both involve uncertainty, but only one is psychologically manageable.
The courage dimension — what makes this genuinely hard
Communicating change before you're ready requires a specific kind of courage that doesn't get enough explicit acknowledgment in the leadership literature. It's not the courage of a difficult decision — that kind of courage has a clear structure: you make the call and own the consequences. The courage of early change communication is different. It's the courage of sustained visibility in a state of uncertainty: being willing to be seen, to be questioned, to be unable to answer many of the questions asked, and to accept that people will remain anxious despite your honest efforts.
Most leaders who avoid early communication aren't doing so because they're dishonest or because they don't care about the people affected. They're doing so because the alternative — being visible without answers, being asked questions they can't fully answer, standing in front of their teams in a state of acknowledged uncertainty — is genuinely uncomfortable. The performance of competence, which is part of what the role requires, is much easier to sustain when you communicate only from a position of complete information.
I've had leaders tell me, explicitly, that they delayed a significant announcement because they weren't sure they could answer the questions that would come. That's an honest account of the dynamic. The problem with it is that the calculation only accounts for the discomfort of the leader and not for the cost to the people waiting. When you delay communication to protect yourself from the discomfort of answering difficult questions, you're making a trade: your comfort for their anxiety. That trade is worth naming precisely.
The leaders I've seen handle change communication best have usually made a philosophical choice that precedes the tactical questions. They've decided that people's right to honest information about decisions that will affect their working lives is more important than their own comfort of appearing decisive and certain. That belief — which is really a belief about what respect for people requires — produces a different communication style. More provisional. More honest about uncertainty. Less focused on managing impressions and more focused on giving people what they need to navigate their own experience of the change.
When delay is genuinely justified — and how to distinguish it from comfort avoidance
I want to be clear that not all communication delay is avoidance. There are real constraints that legitimately require holding information: legal requirements in certain regulatory environments, board notification obligations before employee communication in public companies, contractual commitments in partnership agreements, genuine competitive sensitivity where premature disclosure creates external risk. These are real.
The question is whether the delay is driven by those genuine external constraints or by the internal discomfort of communicating uncertainty. There's a practical test: if the constraint were removed tomorrow, would you communicate immediately? If the answer is yes, the constraint is real and the delay is legitimate. If the answer is "not yet, because we haven't finalized the plan," the constraint isn't the primary driver. The desire for a polished, complete announcement is doing most of the work.
Even when delay is genuinely required, the communication about the delay itself is usually worth doing. "There are things in motion that I can't tell you about yet, and I expect to be able to give you more information within four weeks" is better than silence. It doesn't give people the information they want, but it gives them accurate information about the information situation, which is meaningfully better than nothing.
The crisis version of this is particularly important. When organizations are under acute pressure — when the stakes of the change are high and the timeline is compressed — the temptation to hold communication until the plan is solid intensifies at exactly the moment when the cost of doing so is highest. People's need for accurate information is greatest when the stakes are highest. The instinct to protect the plan until it's complete is most dangerous precisely when people most need to be oriented.
What questions from your people are actually telling you
One of the most valuable pieces of early change communication is what you learn from the questions people ask. Every question is information about what your communication has left unclear, what people are most worried about, and what's most salient for them about the change — which is often different from what you think is most salient.
The leader who communicates early and invites questions is collecting real-time signal about the state of understanding and concern in the organization. That signal is genuinely useful — not just for the emotional management of the change process, but for the quality of the decisions being made. The people closest to the work often see things that the people designing the change don't see, and the question period is one of the primary mechanisms by which that information surfaces.
I've been in change processes where the question period surfaced a genuine implementation problem that the design team hadn't considered — a technical dependency, an informal relationship that the new structure would break, a customer implication that nobody had mapped. Early communication created the opportunity for that information to surface before the decisions became irreversible. Late communication — communication at the point of final announcement — creates no such opportunity. By then, the plan is done.
There's also a trust dimension to questions that's worth naming. When a leader communicates early and invites questions honestly — including questions they can't answer — and then actually follows through on updating as they learn more, they're demonstrating something about how they operate: that people's genuine concerns matter, that uncertainty isn't shameful, and that the relationship between leadership and the people they lead is genuinely reciprocal rather than unidirectional. That demonstration has value beyond any specific change process. It's trust-building in the most durable sense.
The retrospective view: what the restructuring taught me
The restructuring I described at the opening of this essay eventually worked out reasonably well — not because of how we handled the communication, but somewhat in spite of it. We corrected course reasonably quickly once we understood the damage the silence had done. We had direct conversations with the people most affected, acknowledged the gap in our communication honestly, and established a much more regular cadence for the rest of the process.
What I've carried from that experience is a kind of communication default that I try to maintain regardless of the circumstances: when in doubt about whether to communicate, the answer is almost always yes. The exceptions — the genuine legal, regulatory, or competitive constraints — are real but they're fewer than the discomfort-avoidance disguised as constraint. And even within the genuine constraints, there is almost always something honest that can be said: about the direction, about the uncertainty, about when more will be known.
The people in organizations are not fragile. They can handle uncertainty, including significant uncertainty about their own futures. What they can't handle as well — what actually erodes trust and engagement in ways that are hard to repair — is the sense that the people responsible for the decisions affecting their lives don't think they deserve honest information. That sense, once formed, has a long half-life. The communication choice that protects leader comfort at the cost of that trust is almost never the right trade.
Related: Transparency Is a Discipline, Not a Personality Trait, What Crisis Leadership Actually Requires