100 Knowledge Transfer Questions to Ask Before Someone Leaves

Generic handoff forms produce generic answers. The questions below help facilitators surface decisions, risks, relationships, sources, and advice successors need. Use them in themed sessions, not one marathon meeting.

Responsibilities and active work (1-15)

• What outcomes are you personally accountable for this quarter?
• Which work is on track, at risk, or paused?
• What will slip if you are not here next week?
• Which commitments were made to customers or executives?
• What recurring ceremonies actually matter?
• Which tasks look small but carry large blast radius?
• What did you inherit that still confuses you?
• Which projects should be deprioritized after you leave?
• What approvals only you can grant today?
• Where are handoffs already in flight?
• What reports do leaders trust versus ignore?
• Which SLAs are at risk?
• What seasonal patterns affect workload?
• Which backlogs are secretly stale?
• What would you stop doing if you had authority?

Decisions and trade-offs (16-30)

• What major decisions did you make in the last six months?
• Which alternatives were rejected and why?
• What technical debt was accepted knowingly?
• Which shortcuts would you not repeat?
• What would you decide differently with more time?
• Which policies you follow differ from written policy?
• What customer promises constrain engineering?
• Which vendors are tolerated for non-obvious reasons?
• What architecture choices are load-bearing?
• Which experiments failed instructively?
• What data definitions changed meaning over time?
• Which metrics drive behavior you dislike?
• What security trade-offs were explicit?
• Which legal or compliance lines are sensitive?
• What decisions await successor judgment soon?

Risks and incidents (31-45)

• What incidents could recur if context is lost?
• Which risks are live but not in the risk register?
• What near-misses should successors know?
• Which on-call pages are outdated?
• What failure modes scare you most?
• Which customers are fragile right now?
• What single points of failure do you carry?
• Which dependencies are brittle?
• What manual steps are error-prone?
• Which alerts are noisy versus actionable?
• What disaster recovery gaps exist?
• Which audits found issues still open?
• What regulatory deadlines loom?
• Which third parties could surprise us?
• What would you escalate on day one?

People and relationships (46-60)

• Who must be consulted before major changes?
• Which stakeholders prefer email versus chat?
• Who can unblock political issues?
• Which partners are allies versus skeptics?
• Who owns conflicting priorities across teams?
• Which executives want detail versus summary?
• Who carries informal influence?
• Which customers require executive touch?
• Who reviews sensitive content well?
• Which teams depend on you silently?
• Who should the successor meet in week one?
• Which relationships need careful introduction?
• Who was burned by past incidents?
• Which mentors helped you most?
• Who should not be surprised by the transition?

Systems, sources, and workarounds (61-80)

• Which system is authoritative for each domain?
• Where do dashboards disagree?
• Which repos or folders are canonical?
• What access paths are non-obvious?
• Which runbooks are trusted?
• What tickets best explain current state?
• Which policies actually govern work?
• What recordings or notes exist?
• Which integrations are fragile?
• What workarounds are load-bearing?
• Which scripts only you run?
• What environments are dangerous?
• Which credentials rotate unusually?
• What data exports are incomplete?
• Which tools are slated for retirement?
• What license or contract quirks matter?
• Which dashboards require interpretation?
• What logs do you read first in incidents?
• Which automations fail quietly?
• Where is source truth disputed internally?

Mistakes, advice, and validation (81-100)

• What mistakes should successors avoid repeating?
• What do new owners usually misunderstand first?
• Which validations should happen in week one?
• What questions will stakeholders ask immediately?
• Which documents look complete but are not?
• What would you teach in a two-hour bootcamp?
• Which escalations patterns work?
• What cultural norms are unwritten?
• Which rewards or penalties shape behavior?
• What would you document if you had another week?
• Which clones or notes already exist?
• What is missing from those clones?
• Who should review sensitive answers?
• What access must successors receive day one?
• Which rituals build trust quickly?
• What signals mean the handoff succeeded?
• How should successors update this memory?
• What should be captured continuously after you leave?
• Which questions should the next exit ask?
• What else keeps you up at night about this transition?