A restructure is not the hardest part. The hardest part is the six weeks before the restructure is announced, when the leader knows and the team does not - and the team can tell something is happening. What you do in that window determines whether your team comes out of the restructure intact.
I have been through three meaningful organizational restructures - one at Zendesk, one at Adobe, and in my current operating environment - and the thing I remember most clearly about each of them is not the announcement. It is the weeks before the announcement.
The meeting invites that included some people and not others. The executive team suddenly unavailable for two weeks. The one-on-one with a senior leader that ended differently than it usually did.
The team picked up all of it. They always do.
The official message came later. The informal read on what was happening formed much earlier. And by the time the restructure was announced, the emotional response in the team was not to the news itself but to the gap between what they had already figured out and what the organization had been willing to say.
How you lead through a company restructure starts before the restructure is announced. Most guidance on leading through organizational change focuses on the communication plan and the transition period. Those matter.
But the trust damage that makes transitions harder than they need to be accumulates in the silence before the announcement.
What Teams Actually Experience During a Restructure
Before getting into how to lead through a restructure, it is worth being honest about what the experience looks like from inside a team.
Uncertainty is not the hardest part. People can tolerate uncertainty if they trust the person they are following. What they cannot tolerate as cleanly is uncertainty paired with evasion - the sense that the person they report to knows more than they are saying.
Ambiguity about role and scope hits harder than ambiguity about structure. A team member who is uncertain whether their role exists in the new structure is in a different psychological state than one who is uncertain what the new reporting lines will look like. The first creates a survival calculus.
The second is just confusing. Leaders often treat these as the same level of concern. Teams do not.
The high performers leave first. This is not a theory. Per a McKinsey study on organizational transitions, companies that go through major restructures see an average of 31% increase in voluntary attrition among high performers in the twelve months following the announcement.
High performers have options. When a restructure signals instability and the organization has not communicated clearly what comes next, the people with options use them.
Information vacuums fill with the worst available interpretation. If a team does not have real information, they will generate it. The generated information is almost always more alarming than the reality.
This is not a failure of communication skills. It is how humans process threat uncertainty.
What Leaders Usually Get Wrong About Leading Through a Restructure
The most common failure pattern is also the most understandable one: leaders try to reassure the team before they have anything concrete to reassure them with.
"Everything is going to be fine." This costs the leader more than it gains them. The team does not believe it - because they have been watching for weeks and they know something is changing. And they now have data that the leader is willing to say things that are not fully grounded in reality.
That is a more expensive credibility problem than the one you were trying to prevent.
Staying vague to avoid difficult conversations. "I am not able to share details yet" is sometimes literally true and also a way to avoid the conversation that needs to happen. The better version is being specific about what you know, what you do not know, and when you expect to know more.
That is still limited information, but it is honest limited information.
Disappearing into the logistics of the restructure itself. This happens more than most leaders realize. The restructure creates a significant operational workload - new org charts, role definitions, transition planning, executive communication.
Leaders get absorbed in the work of the transition and pull back from the people management layer. The team interprets the pullback as confirmation that things are bad.
Treating everyone on the team as having the same concern. In any restructure, different team members are in different situations. Some are secure and worried about peers.
Some are genuinely uncertain about their own role. Some are looking for a signal that they are valued. Some are already planning their exit.
A communication plan that addresses all of them with the same message serves none of them well.
How to Actually Lead Through a Restructure
The guidance I have found most consistently useful comes from direct experience, not from change management frameworks. What follows is grounded in what I have seen work across multiple transitions.
Be honest about what you know and do not know, at the earliest point you can. There is a period in most restructures where leaders have been told what is coming but have not yet been authorized to communicate it. That window is genuinely difficult.
The best approach I have found: do not pretend the window does not exist. "There are conversations happening at the leadership level that I am not in a position to share details on yet. When I have something concrete, I will tell you directly.
I know that is not satisfying." That is not a communication strategy. That is just honesty.
Have individual conversations before the group conversation. This is slower. It is almost always better.
Your team members are in different situations and they will process the same information differently. A group town hall with Q&A creates a social performance where people are watching each other's reactions as much as they are processing the information. Individual conversations are messier to run and far more honest.
Focus the team on what is not changing. During a restructure, the things that are changing get all of the attention. The things that are not changing - the team's values, the standards for the work, the way the team treats each other - are often the anchors that hold people through the transition.
Naming them explicitly is not performative reassurance. It is orientation.
Be more reachable than you usually are. Not in a way that signals panic. In the practical sense of more frequent check-ins, quicker responses, more availability for conversations that do not have a formal agenda.
The signal this sends is that you are not managing the situation at arm's length.
At Zendesk, during a restructure that changed my team's reporting structure and scope significantly, I ran twenty-minute one-on-ones with each team member in the week following the announcement. Not to deliver information - most of them had the same information I did. Just to hear where they were.
Several of those conversations surfaced concerns I would not have heard otherwise, and a few of them surfaced plans to leave that I was able to address.
Three of those people are still in roles I track. Two stayed because of conversations in that window. I know that with reasonable confidence because they told me, later.
How to Retain Your Best People Through a Restructure
This is the question I get asked most often, and the answer is harder than most leadership writing acknowledges.
You cannot retain everyone through a significant restructure. Some attrition is structural - people whose roles are eliminated, people who genuinely needed a different environment than what the restructure produces, people who had been waiting for a clear moment to decide and the restructure gave them one.
What you can do is reduce the loss that is not structural.
The most reliable retention mechanism during a restructure is clarity about the individual's place in what comes next. Not generic reassurance. Specific clarity.
"Your role exists in the new structure. Here is what changes and what does not. Here is what I am advocating for on your behalf." The more specific, the more credible.
The second mechanism is demonstrated advocacy. Not stated advocacy - demonstrated. The team member who watches their leader fight for scope, argue for a headcount decision, or push back on a restructure outcome that hurts their team has very different retention dynamics than the one whose leader accepts every decision without friction.
I am not suggesting leaders should performatively fight battles they cannot win. The advocacy needs to be real. But the willingness to advocate - visibly, even when it creates some friction with the organization above - is one of the most reliable signals a leader can send that the relationship is worth staying in.
What Good Communication Actually Looks Like
The principle that most change management writing lands on is "communicate, communicate, communicate." This is technically correct and practically underspecified.
Here is a more useful version:
Communicate with specificity. Not "we will keep you updated" but "I will have an answer on the role structure by Thursday and will send the details Friday morning." Specificity creates accountability. It also signals that you are tracking the timeline and not just managing feelings.
Separate facts from interpretation. "The team is being restructured" is a fact. "I believe this will ultimately improve the scope of your role" is an interpretation - and in a restructure, interpretations can be wrong.
Label them clearly. Your team will trust the facts more when they know you are not blending in your own read.
Create space for the team to be unhappy about it. This sounds counterintuitive. It is not.
A team that is told "this is a good thing, here is why" with no room for disagreement will suppress its honest response and move the conversation elsewhere. Acknowledging that the change is real and the adjustment is real - even if the outcome is ultimately good - gives people permission to process it without having to perform enthusiasm they do not feel.
After the Restructure: The Part Most Leaders Skip
Most writing on leading through a company restructure covers the announcement and the transition. The period that follows - three to six months after - gets much less attention, and it is where a significant amount of the lasting damage either gets repaired or becomes permanent.
Post-restructure, the team is often running with changed scope, changed relationships, and changed expectations while still processing the transition. Leaders who move quickly to "back to business" signal that the transition is over. For many team members, it is not.
The practices that help: maintaining the increased check-in cadence for longer than feels necessary, explicitly naming what the team navigated and how, being honest about what worked and what you would do differently. That last one is counterintuitive for a lot of leaders. Naming what you would do differently is not weakness.
It is the fastest way to rebuild trust after a period where the organization moved in ways that were outside anyone's control.
