What Happens to 8 Years of Expertise When Your Best Person Resigns?

It starts with a resignation letter.

Imagine Rhea, a VP of Operations who has spent eight years with your organisation. She knows which clients need a call before a concern becomes an escalation, which vendor commitments need a second check, and why a process that looks inefficient on paper exists in the first place.

On Friday afternoon, she hands in her notice.

The team can recruit a successor. The harder question is how much of Rhea's judgement that successor will have to rebuild through trial and error. Rhea and the colleagues in this article are illustrative characters, but the planning problem is familiar: critical work depends on experience that too few people share.

To reduce knowledge loss when an employee leaves, identify the expertise most at risk, pair its holder with colleagues who need it, document decisions and exceptions, and give those colleagues opportunities to practise with feedback. Structured mentoring helps make this an ongoing part of work, supported by documentation, shadowing, and cross-training.

The cost goes beyond filling the vacancy

Recruitment fees, onboarding time, and reduced productivity are visible costs of employee turnover. In a 2019 article about US employee turnover, Gallup estimated replacement costs at one-half to twice an employee's annual salary. That estimate concerns employees generally. It is not a senior-hire benchmark or an India-specific cost model.

For your business case, use your own recruitment costs, time to proficiency, and operational disruption. Include the time experienced colleagues spend helping a replacement and the cost of preventable rework. Avoid adding these again if they are already included in your replacement-cost calculation. Our guide to building a mentoring business case for your CFO offers a structure for the discussion; populate it with your organisation's actual figures and explicit assumptions.

Knowledge loss also shows up in small delays: a customer issue takes longer to diagnose, a team repeats an abandoned approach, or a decision waits because nobody knows who can approve an exception.

Some of this is tacit knowledge: judgement and practical know-how developed through experience that can be difficult to explain fully. Institutional knowledge is broader. It also includes documented processes, past decisions, relationships, and shared organisational context.

Why a handover document needs a learning process

A good handover document is valuable. It can explain a process, record why a decision was made, identify common exceptions, and point to the right people and records. But reading those notes does not demonstrate that a successor can recognise an unfamiliar problem or make a sound decision under pressure.

Rhea might document how to escalate a supplier delay. Her colleague Karan also needs to understand what she checks before escalating, which trade-offs matter, and when the usual approach is inappropriate. Watching her handle a case, discussing her reasoning, and trying a similar case with feedback makes that learning more concrete.

NASA's Knowledge Continuity guide for supervisors recommends combining mentoring with role documentation, cross-training, lessons learned, and shared resources. For departures, it also describes transition plans, shadowing, interviews, and continuity books. This is practical guidance from NASA's context, not evidence of a guaranteed commercial return.

The useful principle is to build a way for people to find knowledge, discuss it, and apply it. A mentoring programme and a shared knowledge repository serve complementary purposes.

Find the knowledge your team cannot afford to lose

Start with a conversation between the manager and the people doing the work. Ask which decisions, relationships, or recurring exceptions would become difficult if one colleague were unavailable tomorrow.

• Which customer or supplier relationship depends on one person's context?
• Which process needs the same expert whenever something unusual happens?
• Which past failure would a new colleague be likely to repeat?
• Which responsibilities have no colleague who can currently provide cover?

Prioritise areas where disruption would have a serious consequence and where learning takes time. Include specialists and experienced individual contributors as well as managers. Match the learning opportunity to the people who will need the capability in their work.

For leadership roles, connect this assessment with your leadership pipeline and succession planning. Naming a potential successor is the beginning; establishing what they can handle independently is the next step.

A five-step knowledge-transfer checklist

Use the following workflow for one priority area before expanding it across a department. The steps are a practical starting point, and the time required will depend on the complexity of the work.

1. Define one observable outcome

Replace a broad goal such as learning operations with a task someone can demonstrate. In Rhea's case: Karan can assess a supplier delay, explain the options, and recommend an escalation route within the team's existing approval rules.

