Inheriting a team with low morale after a reorg

"You've just taken over a team that came out of a reorg badly. Morale is low, two people are interviewing, and delivery has stalled. Your first ninety days?"

What the question is actually testing

Whether you diagnose before you act. "Low morale" is a symptom with several distinct causes, and the intervention that fixes one makes another worse.
Whether you resist the urge to fix it with energy. A new lead's instinct is enthusiasm, a vision, an offsite. To a team that has just been reorganised, that reads as someone who has not understood what happened.
Whether you can deliver something small and real quickly. Trust after a reorg is rebuilt by evidence, not by statements of intent.
Whether you know what you cannot fix. Some of the causes are organisational and outside your authority, and pretending otherwise costs you credibility fast.

Structure: first move, information I would gather, line I would not cross.

The answer

First move: listen, and resist doing anything for two weeks

"My first move is not a plan, it's two weeks of 1:1s and no changes. And I would say that explicitly to the team, that I am not going to change anything for two weeks because I do not understand the situation yet. That sentence does more than anything else I could say in week one, because the thing they are bracing for is another change imposed by someone who was not here."

The questions I would ask in every 1:1, and they are deliberately specific because "how are you feeling" produces nothing:

  What was working before the reorg that isn't now?
  What's the most frustrating part of your week?
  What would you change if you could change one thing?
  What are you working on that you think is pointless?
  Who do you go to when you're stuck? (This maps the real
    structure, which is rarely the org chart.)
  What do you want to be doing in a year?
  What's the thing nobody's telling me?

That last question is the one that works, and asking it plainly, once, in every 1:1, surfaces more than anything else. People will answer it if you have not yet given them a reason not to.

The diagnosis: low morale has five distinct causes

They need different responses and the wrong one makes things worse.

LOSS OF AUTONOMY          The reorg moved decisions away from
                          them. They now need approval for
                          things they used to decide.
                          -> Fixable by me, immediately, and
                             the highest-leverage of the five.

LOSS OF PURPOSE           They no longer see how their work
                          matters, or the thing they cared
                          about was cancelled.
                          -> Fixable by connecting the work to
                             an outcome, IF the connection is
                             real. If the work genuinely does
                             not matter, say so.

LOSS OF PEOPLE            Friends and long-term collaborators
                          were moved or left. This is grief and
                          it does not respond to interventions.
                          -> Time, plus deliberately rebuilding
                             relationships in the new shape.

LOSS OF TRUST             They were told things that turned out
                          to be untrue during the reorg.
                          -> The slowest to repair, and only
                             repairable by consistent small
                             behaviours over months.

WORKLOAD                  The reorg left them with the same
                          work and fewer people, or with an
                          unfamiliar system nobody handed over.
                          -> Fixable, and the most concrete.

The distinction that matters most: which of these can I actually affect? Autonomy and workload I can change this month. Trust I can only rebuild slowly. Grief I cannot fix at all and should not try to, and attempting to will read as not understanding.

Weeks 3 to 6: fix one thing, visibly and completely

Trust after a reorg is rebuilt by evidence, and the evidence has to be small enough to finish and visible enough to notice.

CHOOSE something that is:
  named by several people in 1:1s
  entirely within my authority
  completable in under three weeks
  visible when it is done

GOOD CANDIDATES
  kill a recurring meeting nobody values
  remove an approval step the reorg introduced
  fix the thing that pages them at 3am
  get the environment or tooling that has been "coming soon"
  cancel the project everyone says is pointless
  give back a decision that was taken away

BAD CANDIDATES
  a reorg of my own
  a new process
  a vision statement
  an offsite
  anything that takes a quarter

Killing something is usually better than adding something, because it demonstrates you listened and it costs the team nothing to receive. A new process, however good, is another change imposed by someone new.

And say what you did and why, explicitly linking it to the 1:1s: "Four of you said the Thursday sync was the least useful hour of your week, so it is gone. If I got that wrong, tell me." The link between what they said and what happened is the whole mechanism.

