From 45-Minute Interview to Complete SOP in Under an Hour

Every organization has the same problem: the most experienced people have the most knowledge, and they are always the ones with the least time to document it. The senior engineer who knows exactly why the deploy keeps failing at 2am. The head nurse who can triage any emergency in her sleep. The sales director who knows every client's pressure point from fifteen years of relationship-building.

These people know things that would take a newcomer years to figure out on their own. And they will never sit down and write it down.

Why the Documentation Gap Is Structural

The standard approach to capturing expert knowledge is to ask the expert to write it down. This fails almost universally, and not because of resistance or laziness. It fails because writing documentation is a fundamentally different cognitive task than doing the work.

When an expert does their job — whether it is closing a complex sale, debugging a production issue, or running a kitchen during a dinner rush — they are operating on years of accumulated pattern recognition. They see signals that a newcomer would miss entirely. They make micro-decisions constantly, weighing factors that never make it into any written record.

Asking an expert to document their knowledge is like asking them to describe the path they took to get to work. They can tell you the general route. They cannot tell you about the fifty course corrections they made along the way that day — and those fifty course corrections are often the most valuable knowledge.

Structured interview capture solves this differently. Instead of asking the expert to remember what they know, we create a conversation that surfaces what they know, including the things they would never think to write down.

How the Interview Process Works

BrainVault's interview mode starts with a broad prompt: "Tell me about how you handle [specific situation]." The expert talks. The AI listens. Then the AI asks follow-up questions based on what was said — drilling into specifics, asking for examples, probing the edge cases.

The follow-up questions are the key. A standard documentation template might ask: "What are the key steps in this process?" An AI follow-up might ask: "You mentioned that step three often surprises new people. What specifically goes wrong there, and how do you recover?"

This is the question the expert would never write down because it seems obvious to them. But for someone learning the process, that edge case knowledge is exactly what determines whether they succeed or fail.

From Transcript to SOP

The interview produces a transcript. The transcript is then processed into a structured document: a Standard Operating Procedure that reflects how this specific person actually does the work.

The document is not a generic template filled in — it is a reflection of the expert's actual approach, including their specific judgment calls, their preferred techniques, and the way they handle the cases that don't fit the standard path.

The result is an SOP that reads like the expert wrote it, because in a meaningful sense, they did — they just did it by talking, not by writing.

What Makes the SOP Actually Useful

Most SOPs fail because they describe the ideal path, not the real path. They document how the process should work, not how it actually works when something goes wrong.

An SOP generated from an interview captures both. The expert talks about how they handle the normal case, and the AI's follow-up questions surface the edge cases: the client who pushes back at step three, the system that times out when it should not, the vendor who lies about their delivery window.

This matters because when someone reads an SOP to learn a process, they will inevitably hit situations the SOP did not anticipate. If the SOP only covers the happy path, they are stranded. If the SOP includes the expert's mental model — their decision framework for handling the unexpected — they have something to work with.

The Speed of It

One of the surprising things about this process is how fast it goes. A 45-minute interview, processed and formatted, typically produces a complete SOP in under an hour of total time investment from the expert.

Compare that to the traditional approach: ask the expert to write it up, they procrastinate for two weeks, they produce something generic that captures the structure but none of the nuance, you send it back for revisions, they push back because they did not have time to do it properly, six weeks have passed and the document is mediocre.

The interview approach works because it meets the expert where they are. They are already doing the work. We just ask them to talk about it — which they will do for 45 minutes, because it feels like less effort than writing documentation.