Record the knowledge holder, the learner, the manager responsible for the outcome, and a review date. Give both participants protected time for the work.

2. Work through a real decision

Choose a recent case and ask the expert to explain it from the information available at the time. Avoid reducing the discussion to a polished account of the final answer.

• What first made you think there was a problem?
• What information did you check before acting?
• Which options did you rule out, and why?
• What would have changed your decision?
• When should someone seek help instead of deciding alone?

Agree on a specific task for the learner to complete afterwards. Clear expectations and follow-through also address problems discussed in our article on why mentoring relationships fail.

3. Capture the reasoning in a reusable note

Write a short decision note in your team's shared repository. Include the situation, the signals checked, the decision, the alternatives, the exceptions, and the escalation contact. Link to the current process and identify who will keep the note up to date.

This is a suggested working format that your team can maintain in its existing tools. A note becomes useful when another colleague can locate it and understand when the guidance applies.

4. Let the learner practise

Have the learner observe the work, then take the lead on a suitable case with the expert available to review it. Use a simulation where a live mistake could carry significant consequences. Ask the learner to explain the decision, including uncertainty and the point at which they would escalate.

A correct answer reached by guessing is a reason for more discussion. So is a response that follows the usual process without recognising an important exception.

5. Check readiness and close the gaps

The manager and expert should review evidence against the agreed outcome. Record whether the learner can explain the task, perform it with support, or perform it independently within their authority. Give specific feedback and schedule another attempt where needed.

For critical work, develop more than one capable colleague where feasible. Revisit readiness when the process, technology, or responsibilities change.

What this looks like in Rhea's team

In this illustrative example, Rhea and Karan choose supplier escalation as their first priority. They review an old delay and discover that the first warning was a change in delivery commitments, before the supplier missed a deadline.

Karan writes down the checks Rhea performed and the circumstances in which she involved procurement. He then works through a different scenario. His first response misses a contractual constraint, so Rhea explains its significance and they revise the note together.

At the next review, Karan must explain a suitable response to a new case and identify who has authority to approve it. The manager records the evidence and any remaining support needed. The useful result is a clearer view of what Karan can do and what still depends on Rhea.

Measure capability alongside participation

Session attendance and completed tasks help you see whether a programme is running. To assess knowledge transfer, also track outcomes tied to the work:

• Capability coverage: how many priority areas have another colleague who has demonstrated the required capability.
• Time to proficiency: how long learners take to meet a predefined standard.
• Operational evidence: changes in relevant rework, avoidable escalations, or delays, with their context recorded.

For example, if six of ten assessed priority areas have a capable backup, coverage is 60%. This is an illustrative calculation, not an industry benchmark or a built-in Mentorgain score. Review the remaining four areas individually because their business consequences may differ.

Compare results with a baseline and investigate other changes that could explain improvements. A better outcome after mentoring does not, by itself, show that mentoring caused it.

If the resignation letter has already arrived

Use the remaining time to reduce the largest gaps. Agree on the most important open decisions, recurring exceptions, and relationships to transfer. Schedule focused discussions around these items, make introductions, and check that the team can access the relevant records.

If a successor has not been appointed, assign an interim owner for each priority area. Have that person explain the current situation and next action back to the departing colleague. Record unresolved questions and who will address them after the departure. An available notice period is a constraint to plan around; it is not a promise that years of expertise can be transferred in full.

How Mentorgain supports the programme

Mentorgain can help teams organise the mentoring activity behind this approach. Its journeys and tasks support goals, assigned actions, and progress tracking. Session tracking supports meeting records, notes, and follow-up actions, while reporting and surveys help programme owners review participation and feedback.

Your managers and experts still define the critical knowledge, review the learner's work, and decide whether the required capability has been demonstrated. Keep operational decision notes in an appropriate shared repository and connect the mentoring activity to those resources.

Start with one team and one area of expertise that currently depends on a single person. Book an exploratory call with Mentorgain to discuss how to organise the mentoring goals, sessions, and follow-up around it.