Tacit Knowledge Capture Interview Kit

Purpose and When to Use This Kit

This kit helps you capture hard-to-write-down knowledge held in people’s heads—how things really get done, hidden heuristics, problem-detection cues, and unwritten shortcuts. Use it for handoffs, role transitions, retirements, post-incident reviews, onboarding, or whenever key context risks being lost.

How to run a short capture session

1. Identify the knowledge owner and the most valuable topics to capture (process steps, troubleshooting cues, common mistakes, tacit criteria for decisions).
2. Schedule 30–90 minute sessions (two 45-minute sessions often work well).
3. Share the session purpose in advance and ask the participant to bring artifacts (diagrams, logs, checklists, photos).
4. Record audio (and video or screen capture where helpful) and take structured notes using the synthesis template below.
5. Immediately synthesize key points and assign next steps to integrate outputs into repositories and operational artifacts.

Consent language (use or adapt verbatim)

Before recording, read or provide this consent statement to the participant and capture their verbal agreement on the recording:

"We’re recording this session so we can capture your knowledge and make it available to the team. The recording and notes will be stored in our knowledge repository. We will share a short, edited summary and any identified action items with you for review before publishing. If you have any concerns about what’s recorded, tell us and we will pause or exclude sensitive parts. Do you consent to proceed?"

Follow your organization's privacy, HR, and regulatory requirements. If sensitive or proprietary content is expected, consult legal or compliance before recording.

Recommended recording formats

• Audio (MP3/AAC): small, reliable, great for interview-focused captures.
• Video (MP4) with close-up of artifacts when physical gestures or visual cues matter.
• Screen capture (MP4 or WebM) for tool walkthroughs or demos.
• Photographs of equipment, whiteboards, forms, or work area (JPEG/PNG).
• Text notes and annotated images saved as plain text or PDF for quick indexing.
• Automated transcription (if available) to speed synthesis. Always review for accuracy and privacy.

Logistics & recording checklist

• Choose a quiet place; test audio quality and battery/space before starting.
• Confirm consent and record the consent statement on the recording.
• Note date, interviewer, participant, role, and topics at the beginning of the recording.
• Ask the participant to narrate artifacts as they show them (photos, schematics, prints).
• Time-box sections and pause to confirm unclear points.
• Close session by repeating key takeaways and next steps; confirm permission to publish the summary.
• Securely store raw recordings and transcriptions per your retention policy.

Role-specific interview scripts (adapt as needed)

Engineer / Specialist — 45 min script

1. Opening (2 min): Purpose, consent, what we'll capture and where it will be stored.
2. Context (5 min): "Describe your role, typical responsibilities, and the systems you rely on."
3. Critical tasks (10 min): "Walk me through the tasks you do most often. What’s important but not written down?"
4. Troubleshooting (10 min): "Show a recent problem and how you diagnosed it. What signals tipped you off? What shortcuts or checks do you use?"
5. Workarounds and judgment calls (10 min): "When do you depart from the documented process and why? What heuristics guide your judgment?"
6. Artifacts and examples (5 min): Ask to see diagrams, code snippets, checklists; photograph or capture screen.
7. Close (3 min): Key takeaways, unanswered items, permission to follow up.">

Operator / Technician — 30–45 min script

1. Opening and consent (2 min).
2. Daily routine (8 min): "What are the first things you check in the morning? Which checks catch problems fastest?"
3. Common issues (10 min): "What issues do you see daily/weekly? How do you spot and fix them?"
4. Hands-on cues (10 min): "Are there sounds, odors, or vibrations that indicate trouble? Can you demonstrate?"
5. Handoffs and communication (5 min): "How do you communicate shift changes and important anomalies?"
6. Close (3 min): Confirm what to capture and follow-up steps.

Manager / Supervisor — 30–60 min script

1. Opening and consent (2 min).
2. Role priorities (8 min): "What outcomes are you accountable for? Which decisions are hardest?"
3. Decision criteria (10 min): "How do you decide where to focus resources? What signals or metrics matter most?"
4. Handoffs and escalations (10 min): "Describe critical handoffs and how you expect teams to escalate issues."
5. Risk and exceptions (10 min): "When do you make exceptions and how are they documented?"
6. Close (5 min): Identify essential artifacts to capture and successors to consult."

Quick synthesis template (fill immediately after the session)

Use this template to convert raw capture into usable knowledge.

• Title: [Short descriptive title]
• Date / Interviewer / Participant / Role:
• Context: One-sentence summary of where this knowledge applies.
• Key outcomes / What they know that matters:
  • Item 1 — short, actionable statement
  • Item 2 — include why it matters
• Step-by-step or cues: Clear steps or observable cues (sounds, lights, readings) to watch for.
• Common failure modes & fixes: For each: symptom, likely cause, first check, fix, and how to verify.
• Workarounds & judgement calls: When to use them and risks.
• Artifacts captured: Photos, diagrams, file names, timestamps, transcript link.
• Actions & owners: Publish summary, add to SOP, train successor, assign review date.
• Confidence & follow-up: Any areas the interviewer should verify or explore later.

Integration checklist — put the captured material to work

1. Transcribe or summarize recording and attach to the raw file.
2. Create a short (3–6 bullet) executive summary for quick consumption.
3. Tag the summary and raw file with metadata: role, system, location, process, risk level, relevant keywords, and date.
4. Link to operational artifacts: SOPs, work instructions, training modules, incident reports, drawings.
5. Decide publication scope and permissions (who can view, edit, or annotate).
6. Add key items to living documents (SOPs, checklists, onboarding guides) with an explicit change note and author.
7. Schedule a short peer review (owner + 1 subject-matter reviewer) to validate critical items.
8. Assign follow-up actions (training, SOP updates, tooling changes) with owners and due dates.
9. Set a review date (e.g., 6–12 months) to confirm continued validity.

File naming, storage, and metadata conventions (suggested)

• Filename: [YYYYMMDD]_[Site]_[Role]_[ShortTitle] (e.g., 20260901_PlantA_Operator_BeltJam.mp3)
• Repository: central knowledge repo / team folder with controlled access and searchable metadata.
• Essential metadata: date, interviewer, participant, role, system/process, location, risk level, tags, transcript link.

Common pitfalls & advice

• Don’t let the perfect summary block quick publication—publish a short summary first, refine later.
• Avoid jargon without context—capture the phrase and a one-line explanation of what it means in practice.
• Respect confidentiality—redact or exclude sensitive customer or personal data and note redaction in metadata.
• Prioritize high-risk, high-usage knowledge first (critical equipment settings, emergency responses, or decision heuristics).

Starter checklist (printable)

• Schedule 45–60 min session
• Send pre-work: topics and artifacts to bring
• Confirm consent language and recording method
• Test equipment and start recording with metadata note
• Follow role script and capture artifacts
• Complete quick synthesis template within 24 hours
• Publish summary, attach raw files, tag, and assign follow-ups

Next-level ideas (optional)

When the organization is ready, consider an interactive capture form to standardize metadata, automatically store transcriptions, and create trackable action items. Periodic knowledge cultivation sprints and 'knowledge handoff' events can accelerate onboarding and reduce single-person dependencies.

References & responsible use

Follow your organization's data retention, privacy, and HR policies when recording and publishing material. This kit is a practical operational tool—not a substitute for legal or HR guidance where required.