Most standard operating procedures fail for the same reason: they were written by someone who learned the process from reading documentation, not by the person who actually does the work. The result is a document that describes what should happen, not what actually happens — and new team members learn that gap the hard way.

SOP generation from expert interviews is a different approach. Instead of asking an expert to sit down and write a document they do not have time for, you interview them about their work and convert that conversation directly into a structured procedure. This guide walks through the full process, step by step.

Why Interviews Produce Better SOPs Than Written Documentation

When an experienced person does their job, they are operating on pattern recognition built from years of practice. They notice things a newcomer would miss. They make constant micro-decisions — when to escalate, when to wait, which client needs a call instead of an email — and most of these decisions happen below the threshold of conscious thought. They are expertise made automatic.

Written documentation captures the skeleton of a process. Interviews capture the muscle memory.

The gap between what an expert can write down and what they actually know is not laziness — it is the nature of tacit knowledge. They cannot document what they have forgotten they know.

A structured interview, with follow-up questions that probe for specifics, surfaces the tacit knowledge. The interviewer or AI asks: “You said you call the client at that step — what are you listening for in that call?” That question produces an answer the expert would never have thought to include in a written SOP. That answer is often the most valuable thing in the document.

What You Need Before You Start

Before scheduling the interview, clarify two things:

You also need a recording and transcription tool, or access to an AI interview platform like BrainVault's interview mode that handles both automatically. Trying to take notes in real time while running an interview splits your attention and you will miss the details that matter.

The Step-by-Step SOP Generation Process

Step 1

Open with the process overview

Start broad: “Walk me through how you handle [process] from start to finish.” Let the expert talk without interruption. This gives you the skeleton — the major phases and their sequence — and tells you where to probe next.

Step 2

Probe each step for triggers and outputs

For each step the expert describes, ask: “What tells you it is time to do this?” and “What should exist or be true when this step is done?” These are the inputs and outputs — the connective tissue between steps that most SOPs omit entirely.

Step 3

Surface the edge cases

This is the most valuable part of the interview. Ask: “What goes wrong at this step?” and “What does someone new usually get wrong here?” The answers reveal the failure modes that a written SOP would never capture because the expert finds them too obvious to mention.

Step 4

Ask about judgment calls

Identify every place where the expert makes a decision rather than following a fixed rule. “How do you decide whether to escalate?” “What would make you skip this step?” These decision rules are the difference between an SOP that handles 80% of situations and one that handles 95%.

Step 5

Confirm tools, systems, and contacts

Work through each step and ask: “What system are you in when you do this?” and “Who else is involved?” A new team member cannot follow an SOP that says “check the status” without knowing which system to open. Specificity is kindness.

Step 6

Close with the success criteria

End every interview with: “How do you know when this process has gone well?” and “What would make you redo a step?” This produces the quality checkpoints that turn a procedure into a feedback loop.

Structuring the SOP from the Transcript

Once you have the transcript, the conversion to a structured document follows a consistent format. A good standard operating procedure template includes:

The key structural principle: every step should be specific enough that someone doing it for the first time could complete it without asking a question. If a step requires a follow-up question to execute, it is not specific enough.

Using AI to Accelerate the Process

The manual version of this process — conducting the interview, transcribing it, extracting the structure, writing the SOP — takes somewhere between four and eight hours per document. For complex processes with multiple edge cases, it can take longer.

AI-assisted SOP generation from interviews compresses this significantly. The AI handles the probing questions during the interview, extracts the structure from the transcript automatically, and formats the output into a complete SOP document. The total time investment from the expert is typically 45 minutes. The editing time for whoever reviews the output is usually under an hour.

For organizations that need to capture knowledge from multiple people across multiple processes — standard for professional services firms, accounting practices, and consulting firms undergoing growth or succession planning — the time savings compound quickly.

Common Mistakes and How to Avoid Them

Interviewing the wrong person. Title and expertise do not always align. Interview the person who does the work most often, not the person who has the highest rank. The senior partner who “used to run” a process five years ago does not have current knowledge.

Stopping at the overview. The overview is the easy part. The value is in the follow-up questions. Budget at least half your interview time for probing the steps the expert considers obvious.

Skipping edge cases. Every process has failure modes that experienced people handle automatically. These are exactly the scenarios that strand a new team member. Ask specifically: “What goes wrong here? What does it look like when this step fails?”

Producing a document no one reads. An SOP that lives in a shared drive and never gets looked at is not a solved problem — it is a documented one. After creating the document, walk someone new through it and observe where they get stuck. Those points are your first revision targets.

When to Use This Approach

SOP generation from expert interviews works best for:

It is less suited for purely mechanical processes with no judgment calls, or for processes that are already well-documented and followed consistently. For those, a documentation review and formatting update is usually sufficient.

Generate Your First SOP in Under an Hour

BrainVault's AI interview mode captures expert knowledge and converts it to a complete, structured SOP automatically.

Start Free — No Credit Card Required

Not sure where to start? Take our 3-minute Knowledge Risk Assessment to identify which knowledge holders and processes are most at risk in your organization. You'll get a scored breakdown with prioritized recommendations.