Expertise Capture Interview Guide (turn tacit knowledge into repeatable SOPs)

Why capture expertise now?

Top performers carry tacit knowledge — pattern-recognition, small judgment calls, shortcuts and contingencies — that rarely exists in written form. When that knowledge leaves with a person, performance suffers, training becomes costly, and small fixes that used to happen organically turn into recurring problems. This guide helps you capture that knowledge through focused interviews, convert it into usable SOPs and training assets, and validate changes so the organization can keep improving.

When to use this guide

• Before retirement, role-change, or departure of a skilled employee.
• When you notice persistent variation between shifts or people.
• To turn an informal 'best practice' into a standard work document or training module.
• As part of onboarding or continuous improvement cycles to broaden organizational knowledge.

Quick overview of the process

1. Prepare: select interviewees, define scope, gather materials.
2. Interview: run a structured interview focused on workflows, decisions, contingencies and reasons.
3. Record & organize: capture audio, photos, notes and immediate observations.
4. Translate: convert notes into stepwise SOP draft using the provided translation template.
5. Validate: workshop the draft with peers, test on the floor, revise and approve.
6. Publish & train: add to SOP library, build a short training exercise, and schedule follow-up checks.

Before the interview: preparation checklist

• Define the process scope: choose a single workflow or task that's small enough to document in one session (e.g., 'End-of-day prep for line 2', 'Calibrating mixer').
• Pick the right interviewee(s): someone who reliably performs the task, explains it clearly, and can show the work on the job.
• Notify and schedule: give the interviewee time to prepare and arrange a quiet time with minimal interruptions.
• Assemble tools: audio recorder (backup phone), camera or phone for photos, laptop or tablet for notes, printed templates.
• Check consent: explain purpose and how the material will be used; get verbal or written consent for recording if required.
• Draft goals: write 2–3 clear objectives for the interview (what you will be able to do with the SOP afterward).

Interview structure and script

Run the interview as a guided conversation that alternates demonstration and probing questions. Prioritize observing work when possible — the most useful details show up in action.

Suggested structure

1. Opening (5 minutes): set context, confirm consent, state goals, and ask the person to show the workflow once while narrating.
2. Step walkthrough (30–45 minutes): watch each step, take photos and notes, then ask clarifying probes after each step.
3. Contingencies & decision points (10–20 minutes): discuss what to do when things go wrong or conditions change.
4. Resources & metrics (5–10 minutes): capture tools, materials, timing expectations, and how success is measured.
5. Wrap-up (5 minutes): ask for tips, common mistakes, and whether the person wants to review the draft SOP later.

Core question sets (use these as prompts)

• Why: Why do you do this step this way? What is the desired outcome?
• When: When do you perform this task? How long should each step take?
• How exactly: Describe each action as if teaching someone who’s never seen it.
• Contingencies: What do you do if X happens? (e.g., machine stalls, ingredient shortage, spill)
• Decision points / tolerances: When do you decide to stop, escalate, or rework?
• Checks & signals: What signs tell you the step succeeded or failed?
• Shortcuts & tips: Small adjustments that save time or reduce risk — include them but flag as optional.
• Who else: Who must be informed or who helps during the task?

Recording checklist (practical details)

• Primary audio recorder and backup (phone + external mic optional).
• Photos of workspace, controls, labels, and any critical measurements.
• Short video clips of hands-on steps where gestures matter (10–30s clips).
• Printed translation template and a printed SOP example to show the interviewee.
• Time-stamped notes: note rough timestamps when critical points occur so you can find them in recordings later.
• Store raw files in a named folder (date_person_task) and record filenames in notes.

Translation template: turning interview notes into a stepwise SOP

Use this structured template to make an editable SOP draft. For each numbered step, capture the action, expected result, time, tools, and decision rules.

Example (short)

Step: "Weigh portion" — Action: "Zero scale, place container, tare, add filling until scale reads 150g ±5g." Expected outcome: "Each portion is 150g ±5g. If portion >155g, remove and reweigh; if <145g, prepare a new portion." Tools: "Scale #3 (calibrated), scoops."

Validation & change control

• Circulate the draft SOP to 2–3 peers and a supervisor for comments within a week.
• Run a 3-shift pilot where staff use the SOP and record deviations and timings.
• Collect quick feedback: what was unclear, what slowed work, what improved quality?
• Revise the SOP and record the version, approver, and effective date.
• Schedule a follow-up review in 30–90 days to confirm the SOP still works in practice.

Turning the SOP into training

1. Create a short 5–10 minute demo video or a photo sequence of the critical steps.
2. Build a 10-minute hands-on exercise with acceptance criteria from the SOP.
3. Use a short checklist for the trainer to observe the trainee during the exercise.
4. Link the SOP to the job description and performance metrics where relevant.

Storage, ownership and living knowledge

Store the final SOP in your central SOP library with a clear owner, version history, attachments (photos, audio snippets, video), and references to related procedures. Make it discoverable by role and by task. Keep interview recordings for a limited retention period per policy, but keep photo references and the final accepted draft indefinitely as part of organizational memory.

Next steps & suggested experiment

Run this sequence on one high-value task this week. Timebox the whole capture, translation and pilot cycle to 2–3 weeks so you learn quickly and improve the process before scaling.

Template downloads: Use the step template above to create a document or copy-and-paste sections into your SOP system. Consider adding audio clips, annotated photos, and a 3-shift pilot checklist to the SOP entry.