Skip to main content
HR Strategy4 min read

What a Team Loses When Someone Leaves

Departure checklists are thorough about the wrong things. Hand over the accounts, document the processes, transfer the client relationships, revoke the access. All necessary, all recorded. Then the person leaves and something else goes with them that was never on any list.

Every long-standing employee is holding a map of who knows what. They know that the finance question is really a question for Priya, that the design team's calendar is meaningless and you should just ask, that a particular client sounds angry when they are actually fine. None of that is written anywhere. It exists as relationships and accumulated context, and it walks out on the last Friday.

Teams feel this for months afterwards in a form they usually misattribute. Things take longer. Questions get asked of the wrong people. Two colleagues who only ever talked through the person who left stop talking altogether. Everyone assumes they are still absorbing the workload, and partly they are, but a good share of it is the missing map.

There is a second, quieter loss. The person who left was a link between people who are not otherwise linked, and removing a link can disconnect a whole pocket of the team. This is most visible when a long-serving employee goes: suddenly two functions that got along fine are cautious with each other, and nobody can identify what changed.

Knowledge transfer handles the documented part and not this part. You cannot hand over a relationship in a thirty-minute session. What you can do is make the team less dependent on any single connector in the first place, which mostly means people having enough direct contact that no relationship is running entirely through a third party.

It is worth being clear-eyed here. This is not something to fix during a notice period. By the time a resignation lands, the only options are damage control. The work happens in the ordinary months, and it is the same unremarkable work that pays off everywhere else: people from different parts of the team regularly having reasons to interact directly.

One practical thing does help at the moment of departure, and almost nobody does it. Ask the person who is leaving who they think should now be talking to whom. They know. They have been the bridge for years and they can usually name every pair of people who never quite connected without them. It takes ten minutes and it is more useful than most of the checklist.

Key takeaway

Departing employees take an undocumented map of who knows what, plus the links they personally held together. Handover sessions cannot transfer that. Teams where people already talk directly lose less, and asking a leaver who should now be talking to whom recovers more than any process document.

Your team’s own answers make better trivia than any question bank.

← Back to the blog