The short answer
Capture an expert's knowledge by running a deliberate process rather than a farewell chat. Map critical roles and knowledge risks early, hold several structured interviews led by a neutral facilitator, record stories and decisions that live only in the expert's head, and pair the successor with the expert before the last day. Keep knowledge capture separate from the HR exit interview and make it a standing practice.
Key takeaways
- An HR exit interview explores reasons for leaving; a separate knowledge-capture interview extracts processes, contacts, judgment and history.
- NC State research found that only about one in three recent retirees was formally asked to transfer knowledge, while 79% of risk managers rated current transfer processes as weak.
- Tacit knowledge — workarounds, judgment, trade-offs — rarely appears in documents and is best surfaced through recorded storytelling sessions.
- SHRM estimates the cost of replacing an employee at 50% to 200% of annual salary, most of which is lost context, not recruiting.
- Durable retention depends on shadowing, after-action reviews and communities of practice, not on a single exit questionnaire.
Why the exit interview is not enough
When an experienced employee leaves, the organization loses more than hours of work: it loses context, judgment and the unwritten history behind decisions. SHRM estimates that replacing an employee can cost from 50% to 200% of annual salary depending on level, and a large share of that cost is not recruiting but the time needed to rebuild trust and knowledge that walked out the door.
A conventional HR exit interview asks about reasons for leaving and workplace culture. It rarely aims to extract expertise. Practitioners therefore treat knowledge capture as a separate exercise with its own questions and facilitator. In NHS England's Health Education England libraries, for example, a knowledge specialist conducted structured interviews with colleagues before they moved on, using a shared template, so that knowledge transferred between teams rather than vanishing.
- Separate the 'why are you leaving' conversation from the 'what do you know' conversation.
- Assign a neutral facilitator, not the departing person's direct manager.
- Plan a series of sessions rather than one rushed meeting on the final day.
Start early: map critical knowledge and risk
Research by NC State's Enterprise Risk Management Center shows that knowledge-loss risk is poorly handled: only about one in three recent retirees reported being formally asked to transfer knowledge to a successor, while 79% of surveyed risk managers rated current transfer processes as minimally or only somewhat effective.
To avoid this trap, build a knowledge-risk map before someone hands in notice. Identify which systems and processes depend on one or two experts, then overlay the age profile and plans of those holders. Technology leaders advise treating institutional-knowledge loss as an enterprise risk comparable to technical debt or cybersecurity, and logging it in the risk register so that vulnerable roles are renewed or supported deliberately.
- List critical roles and systems that rely on a single expert.
- Cross-reference criticality with the likely departure timing of key holders.
- Prioritize roles whose loss would cause the greatest operational damage.
- Where feasible, begin 18–24 months before a predicted retirement.
The structured capture interview: what to ask
A practical model is the semi-structured interview in three stages: preparation and rapport, information gathering, and closing that surfaces gaps. In the preparation stage, ask the employee to recall tasks, contacts and undocumented rules in advance. During the main stage, ask open questions about what happens when the standard process fails, who loses capability after departure, and where the landmines sit.
Record the conversation with consent, then turn transcripts into reusable artifacts: a contact map, a log of undocumented decisions, and playbooks for typical and atypical situations. Do not rely on a single session. NHS England's experience shows value in running several interviews and asking managers what knowledge they actually need from the leaver, then feeding results back to improve the service.
- 'What will break when you leave?' exposes hidden dependencies.
- 'Who do you call when the normal process doesn't work?' reveals the informal network.
- 'What have you figured out that you never wrote down?' surfaces tacit knowledge.
- Capture the reasoning behind decisions: why this option and what was rejected.
Turn conversations into transferable assets
An interview adds little unless the result is structured and stored where others can find it. Combine several mechanisms: storytelling workshops in which the expert narrates failures and the logic behind workarounds; shadowing, where a successor observes real work; after-action reviews after key events, which examine what was expected, what happened and why; and communities of practice that keep knowledge flowing across teams.
Technology leaders point out that judgment and context transfer best through narrative rather than instructions. Recorded storytelling sessions complement formal documents because they preserve the why behind workarounds and the cautions missing from procedures. Place all material in a shared repository rather than personal drives, so a new hire can actually use it.
- Record expert narratives and pair them with official procedures.
- Run joint working sessions between expert and successor, not just document handoffs.
- Apply after-action reviews to capture lessons after meaningful events.
- Move knowledge from personal folders and mailboxes into a central, searchable store.
Make knowledge transfer a standing discipline
Capturing knowledge only at departure is reactive and usually too late. Durable results come from a culture in which knowledge is shared continuously: mentoring, shadowing, communities of practice and collaborative tools that record lessons as work happens. The goal, as HR executives put it, is to build a team where no single person holds too much of the company's future in their head.
International bodies such as Caritas recommend making knowledge-sharing a requirement when staff change roles or leave: an informal 'pass the baton' meeting with colleagues the leaver chooses, plus an exit presentation to a wider audience. These activities should be built into policy and clearly distinguished from the HR exit interview so they happen systematically rather than by goodwill.
- Write knowledge transfer into the standard offboarding process.
- Establish communities of practice and after-event reviews as routine.
- Appoint an owner for the knowledge-sharing culture.
- Verify effectiveness by asking successors what they still lack weeks after handover.
Put it into practice
Knowledge-Capture Exit Interview Pack
A three-session protocol for extracting an expert's knowledge before departure. Share questions in advance, agree on recording and storage, and run each step in the shared repository rather than in personal files.
- Two weeks ahead: with the manager and successor, list the role's critical tasks, systems, and relationships.
- Session 1, role map: responsibilities, reporting lines, informal contacts, and who seeks whom for advice.
- Session 2, tacit knowledge: 'what breaks without me', 'whom I call on failure', workarounds and why they exist.
- Session 3, decision history: why current approaches were chosen, what was rejected, and what must not be undone.
- After each session: transcribe, summarize, and store in the shared repository with the employee's consent.
- Before departure: run shadowing on two to three real tasks with the successor working under the expert's watch.
- Before departure: compile a 'cautions list' of actions to avoid, each with its reason.
- After departure: agree a 30–60 day availability window for successor questions.
- At 90 days: interview the successor about gaps and close them through the community of practice.
Questions people ask
How does a knowledge-capture interview differ from an HR exit interview?
An HR exit interview explores why a person is leaving and how they experienced the culture. A knowledge-capture interview extracts expertise: processes, contacts, undocumented rules and the reasoning behind decisions. Because the goals and questions differ, many organizations run them separately, with a knowledge specialist or librarian facilitating capture rather than HR, as demonstrated in NHS England knowledge services.
How do I identify which departing employee's knowledge matters most?
Build a knowledge-risk map: identify systems and processes that depend on a single expert, estimate the damage if that person leaves, and overlay likely departure timing. Log institutional-knowledge loss in the risk register, as CIOs do for technical debt. Prioritize roles whose exit would cause the greatest operational damage rather than the most senior titles.
Which questions best surface an expert's tacit knowledge?
Open questions about atypical situations work best: 'What will break when you leave?', 'Who do you call when the standard process fails?', 'What did you figure out that you never wrote down?', and 'Where are the landmines?'. Also ask the expert to narrate a specific past failure and the logic of the fix, because that reveals judgment that no document contains.
What should I do if the expert has little notice before leaving?
Focus on the highest-value items: a contact map, undocumented dependencies and a cautions list. Run at least one recorded interview and one joint session with the successor. Store everything in a shared repository and arrange a short post-departure availability window for questions. You cannot transfer a full career's knowledge in final days, so prioritize ruthlessly.
How do I verify that knowledge was truly transferred, not just documented?
Transfer is complete when the successor can independently perform a critical task. Check this through joint sessions where the successor works under the expert's observation, then interview the successor roughly 90 days after departure about remaining gaps. Documentation without practice often goes unused, so pair it with shadowing, mentoring and after-action reviews.
Sources and further reading
Sources were checked when this page was generated. Confirm changing dates, rules and prices with the original publisher.
- The Myth of Replaceability: Preparing for the Loss of Key EmployeesSociety for Human Resource Management (SHRM)
- Succession Planning Strategies: Capturing Knowledge & Expertise of Seasoned TalentNC State Enterprise Risk Management Initiative
- Sharing ideas, tips and lessons learned from mobilising knowledgeNHS England Health Education England Library
- Institutional MemoryCaritas Europa Knowledge Management Portal
- CIOs face IT knowledge loss as baby boomers retireTechTarget