When a key person leaves: the first 48 hours and the next three months
Echipa HR 365 · reviewed 2026-09-14 · 5 min read
When someone load-bearing leaves, you get two risks that are handled differently: an operational one, immediate — what stops if they are gone — and a morale one, which appears two or three weeks later, when the team starts wondering why they left and whether they should too.
The first 48 hours
In this order, not another
- Manager — the list of things that stop if they are unavailable from tomorrow — not in two weeks, from tomorrow
- Manager — for each one, who could take it over and what they are missing in order to
- Manager and HR — the decision about the announcement: who finds out, when, in what order
- Manager — the conversation with them about what they would like to leave behind — most people want to leave things in good shape, if asked
About the counter-offer
The first instinct on an important resignation is to try to stop it. It rarely works and usually postpones the departure by a few months — because the real reason, in most cases, was not the salary, and if it was, it stays solved only until the next comparison.
The second cost is less visible and more durable: the team finds out. From that moment, resigning becomes, in everyone’s perception, the lever by which a raise is obtained — and that produces, over the following months, exactly the conversations you do not want.
The second risk: morale
It arrives after two or three weeks, not immediately, and it is harder to manage than the operational one. The departure of someone respected plants a question in everyone else’s mind that they never say out loud: if they left, what do they know that I do not?
| Helps | Makes it worse |
|---|---|
| An honest announcement, with what changes concretely | Silence or minimising it (“it is not a big deal”) |
| An individual conversation with those most affected | One general message to everyone, and nothing else |
| A visible coverage plan, even an imperfect one | Weekly improvisation, visible to everyone |
| Public acknowledgement of their contribution | Erasing them from the conversation, as if they had never existed |
The last row matters more than it looks. How you talk about someone after they leave is read by everyone else as a forecast for themselves — and a company where former colleagues vanish from the vocabulary produces, over time, people who do not get attached.
What to prevent, for next time
- Identify the critical roles: the ones whose month-long absence visibly stops or slows something. There are usually two or three.
- For each, check whether anyone could take over within six months. If not, that is the urgent one.
- Reduce concentration: work done in pairs, even occasionally, shrinks the surface of the loss more than any documentation.
- Watch for signs of overload in those people. The indispensable ones are, statistically, also the most loaded.
The fourth point closes the circle: a key person is key precisely because they carry a lot, and whoever carries a lot is the most likely candidate to leave. Real prevention is not a succession plan on paper, it is reducing their load before they reach the limit.
One last thing, true of any significant departure: how you treat the person in their final two weeks is read by everyone else as how they will be treated one day. A departure handled well — no sudden coldness, no exclusion from conversations, a public thank-you where it is warranted — costs nothing and buys trust from the people staying. One handled badly becomes the story the team tells about the company, long after the person has gone.
Do I tell the team it was a critical role?
Not in those terms. Say what changes concretely and what is being covered. Declaring someone “irreplaceable” puts everyone else in an uncomfortable position and helps nobody.
Do I take them off projects immediately?
No, unless there is a concrete reason. Immediate exclusion damages both the handover and the message to the team — and the risk it covers is usually theoretical.
What if they are going to a competitor?
Apply whatever the contract provides, if anything, and behave as fairly as in any other departure. Disproportionate reactions become known immediately and cost more, in reputation, than the risk avoided.
Where to start
Without anyone leaving: write the list of roles whose month-long absence would stop something. If there are more than three in a small company, you have a concentration problem, not a succession problem.
Then, for each, check the signs of overload. The best moment to prevent a key person leaving is six months before they start thinking about it.
What not to do in the first days
- Do not reorganise the team immediately. The first reaction is almost always too broad; wait two weeks.
- Do not promise the team that “nothing changes”. It does, visibly; the promise costs credibility.
- Do not split their work equally among everyone. Responsibility dilutes and nobody actually takes it over.
- Do not start recruiting before updating what the role does. After two years, their job is no longer the one in the description.
The third point is the most frequent and the most counterproductive: an “equitable” split produces a situation where everyone has a little and nobody answers for anything. Better two people taking over whole areas, even if it is harder for them.
A skills matrix that shows who is covered by a single person
Columns with only one name are flagged automatically, so the continuity risk is visible before the resignation — while it can still be reduced.
Free account, every module for 7 days, no card required.