Tacit Knowledge Transfer Interview Script and Facilitator Guide

Purpose

This script helps a facilitator capture tacit expertise from a subject-matter expert (SME) in a single 45–60 minute conversation and produce usable inputs for playbooks, onboarding, checklists, and knowledge artifacts. It focuses on concrete decisions, tradeoffs, recurring exceptions, hidden heuristics, and reproducible artifacts.

Before the interview (Facilitator checklist)

• Schedule 45–60 minutes and confirm a quiet, interruption-free location (in-person or virtual).
• Request relevant artifacts in advance (logs, templates, example emails, runbooks, config files, diagrams).
• Prepare recording (with consent), note-taking template, and a basic template for synthesis (roles, steps, decision rules, artifacts, risks).
• Share a brief agenda with the SME so they know what to expect.

Permission & recording script (read at start)

“Thank you for making time. I'd like to record notes (and audio/video if you’re comfortable) so we can accurately capture the details you share. This interview will focus on practical decisions, common exceptions, and the artifacts you use. Anything you prefer not to record, tell me and we'll exclude it. We expect this will take about 45–60 minutes. Is that okay?”

Time allocation (suggested)

• Opening, permission, context: 5 minutes
• Role history & scope: 5–8 minutes
• Critical decisions & tradeoffs: 15–20 minutes
• Recurring exceptions & hidden heuristics: 10–12 minutes
• Artifacts, examples & handoffs: 5–8 minutes
• Closing, follow‑up, next steps: 2–5 minutes

Interview sections & sample questions

1. Context and role history

• How long have you been doing this role or task? How has the work changed over time?
• What parts of the work are within this role’s scope, and what is out of scope?
• What are the top 3 outcomes you’re responsible for?
• Probe: Which stakeholders or teams matter most to successful outcomes?

2. Critical decisions and tradeoffs

Goal: surface the decision rules and when they apply.

• What are the regular decisions you make that most affect outcomes?
• For each decision: what information do you check first? What thresholds or signals do you use?
• When you choose A instead of B, what tradeoffs are you accepting (time, cost, quality, risk)?
• Probe: Can you walk me through a recent example and your thinking step-by-step?

3. Recurring exceptions and edge cases

• What unexpected situations occur regularly? How do you detect them early?
• What workaround or contingency do you use when the normal process fails?
• Which exceptions are high‑impact and require escalation?
• Probe: Are there near misses or small failures that reveal a bigger hidden risk?

4. Hidden heuristics and unspoken rules

• Are there shortcuts, heuristics, or rules-of-thumb you rely on but rarely document?
• Which of these are learnable quickly, and which require context or judgment?
• Probe: Translate one heuristic into a clear if‑then rule or checklist item.

5. Common pitfalls and myths

• What mistakes do new people typically make? How can they be avoided?
• What misconceptions about the work have cost time or caused errors?

6. Top reproducible artifacts and evidence

• Which documents, templates, logs, dashboards, or commands do you use routinely?
• Ask the SME to open or point to example artifacts and explain the critical fields and how they’re used.
• Probe: Which artifact versions matter (e.g., config file vs. runbook) and how are they stored?

7. Handoffs, escalation, and onboarding tips

• When should someone escalate, and to whom? What information should they include?
• What are the fastest ways to get a new person up to speed on this work?
• Probe: If you had to onboard a replacement in two days, what would you prioritize teaching?

Facilitator probing prompts (use to follow up)

• “Tell me more about the last time that happened.”
• “What signals or metrics changed first?”
• “What would someone assume incorrectly if they didn’t know this?”
• “How confident are you in that approach? When does it break down?”

Closing and immediate actions

• Confirm any artifacts the SME will share and set deadlines.
• Ask: “Is there anything I should have asked but didn’t?”
• Agree on who will review the synthesized output and expected format (playbook page, checklist, short video, or annotated artifact).

Follow-up synthesis checklist (what the facilitator should deliver)

1. Create a 1‑page summary: role, top decisions (with if‑then rules), exceptions, and one prioritized onboarding checklist.
2. Attach or link example artifacts and mark the critical fields/lines with brief notes.
3. Extract 3–5 reproducible heuristics as clear rules or checklist items.
4. Identify one immediate improvement or missing artifact and owner to create it.
5. Store the interview notes and artifacts in the knowledge repository with tags for role, process, system, and risk level.

Recommended outputs & formats

• Short playbook page (1–2 pages) summarizing decisions, traps, and artifacts.
• Checklist or quick‑start card for onboarding
• Annotated example artifacts (with callouts)
• Optional 5–10 minute recorded walkthrough by the SME for complex tasks

Facilitator tips & pitfalls to avoid

• Don’t let the conversation drift into high-level strategy; steer back to concrete steps and examples.
• Be comfortable asking for precise numbers, thresholds, file names, or command lines — those details make artifacts usable.
• When an SME uses jargon, ask for the plain-language translation and an example of when it matters.
• Avoid over-editing the SME’s words during synthesis; preserve intent, then clarify as needed with follow-up questions.

Metadata & tagging recommendations

Tag the artifact with: role, system, process, date, interviewer, SME name, risk/criticality, and expected update cadence.

Template: Quick note fields for interviewer

• SME name & role:
• Date & interviewer:
• Top 3 decisions:
• Top 3 exceptions:
• Artifacts to collect:
• Follow-up actions & owners:

Optional next steps for scale

Run this interview with a small set of SMEs across related roles, consolidate overlapping heuristics into a team playbook, and convert high‑value heuristics into checklists or automated guardrails where possible.