Great knowledge transfer interviews feel like guided sense-making, not interrogations. The right questions surface undocumented know-how, decision rationale, hidden risks, and successor advice, without drowning people in generic forms. This library organizes prompts by theme so facilitators can run consistent sessions across roles while still tailoring depth. Pair each answer with sources so what you capture stays verifiable when the story is challenged six months later.
Facilitator-ready structure
Themes help you sequence interviews: start with stakes, move through decisions and risks, end with advice and sources.
Spot contradictions early
When answers disagree with tickets or docs, dig in, that is where expensive surprises hide.
Feed WorkFera directly
Use these prompts inside WorkFera workflows so Fera can ask follow-ups automatically and reviewers can bless sensitive lines.
How to use this question library in the real world
Pick a scope before you open with questions: is this an exit interview, a project handoff, or a continuous backup session? Scope changes tone and legal sensitivity. Then choose three to five themes for a sixty-minute session rather than racing through every prompt, depth beats checkbox volume.
Record sources as you go: links to dashboards, tickets, policies, or architecture diagrams. When someone says “everyone knows that,” ask who exactly would still know if they were on leave for a month. That converts implicit confidence into explicit ownership.
Close every session by asking what the successor should validate in week one and what should never be changed without a named approver. Those two answers prevent a surprising amount of rework.
Undocumented know-how and decision history
These prompts expose the gap between official process and lived practice, the shortcuts that exist because tooling is immature, the approvals that happen in chat, and the customer-specific exceptions that never became policy.
- What do only you know about this work?
- What would the next person misunderstand if they only read the documents?
- What context would disappear if you were unavailable tomorrow?
- What decision still affects this work today, and who influenced it?
- What alternative was rejected, and what would convince you to revisit it?
Read
Align vocabulary across HR, IT, ops.
Run
Use checklists live in meetings.
Cite
Every claim points to evidence.
Lock
Promote to clone after review.
Risks, people, systems, and sources
Risk prompts should separate early warnings from catastrophic tail risks. People prompts should capture informal power, not only RACI charts. Systems prompts should reveal which permissions are load-bearing and which integrations are brittle.
- What warning signs should the next person watch, and what is noise?
- Who approves exceptions when policy does not fit reality?
- Which dashboard is directional versus authoritative?
- When sources disagree, which one should be trusted and why?
From reading to doing
Learn
Guides set the sequence.
Try
Templates structure the room.
Automate
WorkFera adds follow-ups + review.
Measure
Fewer repeat questions, calmer transitions.
Successor advice and closing the loop
The best final questions focus on time savings: what meeting to skip, what doc to ignore, what ritual is outdated. They also name social debt, relationships that need repair before the next milestone.
Want Fera to run these prompts with adaptive follow-ups? WorkFera structures capture, review, and Knowledge Clones so answers become durable company memory instead of buried interview notes.
WorkFera creates a structured knowledge transfer workflow. The user adds manager context, sources, and the people involved. Fera then asks targeted questions, detects missing context, structures the answers, and creates reviewed knowledge that can be locked into a Knowledge Clone.
How to facilitate with this artifact
Send the link pre-read with a tight agenda: scope, sources, and who can approve sensitive lines. Keep sessions short and recurring rather than one marathon, memory quality drops when fatigue sets in.
Assign a notetaker to paste links and ticket IDs into answers live; retroactive sourcing weeks later rarely matches the discipline of evidence captured in the room.
- Pre-read + 45-minute focused blocks
- Named reviewer before anything is treated as canonical
- Explicit “definition of done” for the handoff package
Checklist for reviewers
Reviewers should verify every customer- or employee-facing claim against a source, flag speculation, and separate opinion from policy. Prefer redaction over deletion when nuance still helps internal successors.
After approval, lock the version used for Ask Fera and note the refresh owner so the artifact does not silently rot when tools or contracts change.
- Source or owner for each sensitive statement
- Redaction options preserved where internal detail helps
- Locked version + next refresh trigger documented
Templates turn anxiety into a shared script, then WorkFera turns that script into grounded, reviewer-approved memory.
Want Fera to ask these questions automatically?
Capture critical knowledge before it disappears. WorkFera helps teams preserve undocumented know-how, review it, and turn it into trusted company memory.
Request Demo