4.8Preserving Institutional Knowledge When Team Members Leave

When someone announces they are leaving, you have a limited window to capture what they know. Here is a structured approach.

The Knowledge Extraction Interview

Schedule 2-3 one-hour sessions with the departing team member. Record them (with permission).

Session 1: Systems and Processes

• What systems do you own or primarily test?
• What are the most common failure modes?
• What workarounds do you use regularly?
• What is not documented that should be?

Session 2: Relationships and Context

• Who are the key contacts for each system?
• What political or organizational context is important?
• What decisions were made and why?
• What would you do differently?

Session 3: Active Work and Handoff

• What is in progress? What is the status of each item?
• What commitments have been made to stakeholders?
• Where are the credentials, access keys, and configuration files?
• What are the biggest risks in the next 3 months?

Knowledge Handoff Checklist

• All active work items documented and assigned to a new owner
• Access to all relevant systems transferred
• Documentation reviewed and updated
• Key relationships introduced (the departing person introduces their replacement to stakeholders)
• Recorded walkthroughs of complex processes stored in shared location
• Playbook sections owned by the departing person reassigned