Capture Expert Knowledge Before Making a Training Video

A standard operating procedure, or SOP, is a map. It lists steps in order. But maps do not show potholes. Expert staff carry a second map in their heads. It includes triggers, exceptions, and quiet warning signs.

If you record the SOP alone, you get a lecture. If you interview the expert first, you get a story. Stories prepare new staff for moments the SOP does not cover.

This guide shows you how to capture that knowledge before you write a script or press record. You will learn a repeatable interview method, a way to trace every claim to its source, and a checklist your team can adapt.

Why a Script Comes Second

This method is distinct from turning an existing SOP into a video. Here, the source does not yet exist. You create it through conversation.

An SOP describes what should happen. An expert can tell you what actually happens, and why. That difference matters. New staff need both. The interview is how you collect the second half.

The Core Idea: Interview for Tacit Knowledge

Tacit knowledge is what people know but rarely write down. It lives in habits and instincts. You cannot copy it from a manual. You must draw it out with good questions.

A willing subject expert is essential. Choose someone who does the task well and can explain why. Pay them for the time. Make the session feel like a conversation, not an audit.

Use fictional examples from the start. Do not record actual customer details. This protects privacy and keeps the expert relaxed.

A Proposed Workflow

Here is a practical method you can adapt. It has five stages.

Stage 1: Prepare the Interview

Book 45 to 60 minutes as a planning example. Adjust based on the task and the expert's availability. Use a quiet room. Record audio only if the expert agrees. Tell them the purpose: to capture judgment, not to grade performance.

Write five to seven open questions. Avoid yes or no prompts. Ask about the last time something went wrong. Ask what a new person always misunderstands.

Bring a simple template. It should have columns for triggers, decisions, and failure signs. You will fill it in together.

Stage 2: Walk Through a Real Task

Ask the expert to describe a common task from start to finish. Use a fictional customer example. For instance, two requests for the same service visit.

Listen for moments where the expert pauses. A pause is a cue to ask a question. It may mark a decision point, or it may simply be the expert gathering their thoughts. Ask: "What made you choose that option?" or "What would make you stop here?"

Write down the exact words the expert uses. Their phrasing often becomes your script language.

Stage 3: Probe for Exceptions

Every process has edge cases. These are unusual situations that break the normal flow. Ask the expert to list three.

For each exception, capture four things:

• The trigger: what tells you this is different?
• The decision: what do you do?
• The reason: why this choice?
• The escalation point: when do you hand it off?

This stage often reveals the most valuable content.

Stage 4: Trace Source to Script

Now you have raw interview notes. You need to turn them into a script. But you must be able to show where each claim came from.

Create a trace table. It links each script line to a specific interview moment. A trace table shows the source of a claim. It does not prove the claim is true. You still need to validate each claim before publishing.

Validation means checking interview claims against current policy, manuals, or an authorized process owner. If the expert describes an undocumented workaround, flag it. Do not publish it as standard practice until the process owner confirms it.

Here is a fictional worked example.

Worked Example: A Fictional Service-Booking Team

Team A arranges home-cleaning visits. All people, records and policy details in this example are invented to show the method.

Task: Handle two requests that appear to describe the same visit.

Expert: Priya explains how she checks a request before creating another booking. She does not assume that matching names prove the requests are duplicates. A client may need two visits.

The interviewer asks what would make Priya stop. She says the first warning is a mismatch in the requested date or service. Her team lead then checks that advice against the team's fictional booking procedure. An undocumented shortcut stays out of the training script until the owner resolves it.

Draft script point	Interview source	Validation step in this fictional case	Sign-off
Compare the request date, address and requested service	Note A	Process owner checks the current booking procedure	Owner approves
Do not delete one request just because names match	Note B	Owner confirms that repeat visits are allowed	Owner approves
If details conflict, pause and ask the booking lead	Note C	Lead confirms the escalation route	Lead approves
Tell the client when to expect a reply	Note D	Response time has not yet been agreed	Hold this line; owner must decide

The last row is the useful one. A source note does not make the claim true or ready to teach. The team holds the line until there is a current, approved answer. The final script records the source, the validation and the reviewer for every decision it teaches.

Stage 5: Expert Sign-Off and Access Boundaries

