Leadership team alignment during a reorg or layoff is tested in private, before any employee sees the new org chart. Keep it by settling the decision and the reasons inside the leadership team first. Agree one explanation every leader will give, confirm new reporting lines in writing, and meet briefly two or three times a week for the first few weeks.
Why is a reorg a leadership problem as well as an HR one?
Because the remaining leaders go through the change too. Scope moves and reporting lines move. Some leaders lose people they hired; others inherit teams they have never run. Harvard Business Review's piece on what to do and say after a tough reorganization starts from the same place: "There is often a lot of confusion and uncertainty."
A reorg squeezes structural change and emotional weight into a few days, with the whole company watching. A team that was quietly misaligned before has no time to work it out slowly. The gaps come out fast, in front of anxious people.
What breaks first?
Usually these, in this order:
- Reporting lines nobody confirmed in writing. Scope, budget and who reports to whom all move at once. Unless every affected leader confirms the new structure in writing, two of them will describe it differently within a week.
- One leader hearing the plan before another. Even a scheduling accident reads as a slight, and the leader who heard second starts asking what else they missed. We describe this pattern in signs your leadership team is not aligned.
- An announcement before the leaders agree on why. If the company collects five different reasons within a day, it concludes there was no real reason.
How do you align the team before the announcement?
Every leader should be able to explain the decision in their own words and land on the same substance. Nodding along in a meeting does not count. If a leader still thinks the decision is wrong, that has to come out before the announcement. Otherwise it surfaces when their team asks a hard question and the answer does not match.
Disagreement handled early is cheap. Disagreement held back until it leaks is expensive, and a reorg is exactly when it leaks. Reducing executive team conflict covers how to bring it out early.
Why agree one shared explanation?
Because each leader will otherwise explain it from their own partial view, and the versions drift apart within days. Write down, in plain words, the reason the whole team will give. Leaders can use their own words, as long as five leaders answering five employees say the same thing.
The people who stay are listening closely. HBR's guide on how to communicate layoffs to your staff notes that "layoffs cause fear, anger, and deep loss of trust among remaining employees," and that how you communicate "can make a critical difference."
Keep the written explanation where every leader can find it, so it outlasts the announcement week.
How often should the leadership team meet after a reorg?
Two or three times a week for the first two to three weeks, for about fifteen minutes. Keep the agenda narrow:
- Has anyone heard a version of the story that differs from the agreed one?
- Is any reporting line still unclear?
- What are you hearing from your own reports that the rest of us should know?
A week between meetings is long enough for a small misunderstanding to become a rumour. When the syncs stop surfacing anything new, go back to your normal rhythm.
What if a leader privately disagreed?
Bring it into the room before the decision locks. A leader who disagrees deserves a real hearing while the outcome is still open. Once the team decides, they owe everyone a consistent public position, plus a quick way to raise new information. What cannot happen is quiet non-support: nodding in the room, then hedging with their own team.
Then check whether the team has steadied or just gone quiet. A steady team still disagrees openly. Over a few weeks, ask whether the new structure holds without side conversations reopening it, whether the story two levels down matches what you agreed, and whether leaders still raise friction with each other directly. If meetings only got shorter and quieter, that is drift, and it adds to what leadership misalignment already costs. Teams Align is our product for leadership teams.
Frequently asked questions
- How do you keep a leadership team aligned during a layoff or reorg?
- Settle the decision and the reasons inside the leadership team before anyone outside hears a version of it. Agree one explanation every leader will give, confirm the new reporting lines in writing, and hold a short sync two or three times a week for the first few weeks so drift is caught before it becomes rumour.
- What breaks first in a leadership team during a reorg?
- Usually the new reporting lines among the remaining leaders. Scope, budget and who reports to whom change quickly, and if nobody confirms them in writing, two leaders will read the same conversation differently. A close second is one leader hearing the plan before another, which feels like a trust problem even when it was only a scheduling accident.
- Should the leadership team agree on one explanation before announcing a reorg?
- Yes. If leaders give different reasons when employees ask why the reorg happened, people conclude there was no real reason, only private decisions explained after the fact. One agreed explanation, even a short one, holds up better than five leaders each answering honestly from their own partial view of what happened.
- How do you know a leadership team has stabilised after a reorg?
- A stable team still raises friction and disagrees openly in the room. A team that has gone quiet stops raising anything, which is a warning sign. Check that the new structure holds without side conversations reopening it, and that the story told below leadership still matches what the leaders agreed to say.