The people who stayed needed more from us than the ones who left
What leaders get wrong about the aftermath of a restructuring and what to do instead
Another lesson I learned the hard way.
I once had to lay off close to 100 people in a single go. The company rented a hotel conference room. Managers delivered the group message. Then a team of us met with each person, one by one, to walk each individual through next steps.
When it was over, we all went back to the office and leadership expected everyone to carry on.
What followed was textbook, and entirely avoidable. Survivor syndrome set in fast. Performance dropped. A handful of people burned themselves out trying to prove they deserved to stay. Teams that used to collaborate started competing. Innovation simply stopped. People became risk averse.
The company had reduced headcount but hadn’t reduced the workload — so the people who remained were quietly drowning, too afraid to say it out loud and become the next in line.
Nobody talked about it. That was the real problem.
What leaders typically do after a restructuring?
They move on. Way too quickly, actually. The unsaid message becomes: we’re through the most difficult part, now we focus forward. Meetings resume. Targets stay the same. The org chart has new names in some boxes.
Meanwhile, the team watches all of this and learns something they’ll never unlearn: loyalty doesn’t protect you here.
That lesson kills effort. People stop going above and beyond. They do their job, nothing more, and they update their CVs quietly. The best ones — the ones you most need — leave 6 to 12 months later. Not because of the layoff, but because of what came after it.
What most leaders miss is survivor guilt.
The people who kept their jobs didn’t just feel relieved. Many — dare I say most — felt guilty. Why them and not me? That guilt either pushes people into unsustainable overperformance (the heroes burning out) or into quiet disengagement — a form of grief that looks like low motivation but runs much deeper.
You cannot manage your way through that with a strategy update and buying the team a nice dinner.
What actually needs to happen:
→ Acknowledge what happened. Not a general “this was difficult for everyone.” Name the loss. The team lost colleagues, stability, and trust in the institution. That deserves to be said out loud by a leader, not processed in silence.
→ Separate the “processing” conversation from the performance conversation. Don’t ask someone how they’re doing and pivot immediately to Q3 targets. Those are two different conversations. Give each one its own space.
→ Do the workload math. Headcount went down. The work didn’t. Sit with each person and understand what they’re now carrying. Redistribute where possible. Give people the tools — and sometimes the training — to be successful in the new structure. Pretending the load is manageable when it isn’t is how you burn out your best people.
→ Create deliberate listening structures — not just an open-door policy. Few people reach out after a restructuring. They don’t trust it’s safe. Schedule it. Make it a specific, protected conversation with no performance agenda. Ask: what do you need to do your job well right now? Then actually respond to what you hear.
→ Tell people what is not changing. Certainty — even if partial — is stabilizing. After a restructuring, people are scanning every signal for the next threat.
The hardest part of leading through a restructuring is that the people who stayed need more leadership than the ones who left and they’re almost always the ones who get the least.
That gap is where recovery happens. Or doesn’t.
Have you been on either side of this — as a leader or as a survivor? What was the one thing that made the difference?