Weeks 6 to 12: the two conversations that matter most

The people who are interviewing.

Do NOT pretend not to know. If two people are interviewing,
somebody has told me, and behaving as if I do not know
insults them.

The conversation: direct, without pressure.
  "I think you might be looking, and I want to say two
   things. First, I'd like you to stay, and here's
   specifically what I'd change to make that worth it.
   Second, if you go, I'll give you a good reference and
   help you leave well. I'd rather you make an informed
   decision than feel managed."

What makes people stay is almost never a counter-offer. It is
usually the work, the autonomy or one specific frustration
that nobody addressed. Ask which it is.

And accept that some will leave, and that is not a failure.
A reorg that broke someone's reason for being there is not
something a new lead can undo in six weeks.

The person who is angry.

Most post-reorg teams have someone who is visibly, vocally
unhappy. The instinct is to manage them out or to route
around them.

Usually they are the most valuable person in the room for the
diagnosis, because they will tell you things nobody else
will. And in my experience they are frequently the person who
cared most, which is why they are angry.

The conversation: "You're the most direct person here about
what's wrong, and that's useful to me. I want to hear all of
it. And I want to be honest that some of it I can fix and
some of it I can't, and I'll tell you which is which."

The thing that changes them is being right about something
and having it acted on.

And the thing to be honest about

"Some of what caused this is above me and I cannot fix it. The reorg's rationale, the reporting structure, the fact that a product they cared about was cancelled. If I pretend I can fix those, I lose credibility the first time I obviously cannot.

So I would say plainly: here is what I can change, here is what I will advocate for and might not win, and here is what is settled and I am not going to relitigate. People can work with that. What they cannot work with is a new lead promising to fix everything and then quietly not."

Naming the boundary is what makes the rest credible, and it is the thing new leads most often get wrong because it feels like admitting weakness.

Where this goes wrong

Arriving with energy and a vision. To a team that has just been reorganised, enthusiasm from someone who was not there reads as not having understood. The vision comes at month four, after you have earned the right to have one.

Changing things in week one. Whatever you change, you changed it without understanding, and you have confirmed that another person is going to impose things on them.

Promising to fix organisational decisions you cannot affect. The fastest way to lose credibility, and it happens the first time you obviously cannot deliver.

Treating the angry person as the problem. They are usually the best diagnostic instrument in the room and frequently the person who cared most.

Pretending not to know that people are interviewing. Insulting, and everyone can tell.

Focusing on delivery first. Delivery has stalled because of the morale problem, and pushing on delivery before addressing the cause reads as caring about output over people, which confirms exactly what they suspect about a new lead.

Trying to fix grief. Some of the loss is people they liked working with, and there is no intervention for that. Time and new relationships, and anything else is theatre.

Interviewer follow-ups

"What if delivery genuinely cannot wait ninety days?" Then I would be explicit about the trade with my own manager rather than quietly doing both badly. In practice I would pick one deliverable, the most important one, protect the team from everything else, and be visible about that protection, because shielding a team from demands is one of the fastest trust-building actions available to a new lead. What I would not do is push on full delivery expectations while the cause of the stall is unaddressed, because that produces a short-term result and two more resignations.

"Two people leave anyway. Did you fail?" No, and I would resist framing it that way. A reorg that removed someone's reason for being there is not something a new lead undoes in six weeks, and some attrition after a bad reorg is the system correcting rather than a management failure. What would be a failure is being surprised, or having them leave without a conversation, or losing the person I most wanted to keep because I never asked what would make them stay. The measure is whether the people who stay are the ones you wanted and whether they stayed for a reason you can name.

"How do you tell the difference between a morale problem and a performance problem?" Carefully, and I would default to the morale explanation for the first couple of months. Someone disengaged after a reorg looks identical to someone underperforming, and treating a disengagement as underperformance is both wrong and unrecoverable. The distinguishing question is whether they were performing before: if they were, the change has a cause and the cause is usually the reorg. If they were not, that is a separate conversation and it can wait until I have context, because starting a performance process in my first month against someone I do not know is a bad idea regardless of whether it is warranted.

