Tacit Knowledge Capture Playbook

Purpose and when to use this playbook

This playbook helps teams capture the know‑how that lives in people’s heads — the heuristics, shortcuts, troubleshooting instincts, and contextual cues that rarely exist in manuals. Use it when someone is leaving or changing roles, onboarding new team members, preparing for project handoffs, or when hidden expertise is slowing work or causing repeated mistakes.

Principles

• Be brief and usable. Aim for short artifacts (2–5 minutes of content, a 1‑page transfer card, or a 5–7 bullet troubleshooting FAQ) that people will actually read and use.
• Respect people and time. Use open consent, honor privacy boundaries, and schedule capture so it fits normal work rather than feeling intrusive.
• Make it findable and living. Store artifacts with consistent tags, owners, and an update cadence so knowledge remains current.
• Convert tacit to explicit. Focus on decisions, cues, exceptions, common failures, and what to watch for — not just step lists.

Roles

• Knowledge Owner (Subject): the person who holds the tacit knowledge.
• Capture Lead (Interviewer/Observer): facilitates interviews, records artifacts, and drafts transfer cards.
• Reviewer/Verifier: a peer who validates the accuracy and clarity of captured content.
• Keeper (Repository Owner): stores artifacts, tags them, tracks review dates, and maintains the record.

1) 20‑minute interview script (ready to use)

Use this tightly timed script for a focused subject‑matter capture session. Keep the session to 20 minutes, record audio (if consented), and later convert the highlights into short artifacts.

1. 1–2 min — Warm up

   Quickly explain purpose: "We want a short, usable record so others can do this work reliably. I’ll ask a few questions and take notes; we’ll produce 1–3 short artifacts you can review." Confirm consent for recording and reuse.

2. 3–6 min — High‑value overview

   Ask: "What are the three things someone absolutely must get right in this role/task?" Follow with: "What commonly causes failures or delays?" Capture short examples.

3. 7–11 min — Step highlights & decision points

   Ask for the top 6–8 steps in the task, but focus on decision points: "At step X, how do you know to do Y instead of Z? What cues tell you that?" Note shortcuts and time savers.

4. 12–15 min — Troubleshooting and exceptions

   Ask: "When this goes wrong, what are the first three things you check? Which problems look similar but need different fixes?"

5. 16–18 min — Useful tools & templates

   Ask: "Which checklists, logs, or tools do you always use? Any undocumented heuristics or mental models?" Capture names and quick usage notes.

6. 19–20 min — Close and next steps

   Confirm any follow‑up (quick review of artifacts, verify transcript). Ask: "Is there anyone else we should speak to or any artifact I should review?" Thank the subject and confirm storage location and owner.

2) Rapid shadowing checklist

Use for a 30–60 minute observational session. Observe the subject performing the work and tick the most important observable cues.

• Pre‑shadow: Notify the team and confirm consent. Have a notetaker and recorder ready.
• Arrival check: What does the subject check first? (systems, inbox, physical conditions)
• Key actions: Note each major action and the approximate time spent.
• Decision cues: Record explicit cues (alarms, metrics) and implicit cues (feel, look, sound) that trigger a decision.
• Shortcuts: Observe any non‑standard but effective shortcuts and ask briefly about them.
• Interactions: Who did they call, message, or escalate? Capture contact roles and typical reasons.
• Wrap‑up: How do they document or hand off work at the end? Where are artifacts stored?

3) Transfer card template (one page)

A transfer card converts tacit steps into a single, actionable handoff. Use this template and store as a small record linked to the owner and artifact.

• Title: concise task name
• Owner: current subject and contact
• Why it matters: one‑sentence impact
• When to do it: frequency / trigger
• Critical steps (6 bullets max): brief, numbered
• Decision cues: what to watch for (metrics, noises, visuals)
• Top troubleshooting checks: 3 quick checks in order
• Quick links: related templates, logs, and people
• Last reviewed: date and reviewer

Example (short): "Daily Oven Start — Owner: A. Lee — Why: prevents 30‑hr warmup delay — When: start of shift — Steps: 1) Check oil pressure; 2) verify exhaust valve closed; 3) preheat 7 mins; ... Decision cue: if pressure < 10 psi, do X; Troubleshooting: if temp overshoot, check thermostat wiring."

4) Lightweight consent & retention guidance

Use a brief consent script before recording or publishing anything.

Consent script (verbal): "We’d like to record a short session so we can create a concise how‑to (a 2–3 minute clip, a one‑page transfer card, and a troubleshooting FAQ). You’ll review anything we publish, and you can ask us to redact sensitive items. Do you consent to this recording and to the organization storing and sharing the final artifacts internally?"

Retention policy (recommended minimum):

• Store artifacts for at least 2 years by default.
• Mark artifacts that are safety‑critical or compliance‑relevant for annual review.
• Include an owner and a next‑review date on every artifact.

5) Short‑form artifact types & production tips

Create one or more of these outputs after capture. Keep items short and scannable.

• 2–3 minute video clip

  Structure: 15–30s context, 60–90s demonstration of the key steps/decision, 15–30s troubleshooting tips. Use a phone, stable shot, clear captions, and speaker notes. Host reviews and approves final cut.

• Annotated steps (1 page)

  Numbered steps with inline decision cues and short warnings. Include images or screenshots where helpful.

• Troubleshooting FAQ (top 5 problems)

  Format: Problem → Quick check → Short fix → When to escalate.

• Audio highlight & transcript

  Clip the 2–3 most useful quotes from the interview; publish with a 3‑bullet summary.

6) Prioritization: who to capture first

Rank candidates by risk and reach. Prioritize people whose loss would cause the largest operational disruption or who possess knowledge used across many teams. A simple scoring matrix: Impact (1–5) × Frequency (1–5) — capture highest scorers first.

7) Storage, tagging, and maintainability

• Store artifacts in the team repository with clear filenames: [Task]_[Owner]_[YYYYMMDD].
• Tag each artifact with: task, owner, location, risk level, and review date.
• Assign a Keeper to run periodic reviews and to archive or refresh outdated items.

8) Quick start checklist

1. Choose one high‑impact task and one subject to pilot.
2. Schedule a 20‑minute interview and a 30‑minute shadow (or combine if needed).
3. Capture per the scripts and produce one 2–3 minute video and one transfer card.
4. Store, tag, and set a 6‑month review date. Ask the subject to verify the artifacts.
5. Collect feedback from two new users who try the artifact and iterate.

Common mistakes to avoid

• Making artifacts too long or overly formal; they become unused.
• Capturing without clear consent or without giving the subject review rights.
• Failing to assign an owner or review cadence; artifacts go stale.
• Trying to document everything at once — start small and iterate.

Next‑level capabilities (opportunities)

When your organization is ready, convert templates into interactive capture forms (so sessions and transfer cards are saved automatically), and connect stored artifacts to team dashboards or onboarding flows. See Capability Enhancement notes below for implementation ideas.

End of playbook — use this as a living starter. Adjust fields, tags, and retention to match your team’s risk, compliance, and culture.