Leading a Team Through Layoffs and Bad News
In a layoff, your team is not grading your optimism. They are grading whether you told them the truth when it cost you something.
The situation
You've been told the number. Maybe two people on your team, maybe a restructure that removes a function, maybe a budget cut that kills the project three people have given a year to. You found out days before they will, and you've spent those days in meetings you can't discuss, being unusually pleasant in a way everyone has already noticed.
Then the announcement lands and you have to stand in front of people whose colleagues just left, who are afraid they're next, and who will remember for years exactly how you handled the next two weeks. Nothing you say makes this good. What you say determines whether it's survivable with trust intact.
Why it happens
Managers fail this moment in predictable ways. They over-reassure — 'nothing's going to change for this team' — and then something changes, and every future statement they make is discounted. They disappear into meetings because presence is painful, and absence reads as indifference. Or they align themselves with the grief against the company, which feels honest in the moment and leaves the team with no functioning leader and a manager who has publicly given up.
The underlying problem is that most managers try to manage the emotion rather than the information. People can carry hard information. What they can't carry is ambiguity — not knowing whether more is coming, who decides, when they'll know. Ambiguity is what produces the corridor speculation, the resume updates, and the two months of lost work that follow a badly handled cut.
There is also survivor guilt, which nobody names and everybody feels. The people who stayed are working next to empty desks, carrying extra load, and quietly ashamed of being relieved. Left unaddressed, it shows up six weeks later as unexplained attrition among the people you most wanted to keep.
The protocol
- 01Tell the team as a group, in person or on camera, the same day the news is public — not in a written note, and not person by person over a week while rumour outruns you.
- 02Say what you know, say what you don't know, and say when you'll know more. Then actually come back on that date even if the answer is 'still nothing.' That callback is where trust is rebuilt.
- 03Do not predict the future. 'I don't know whether there will be more' is respected. 'This is the last of it' is unforgivable if you're wrong.
- 04Speak plainly about the people who left. Use their names, say what they contributed, say what support they're getting. Sanitised language in this moment tells the room exactly how they'd be talked about.
- 05Hold individual conversations within 48 hours, one per person. Ask two questions: what are you most worried about, and what's on your plate that no longer makes sense?
- 06Re-cut the work visibly within a week. A smaller team with the old list is a demoralised team. Publicly kill something and say who decided it.
- 07Go back to normal operating rhythm deliberately. Grief without structure becomes drift; structure without acknowledgement becomes resentment. You need both.
What to say
The first team conversation
"Here's what happened and what I know. Two roles on this team were cut — Maya's and Dan's. That decision wasn't mine and I'm not going to pretend I agreed with all of it. What I can tell you: their severance and support are in place, the cuts for this quarter are done as far as I've been told, and I don't know what next quarter holds. When I know, you'll know within a day. Ask me anything now, and if I can't answer I'll say so rather than guess."
When someone asks 'am I next?'
"I can't promise you that nobody else will be affected — if I did, you shouldn't believe me. What I can tell you is that nothing on my desk right now involves your role, and if that changes you will hear it from me directly and early, not through a meeting invite from HR."
Addressing the ones who stayed
"Some of you feel guilty, and some of you feel relieved and then feel bad about that. Both are normal and neither is a problem. What I need from you isn't extra hours to cover the gap. Bring me the list of what you're carrying and I'll cut things off it — that's my job this month."
What not to do
- —Don't announce by email and then go quiet. Written first, absent second is the worst possible combination.
- —Don't perform optimism. 'This makes us leaner and stronger' in week one is heard as contempt.
- —Don't badmouth the decision-makers. Honest disagreement stated once is leadership; ongoing complaint is abdication.
- —Don't quietly redistribute the departed workload and hope nobody notices. They notice in four days and resent it for a year.
- —Don't skip your own support. A manager running on no sleep and no outlet makes worse calls in exactly the month that calls matter most.
Signals you got it right
People ask you direct questions in the open rather than speculating in side channels. Corridor speculation is the measurable output of a manager who has not said enough.
Nobody is quietly absorbing the departed workload. If the list did not visibly shrink, the team learned that the cut cost the company nothing and cost them a weekend a month.
The people you most wanted to keep are still arguing with you about the work eight weeks later. Engagement is the last thing to return and the only reliable evidence that trust survived.
The one thing that changes everything
Commit to a date and keep it. 'I'll tell you everything I know every Friday at 4, even if the answer is that nothing has changed.' Uncertainty is bearable when it has a rhythm. Four Fridays of a manager showing up and telling the truth — including the uncomfortable truth that there's no news — does more for a shaken team than any single well-worded speech.
Facing this right now?
Describe your situation and get a diagnosis, one principle, a named protocol, and the exact words to say.
Describe your situation and get a diagnosis →