How to Reorg Without Killing Morale
The fear that stops founders from restructuring when they should is that it will cost them people. That fear is well-founded and slightly misplaced: reorgs do lose people, and what loses them is almost never the structural change itself. It is the days or weeks of ambiguity around it, the discovery that they were told after their peers, and the sense that something happened to them rather than being explained. All three are avoidable. This page is the people side of a restructure.
What’s inside
The three questions everyone is asking
What actually damages morale
The individual conversations
Naming the losses
The people who lose scope
The ones who leave anyway
The recovery curve
Where Blomma fits
The three questions everyone is asking
The moment someone learns a reorg is happening, they stop working and start calculating. They are answering three questions, in this order, and until they have answers they are not doing their job.
What happens to me?Reporting line, scope, title, whether they still have a job. Nothing else registers until this is answered.
Who do I work for?Specifically, and whether that person values them. A new manager is the single largest variable in someone’s daily experience of work, and a reorg that changes it without explanation is the most common trigger for a resignation.
Is my standing better or worse than yesterday?People read structure as status, accurately. A narrower scope, a new layer above them, or a peer promoted over them is a status event, and pretending otherwise does not work.
Every mechanic on this page exists to answer those three, for every affected person, as fast as possible. If you do only that, you will do better than most reorgs.
What actually damages morale
Worth separating the real causes from the assumed one, because founders spend their effort in the wrong place.
Ambiguity duration.Every hour between learning something is changing and learning what it means for you is an hour of anxiety, and the anxiety converts into a story about politics because a vacuum fills with the worse explanation. This is the single biggest driver and it is entirely under your control.
Learning about yourself in a group setting.Hearing your reporting line changed in an all-hands, alongside forty colleagues, is a small humiliation. It is also the most reliable cause of resignations over process rather than substance.
A story that does not match the visible facts.If you say the change is about customer focus and everyone can see it is about two executives who cannot work together, you have spent credibility and gained nothing. People are good at this.
Being denied the loss.Telling someone whose scope halved that this is an exciting opportunity insults them. They know what happened.
Notice what is not on the list: the change itself. Teams absorb structural change routinely when it is explained, sequenced, and honest about costs.
The individual conversations
The core of the whole thing. Every person whose manager, scope, or title changes hears it individually, before any group communication, on the same day.
Keep each one short and answer the three questions in order. Who you report to now. What you own. What is not changing. Then why the change is happening at all — the company-level reason, briefly.
Lead with their situation, not the company rationale. You have been thinking about the strategic logic for weeks; they need to know about their job. Opening with two minutes of context while they wait to find out what happens to them is a common and avoidable cruelty.
Be specific about what is not changing. This is the most underused sentence in a reorg. Uncertainty expands to fill the available space, so naming the boundaries — same team, same project, same compensation, same trajectory — removes most of the anxiety at no cost.
Sequence by risk. The departing-scope people and the new-manager people first, because they are the flight risks. Then the rest.
And have their new manager in the conversation, or immediately after. The relationship starts at that moment, and starting it with a five-minute introduction rather than an email materially changes the first month.
Naming the losses
Every reorg costs someone something — scope, proximity to you, a manager they liked, a project they cared about, a title they had earned. Saying so plainly is what makes the rest of your message credible.
The instinct is the opposite: present the change as upside for everyone, because that seems kinder and easier to defend. It does not work, for a structural reason. Your audience can see the losses. When you describe a change they can see costs them something as pure benefit, they conclude either that you cannot see it or that you are managing them. Both are worse than the loss itself.
So name it. “This means you no longer own the analytics team, and I know that matters to you. Here is why we are doing it, and here is what you own instead.” That sentence is uncomfortable to say and it is the reason people believe the next thing you tell them.
The same applies at company level. “This will slow down cross-team work for a quarter while people settle” is a real cost, and acknowledging it in the all-hands buys you enormous credibility when the slowdown arrives — because you predicted it rather than being caught by it.
The people who lose scope
The hardest conversations, and the ones that determine whether your senior team stays intact.
Tell them well before the announcement — ideally two weeks, individually, as a conversation rather than a notification. A leader who learns their scope shrank at the same time as their team cannot lead through the change, and will usually leave.
Be straight about the reason and keep it about the company’s needs rather than their shortcomings, unless it genuinely is about performance — in which case that is a different conversation and should have happened already, separately. Conflating a structural change with unaddressed performance feedback is unfair and it will not land.
Give them something real. Not a consolation title — a genuine area of ownership, a problem they have wanted, or a defined path back. If there is nothing, say that too, because a hollow offer is worse than none.
And accept that some will leave. A leader whose scope has genuinely narrowed has a legitimate reason to look elsewhere, and handling the conversation well means they leave in six months on good terms rather than in three weeks angrily. That difference is worth a great deal.
The ones who leave anyway
Some departures are not preventable and should not be treated as failures of the process.
Expect a few resignations in the two months after a reorg, concentrated among people whose manager changed and people loyal to someone whose scope shrank. That is a normal cost of a real structural change, not evidence you handled it badly.
What you can control is whether they leave well. A departing person who was told honestly, treated with dignity, and given a proper handover becomes someone who speaks well of the company and occasionally returns. One who was surprised and managed becomes a story that circulates for years, including to your candidates.
And resist over-correcting. The temptation after two resignations is to soften or partially reverse the change, which converts a difficult quarter into a permanently unclear structure and teaches everyone that structure changes under pressure.
The recovery curve
Knowing the shape prevents panic.
Weeks one and two: reduced output, high anxiety, a lot of private conversation. Normal.
Weeks three to six: things start working, and the specific things that are wrong become visible. This is the most useful period — the problems surfacing now are real and fixable.
Week six: the correction. Fix the three or four details that turned out wrong, visibly, and say you are fixing them because the review found them. Announcing this review date on day one is the highest-leverage thing in the whole process, because it makes dissent legitimate and stops people working around problems instead of reporting them.
Months three to four: settled, with the residual departures behind you.
If you are still in week-one conditions at week eight, something specific is wrong — usually an unanswered question about someone senior, or a story circulating that you have not addressed.
Where Blomma fits
The part of a reorg that determines whether it costs you people is a sequence of individual conversations, several of which are genuinely hard — telling a leader their scope is shrinking, telling someone their manager is changing, standing in an all-hands and naming a cost rather than selling a benefit.
Blomma is an always-on AI career coach with no stake in your structure. Use it to prepare each of the difficult individual conversations, particularly the scope-reduction ones, where the opening two minutes determine whether the person stays and leads or starts looking. Use it to draft the all-hands message with the losses named rather than smoothed. And use it in the weeks afterwards, when you will hear a version of the change you did not intend and have to decide whether to correct it publicly.
There is a second application: your managers are the ones delivering most of these conversations, about a change they did not design, and most have never done it. That is coachable, and it is where reorg communication actually breaks down..
Teams absorb structural change. What they do not absorb is finding out late, from the wrong person, in a version that denies what it cost them.