KM / Knowledge Exit Interview Addendum

Purpose

• This addendum extends the Knowledge Exit Interview Process for IT and higher-education environments, with emphasis on shared governance, long system lifecycles, compliance, and institutional memory

User

• Knowledge Management (Facilitator)
• Departing Staff Member (Subject Matter Expert)
• Manager / Asset Owner / Group Leader
• Successor / Backup (if available)

IT / Higher-Ed Knowledge Domains

When scoping and prioritizing Knowledge transfer or capture, explicitly assess the following domains:

1. Academic & Administrative Context

• Academic calendar dependencies (start/end of term, grading, registration)
• Shared governance or committee-driven decisions
• Faculty vs. staff vs. student support nuances

2. Systems & Applications

• Enterprise systems (ERP, SIS, LMS, IAM, HR, Finance)
• Shadow systems or spreadsheets used to bridge gaps
• Integrations, data flows, and upstream/downstream dependencies
• Vendor relationships and renewal cycles

3. ITSM & Operations

• Incident, request, and change workflows
• Known problem areas and recurring tickets
• Monitoring, alerting, and escalation thresholds
• On-call or after-hours practices

4. Security, Risk & Compliance

• FERPA, HIPAA, PCI, GDPR (as applicable)
• Access provisioning/deprovisioning nuances
• Audit artifacts and evidence sources

5. Institutional Memory

• “Why we do it this way” decisions
• Past failures, near-misses, and political landmines
• Historical compromises or technical debt