Before recording, ask the expert to review the script. They should confirm it matches their intent. This is not a legal step. It is a respect step. It also catches errors early.

Set clear access boundaries. Decide who can view the final video. Internal staff only is a common choice. If you use a vendor, ask where files are stored and who can see them.

Do not include real customer names, account numbers, or addresses. Use invented examples. This reduces risk and keeps the focus on the method.

A Reusable Checklist

Use this checklist before you record any expert-knowledge video.

Item	Done?
Expert agreed in writing to be recorded	☐
Expert agreed in writing to avatar or voice reuse, if applicable	☐
Expert agreed in writing to data processing, if applicable	☐
Fictional example prepared	☐
Interview template ready	☐
Audio recorder tested	☐
Triggers captured	☐
Exceptions captured	☐
Failure signs captured	☐
Escalation points captured	☐
Source-to-script trace table filled	☐
Claims validated against current policy or process owner	☐
Expert reviewed and signed off the script	☐
Access boundaries defined	☐
No real customer data in script	☐

Decisions and Edge Cases

Decision: How long should the video be?

Aim for three to five minutes. One video should cover one task or one exception cluster. You can make a series.

Decision: Who should conduct the interview?

Choose someone who listens well and does not interrupt. A manager can work, but a peer often gets more honest answers. Avoid anyone who grades the expert's performance.

Edge case: The expert struggles to explain their steps.

Ask them to narrate while doing the task. Use a fictional scenario. Record the narration. Then ask "why" after each step. This often unlocks tacit knowledge.

Edge case: Two experts disagree.

Do not present conflicting options to novices. Record both views, then resolve the disagreement with the policy or process owner before publishing. The published script should reflect the agreed position. If no owner exists, escalate to a manager.

Edge case: The task involves sensitive data.

Use a sandbox or test environment with sanitized demo data from the start. Create dummy records before you begin. Never record a live screen with real customer details. Do not rely on later blurring to protect a live sensitive recording.

Consent Is Not One Question

Consent to an interview is not consent to everything else. Treat these as separate decisions:

• Consent to be interviewed and recorded.
• Consent to have an avatar or voice clone created from the recording.
• Consent to have personal data processed and stored.

Do not infer permission for a clone from permission to record. Ask separately, in writing, before you proceed.

How Long Should You Keep the Raw Interview?

Personal data in your interview recording should not be held longer than needed for the purpose. The UK ICO storage limitation guidance says retention must be justified and reviewed. Legal duties can justify keeping some records. Do not promise immediate deletion of all backups or consent evidence. UK-specific guidance is under review.

Set a review date and a change trigger. For example, delete raw audio 90 days after the final video is approved, and review the plan sooner if permissions or the purpose change. Keep the trace table and signed script for as long as the video is in use. This is an illustrative choice, not a legal rule.

A Note on AI Tools and Risk

You may use AI tools to transcribe or draft scripts. The NIST AI Risk Management Framework is voluntary guidance to help manage AI risks to people and organizations. Its functions are Govern, Map, Measure and Manage. It is not certification, a legal obligation, or proof a vendor is secure. Your checklist is editorial advice, not an official NIST test.

Before using any AI tool, ask simple questions. Where does the data go? Who can access it? Can you delete it? The answers matter more than marketing claims.

This article is general information, not legal or security advice. Check with a qualified professional for your specific situation.

Three Short FAQs

Q: How many interviews do I need for one video?

A: Start with one interview for a focused task. Add another session if questions or conflicts remain. Have the process owner verify the final guidance before recording.

Q: What if the expert leaves before sign-off?

A: Ask a second experienced staff member to review the script. Note that the original expert did not sign off. If the script contains uncertain claims, mark them as "to verify" or cut them.

Q: Can I use the same interview for multiple videos?

A: Yes. Group the notes by theme. Each video gets its own trace table and its own validation pass.

Useful Next Steps

If you already have written SOPs, see how to turn SOPs into training videos. If you are choosing tools, read AI video for corporate trainers. For broader team communication ideas, see AI video for internal communications.

Your next action: Book one 45-minute interview with a willing expert this week. Use the checklist above. Capture one trigger, one exception, and one failure sign. Validate each against current policy before you write the script.