Team reductions have become a normal part of engineering leadership over the past few years, not an exception. The decisions themselves — how big a team should be, which roles get cut — are made above and beyond what any single manager controls. What’s left to the manager is everything that happens next: whether the team keeps functioning, keeps delivering, and keeps trusting its leadership through the process. That part is a skill, and it’s worth treating as one.
The work doesn’t pause for the reorg Link to heading
The first instinct when headcount changes is to treat it as a standalone event — announce it, absorb the shock, move on. In practice, the roadmap doesn’t wait. Customers don’t wait. A team that’s still expected to ship while absorbing a smaller org chart faces a real risk, and it usually isn’t the reduced capacity itself — it’s letting delivery visibly wobble in the weeks right after, because that’s exactly when the remaining team is watching closest for signs of chaos.
What helps is re-scoping before re-committing. Rather than assuming the same roadmap can survive with fewer people, sit down with your leads within days, not weeks, and rebuild the near-term plan around actual capacity. Saying “here’s what changes, here’s what doesn’t, here’s why” — even when the honest answer is “we’re cutting scope” — does more for trust than pretending nothing has changed.
Overcommunicate, especially the parts that feel uncomfortable Link to heading
It’s easy to underestimate how much silence gets filled with worse assumptions than the truth. If you’re not ready to answer a question, say so directly instead of going quiet. Whatever you can commit to — how decisions about the team’s structure will be made, what won’t change, when there will be more information — say it clearly and repeat it often, because a message given once in a moment of stress rarely lands the first time.
The leads under a manager are usually doing the same work one level down, fielding the same hard questions from their own engineers. Keeping them informed early, even with incomplete information, means they aren’t caught flat-footed in their own 1:1s.
Protect focus, not just headcount Link to heading
The instinct after a reduction is to ask everyone to “do more with less.” That framing tends to be corrosive. A more useful question is: what should the team stop doing? Every restructuring is also a forcing function to cut initiatives that were marginal to begin with. Being explicit about what’s being deprioritized — and standing behind that decision when pressure comes from stakeholders who want everything to continue — matters more for morale than any speech about resilience.
What this comes down to Link to heading
Restructuring tests whether the trust a manager built beforehand was real. The people who stay through it rarely stay because the situation was good — they stay because how it was handled gave them a reason to believe the people running the team would be straight with them. That’s the part of the job that doesn’t show up on a roadmap, but it’s the part that determines whether the team on the other side of the change is one worth building on.