"What if the previous lead is still around and people are loyal to them?" I would not compete with them, and I would be careful about anything that implies criticism, because criticising someone the team respects is criticising the team's judgement. If they are still in the organisation I would talk to them directly and early, both because they know things I need and because a visibly good relationship between us removes the loyalty conflict. What creates the problem is the new lead who implicitly frames themselves as the improvement.

"How do you know if it's working at ninety days?" Three signals I would look for. Whether people bring me problems unprompted, because a team that has stopped telling its lead things has made a judgement. Whether the 1:1 conversations have gone from complaints to plans, which is a real shift. And whether anyone new has said something critical in a group setting, because that is the psychological safety signal and it is the hardest one to fake. Delivery is a lagging indicator and I would not read much into it before month four.

"What if the reorg was your idea, or you agreed with it?" Then I would say so if asked, and not volunteer it in week one. Being honest that I think the structure is right while acknowledging the cost is a defensible position, and it is much better than pretending to be neutral, which people see through. But the first two weeks are for listening, and leading with "I think the reorg was correct" makes listening impossible because nobody will tell you anything after that.

Production evidence

Michael Watkins's The First 90 Days is the standard reference for leadership transitions and is the source of the diagnose-before-acting structure and of the distinction between transition types (a turnaround requires different behaviour from a sustaining-success situation).

Google's Project Aristotle found psychological safety to be the strongest predictor of team effectiveness, which is the empirical basis for the ninety-day signals above: whether people bring you problems, and whether anyone will say something critical in a group setting.

Camille Fournier's The Manager's Path covers inheriting a team directly, including the argument against arriving with changes and the specific dynamic of the team member who is loyal to the previous manager.

Research on organisational change and survivor syndrome documents the reduced engagement and increased turnover intention that follow reorganisations among the people who remain, which is the phenomenon being described and is why some attrition afterwards is expected rather than a management failure.

Self-determination theory (Deci and Ryan) supplies the autonomy, mastery and purpose framing that makes "loss of autonomy" a distinct diagnosable cause with a distinct fix, rather than "morale" being one undifferentiated thing.

Interview delivery note

Lead with the restraint and make it explicit, because it is counter-intuitive and it is what is being tested: "My first move isn't a plan, it's two weeks of 1:1s and no changes. And I'd say that to the team out loud, that I'm not changing anything for two weeks because I don't understand the situation yet. That does more than anything else I could say in week one, because what they're bracing for is another change imposed by someone who wasn't there."

Give the diagnosis as distinct causes, because "low morale" as one thing is the weak answer: "Low morale has about five different causes and they need different responses. Loss of autonomy, where the reorg moved decisions away from them, which I can fix immediately and is the highest leverage. Loss of purpose. Loss of people, which is grief and doesn't respond to interventions. Loss of trust, which is the slowest. And workload. The question I'm answering in the 1:1s is which of those this is."

Then the concrete move: "Weeks three to six, I fix one thing completely and visibly. Something several people named, entirely in my authority, done in under three weeks. And killing something beats adding something, because a new process is another change imposed by someone new. Then I say explicitly: four of you said the Thursday sync was the worst hour of your week, so it's gone."

The two conversations, and the second one is the differentiator: "Then the people who are interviewing, and I wouldn't pretend not to know, because somebody has told me and behaving otherwise insults them. And the person who's visibly angry, who is usually the most valuable person in the room for the diagnosis and frequently the one who cared most. What changes them is being right about something and having it acted on."

Close on the boundary, because naming it is what makes everything else credible: "And I'd be honest that some of this is above me. Here's what I can change, here's what I'll advocate for and might not win, here's what's settled. People can work with that. What they can't work with is a new lead promising to fix everything and then quietly not."

The Staff & Team Lead Interview Reference