Tacit Knowledge Interview Script & Recording Protocol

Purpose and When to Use This Script

This script helps capture tacit, hard-to-document expertise—tradecraft, heuristics, critical incidents, and decision-making cues—so teams can preserve institutional memory, speed onboarding, and reduce repeated mistakes. Use it when a role is changing, a skilled person is leaving or moving, after a notable project, or whenever undocumented expertise affects outcomes.

Interview at a glance

• Recommended interview length: 30–60 minutes (short, focused interviews are easier to schedule and process).
• Primary outputs: recording (audio or video), a one-paragraph summary, and three transferable insights or checklist-style actions.
• Tone: conversational, curious, respectful. Treat the subject as an expert story-teller, not an interrogator.

Preparation Checklist (Interviewer)

• Identify the specific hunger: what decision, task, or situation should this knowledge help with?
• Schedule a quiet, distraction-free time. Share the agenda and estimated length in advance.
• Send a short pre-interview prompt to the interviewee (example below) so they can recall stories.
• Prepare recording equipment and backup. Test audio/video and ensure permission for recording is clear.
• Use the naming convention: [Org]_[Role]_[ShortTopic]_[YYYYMMDD] (e.g., Acme_TechLead_DeployTips_20260906).

Pre-interview prompt (short email or message)

"Thanks for agreeing to share your experience. We'll spend about 45 minutes. Think about a memorable recent example where your judgment mattered—what happened, how you decided, and what you wish others knew. No need to prepare; bring a story. I'll record for accuracy and then share a short summary."

Consent & Use Phrasing (Say this aloud before recording)

"Before we begin, I want to confirm your permission to record this conversation for internal learning. We'll use the recording to make a short written summary plus three key takeaways that others can use. We won't share the raw audio/video outside [team/company] without your additional permission. Do you consent to this recording and the uses I described? You can ask to pause or stop at any time."

Warm-up Questions (5–8 minutes)

• How long have you been doing this type of work and how did you get started?
• What part of this work do you most enjoy and why?
• What's one phrase or rule you use to describe how you usually approach this role?

Story Prompts (use to surface critical incidents & tacit heuristics)

Invite concrete examples. Encourage sequence, decisions, trade-offs, and turning points.

1. Critical Incident: "Tell me about a time when things went wrong or unexpectedly well. What happened, what did you notice first, and what did you do next?"
2. Decision Point: "Describe a decision you made under pressure recently. What options did you consider and why did you choose that path?"
3. Heuristics & Shortcuts: "What quick rules-of-thumb do you rely on when you can't run a full analysis? When do those rules break down?"
4. Hidden Tools & Artefacts: "Are there templates, scripts, dashboards, or little checks you keep in your head or on a sticky note that others don't know about?"
5. Handoffs & Onboarding: "What do you wish new people knew or asked about in their first two weeks on the job?"

Follow-up Prompts to Surface Transferable Detail

• Can you walk me through the steps you took, minute-by-minute if possible?
• What signals or small clues tipped you toward that decision?
• What would you do differently next time? What would you instruct a new hire to do first?
• Are there thresholds (numbers, conditions) you watch for that trigger action?
• Who else should we talk to to get the rest of this story?

Interviewer Conduct Tips

• Listen more than you speak; allow silence—experts often pause to select the right detail.
• Ask for examples, not abstractions. Push for specific sequences, not general opinions.
• Reflect back briefly: "So the key trigger was X, and you prioritized Y because…"
• Respect boundaries; don’t push personal or proprietary details beyond consent.

Audio/Video Technical Checklist

• Preferred formats: Audio MP3 or WAV; Video MP4. Use local recording where possible (not only cloud) as a backup.
• Microphone: external mic recommended. Test volume so that normal speech is near -12dB to -6dB peak.
• Environment: quiet room, avoid HVAC noise, close windows. Use headphones to prevent echo.
• Record file naming: follow the naming convention from Preparation Checklist.
• Create immediate backup: copy to two locations (team drive + secure archive) within 24 hours.

Timestamping Protocol (simple, consistent, and actionable)

Goal: make highlights findable without full transcription.

1. While listening live or during a quick pass, mark important moments using this short form: HH:MM:SS — Tag — One-line note
   Example: 00:12:34 — DecisionPoint — Chose rollback because test server showed 40% failure
2. Use a small controlled set of tags: DecisionPoint, HowTo, Pitfall, Tool, Threshold, Contact
3. Create an index file (text or spreadsheet) saved alongside the recording with timestamp, tag, short note, and suggested action (if any).
4. If you transcribe, include the timestamp at paragraph breaks, e.g., [00:12:34].

Minimum Post-interview Artifact Template (deliver within 48–72 hours)

This is the single most valuable deliverable: a short, actionable summary others can use without listening to the whole recording.

Quick extraction workflow (recommended)

1. Immediate: save recording with correct name and backup.
2. Within 24 hours: interviewer or scribe listens and creates the timestamp index.
3. Within 48–72 hours: produce the one-paragraph summary + three transferable insights and attach timestamps.
4. Optional: run transcription (automated) and use it to generate longer write-ups or knowledge-base entries.

Privacy, Sharing, and Attribution

Always honor the consent agreed at the start. If content will be quoted externally or used in training materials, obtain additional written permission. Attribute ideas to the role rather than the individual when requested.

Adaptations & Shortcuts

If time is limited, record a 10–15 minute focused 'micro-interview' on one decision or incident and deliver one insight plus one timestamped clip.

Example Filled Mini Summary (model)

One-sentence summary: When the deployment pipeline fails, the Tech Lead prefers a fast rollback if >30% of smoke tests fail to preserve customer-facing stability.

Key context: Tech Lead, web platform, production deploys during business hours, incident from 2026-09-01.

1. Insight 1: If smoke failures exceed 30% within first 10 minutes, rollback immediately and notify stakeholders—don’t chase partial fixes.
2. Insight 2: Keep a pre-approved rollback runbook and test it monthly.
3. Insight 3: Pitfall: trying to patch in production without meeting the rollback criteria—this increases downtime.

Top timestamps: 00:05:12 — DecisionPoint — Observed 35% failures; 00:06:30 — HowTo — Steps performed to rollback.

Closing note

This script aims to make tacit knowledge findable and usable. Preserve the human voice—summaries should capture why a choice made sense, not just the mechanical steps. Treat this as a living protocol: adapt tags, file names, and templates to your organization’s needs.