A few years ago, one of the best engineering managers I’d worked with told me he was leaving. Not leaving the team — leaving the company. He’d built something genuinely impressive: a team of 12 engineers who shipped consistently, calibrated well, and almost never created noise for me. He’d hired carefully and coached his people seriously.
The departure of a strong manager is a stress test your org didn’t schedule. What you discover in the months that follow — about your bench, your systems, your culture — is more instructive than anything a retrospective or an all-hands could surface.
What you find out immediately
Within the first two weeks after a strong manager leaves, you learn whether their team was running on competence or on presence. This distinction matters more than most leaders acknowledge before they’re forced to.
A team running on competence has absorbed the manager’s judgment. The senior engineers can articulate tradeoffs without being prompted. Decision-making doesn’t stall. The team might slow down slightly, but it doesn’t go quiet in the particular way that makes you nervous. A team running on presence, on the other hand, looks functional right up until the moment it isn’t — the manager was the connective tissue, and without them you start to see the gaps: engineers who were never really empowered, a planning process that lived in one person’s head, relationships with partner teams that were entirely bilateral.
I’ve seen both. The second one is harder to fix quickly, and it’s rarely the departed manager’s fault. It usually means the org didn’t invest in creating shared context while that manager was still there.
The succession trap
The instinct, after a strong manager leaves, is to find someone who looks like them. Same technical background, same communication style, same reputation. This is almost always a mistake, and I say this having made it myself at Capital One before I knew better.
Succession isn’t cloning. The question isn’t “who’s most similar to the person who left?” — it’s “what does this team need in the next chapter of its growth?” Sometimes that’s someone with deeper people leadership experience. Sometimes it’s an internal promotion that signals to the team that their own trajectory matters. Sometimes it’s a hire from outside who brings a pattern of thinking the org doesn’t currently have.
The leaders who get this right tend to do something counterintuitive: they slow down. They absorb the team directly for a few weeks before making a succession call. Not micromanaging — listening. The team itself often knows what it needs if you ask the right questions.
What resilience actually looks like
The best org-level resilience isn’t built when a manager leaves. It’s built in the months and years before. It shows up in whether your senior engineers have been given real authority, not just responsibility; whether your team’s processes live in documents or in someone’s head; whether the manager you’re about to lose ever ran a “what if I weren’t here” exercise with their reports.
You can’t predict when a strong manager will leave, but you can make deliberate choices — consistently, over time — that make your org structurally less dependent on any single person. That requires deliberate work, sustained over time, and it doesn’t happen automatically just because you have a strong manager in the seat. Sometimes a strong manager is so effective that you never notice what’s missing — and then they leave.
The metric I care about isn’t whether a team survives their manager’s departure. It’s whether the team was ready for its next chapter before the departure happened.
The thing nobody says out loud
When a great manager leaves, there’s a grief process. It’s real and legitimate — the team feels it, you feel it, and acknowledging that is not weakness.
The mistake is letting the grief become either paralysis or denial. The leaders who navigate this well hold both things at once: genuine appreciation for what the person built, and genuine curiosity about what comes next. Not as performance, but as actual orientation. The org that did good work before will do good work again — and usually it grows in the process of figuring out how.