How to Get Knowledge Out of Your Team's Head (Without Slowing Them Down)

The Real Reason Your Processes Aren’t Written Down

Once you’ve decided which process to document first, you run into the actual obstacle: the person who knows how to do the work is not the person who has time to write it down.

Your best employee — the one who onboards clients without a hitch, who troubleshoots equipment failures in 20 minutes flat, who trains every new hire without being asked — that person is swamped. They’re not going to stop doing the work to document the work. And if you hand them a blank Google Doc and ask them to “write up how you do it,” you’ll get one of three outcomes: a vague paragraph, a perfect document three weeks late, or nothing at all.

This isn’t a motivation problem. It’s a format problem. You’re asking someone to do two cognitively different things — perform an expert skill and articulate it as transferable steps — simultaneously. Most people can’t do both at once.

The fix is to separate the extraction from the documentation. Your subject matter expert does the first part; someone else handles the second.

Here are four methods that actually work, with honest tradeoffs on each.

---

Method 1: Watch and Record

How it works: You (or a designated documenter) watch the expert do the task in real time while recording the screen or the physical workspace with Loom, Zoom, or even a phone. The expert narrates as they go.

Best for: Repetitive software workflows, step-by-step physical tasks with a clear sequence, anything where “watch me do it once” captures 90% of the knowledge.

Honest tradeoffs:

• Works extremely well for screen-based work (CRM data entry, invoicing steps, support ticket handling).
• Breaks down for complex judgment calls — the expert will narrate the obvious steps but skip the “I check this because once we had a customer who…” context that makes the SOP actually useful.
• The recording is not the SOP. Someone still has to watch it and turn it into steps. That’s an hour of post-processing for every 20-minute recording.
• Experts often compress their narration when they know they’re being recorded. You get speed, not clarity.

When to use it: When the task is mostly mechanical, when you have someone to do the post-processing, or when the expert genuinely can’t stop to be interviewed.

---

Method 2: Interview-Style Transcript

How it works: You sit with the expert (or call them) and ask structured questions while they talk. You transcribe or take notes in real time, then turn the transcript into a draft. The expert reviews the draft, not the blank doc.

Best for: The widest range of processes, especially ones that involve judgment. This is the default fastest path for most SMBs.

Honest tradeoffs:

• Takes 30–45 minutes of the expert’s time upfront — but they’re just talking, not writing. Most people will agree to “can I ask you questions while you walk me through this?” much more readily than “can you write this up?”
• The draft review step usually takes 10 minutes. The expert corrects what’s wrong rather than starting from scratch.
• Requires someone competent to run the interview and take notes. If the interviewer doesn’t know the business, they won’t know which questions to ask.
• Captures context and edge cases that watching misses, because you can ask “what do you do when X happens?”

When to use it: Almost always. I’ll walk through the full 30-minute interview script below.

---

Method 3: “Teach a Junior” Recording

How it works: The expert trains a newer employee on the task while someone records the session. The new employee’s questions naturally surface the “why” behind each step.

Best for: Processes that already happen informally — where the expert is already training people verbally, just without anything written down.

Honest tradeoffs:

• Gets you two things at once: knowledge capture and actual training.
• The new employee’s confusion is a feature. When they ask “wait, why do we do it that way?” and the expert answers, that exchange is the most valuable content in the SOP.
• Harder to schedule than a one-on-one interview. Requires the right pairing.
• Still requires post-processing to turn the recording into a usable document.
• Quality depends heavily on the junior employee asking the right questions. Brief them beforehand on what to probe.

When to use it: When a new hire is starting and informal training is already happening. Stack the documentation on top of what’s already scheduled.

---

Method 4: Reverse-Document (Expert Does, You Write)

How it works: The expert does the task normally. You observe and write as they go, asking clarifying questions. When done, you hand them a draft to review.

Best for: Short, observable tasks where you can keep up in real time.

Honest tradeoffs:

• Puts almost no burden on the expert — they just do their job.
• Works well for physical tasks (prep procedures, equipment setup, closing checklists).
• Fails for complex cognitive work that happens in someone’s head. “What are you thinking right now?” breaks the flow.
• You need to be fast enough to capture steps without falling behind. If the task is short, this is the most efficient method by time-spent-per-SOP.

When to use it: Closing checklists, setup procedures, physical inspection flows — anything you can watch from start to finish in under 15 minutes.

---

The Default Path: The 30-Minute Interview

For most SMBs, the interview method gets you to a usable first draft faster than any other approach. Here’s why: the expert is just answering questions. The cognitive load stays with you, the interviewer. They talk; you write.

(Per Made to Stick — concrete beats abstract. The script below is not a framework, it’s a runnable plan.)

Before the interview

Send the expert one sentence ahead of time: “I’m going to ask you to walk me through [process name] like you’re explaining it to someone who’s never done it before. It’ll take about 30 minutes.”

That’s it. Don’t send a questionnaire. Don’t ask them to prepare. You want their natural, unfiltered version of how the work gets done.

Have a doc open to type into during the call. A blank Notion page, a Google Doc, a What’s the Process For process editor — whatever you’ll build the SOP in. Type every step they name, every condition they describe, every edge case they mention.

The interview script

Start with the trigger.

“Walk me through from the very beginning — what’s the signal that tells you this process needs to start? What happens, or what arrives, that kicks things off?”

This pins the entry point. Without it, experts start in the middle because the beginning seems obvious to them.

Get the steps.

“Okay, you’ve got [trigger]. What’s the first thing you actually do?”

Then, after each answer:

“And then what?”

Repeat until they reach the end. Don’t editorialize. Don’t suggest steps. Just ask “and then what?” Every time they slow down or skip ahead, repeat the question. You’ll get 70% of the SOP from this one loop.

Surface the conditions.

“Are there any situations where you’d do something different at that step? Any exceptions to the normal flow?”

This is where the real value is. The expert’s mental model is not a straight line — it’s a decision tree. This question opens the branches.

Get the failure modes.

“What’s the most common mistake you see when someone else does this step?”

“What’s happened in the past when this process went wrong?”

These answers become your “common errors” and “what to watch for” notes. They’re the difference between a checklist and an SOP that actually prevents problems.

Check the tools and resources.

“What tools, systems, or documents do you use to complete this? Is there anything you always reference?”

Logins, templates, vendor contacts, equipment, forms — anything they reach for. These become the “resources needed” section of the SOP.

Close with the output.

“When this process is completely done, what does done look like? How do you know it’s finished?”

This gives you the completion criteria. A new employee needs to know what “done” looks like before they hand off or move on.

The handoff question.

“If someone else was going to do this process and you weren’t available to answer questions, what’s the one thing you’d want to make sure they knew?”

Nine times out of ten, the answer to this question is the most important line in the entire SOP.

After the interview

You now have a rough draft in the form of interview notes. Clean them into numbered steps, add the exceptions as notes under the relevant steps, and strip any conversational filler.

Then send it back to the expert with one instruction: “I wrote up what you described. Can you read this and tell me anything that’s wrong or missing? Don’t worry about the formatting.”

Most experts will take 10 minutes to review a two-page draft. They’ll catch one or two things you missed. That’s your final SOP. The whole cycle — 30-minute interview, one hour of cleanup, 10-minute review — gets you from nothing to a working document in under two hours.

---

A Note on Knowledge That Resists Extraction

Some expertise genuinely doesn’t transfer through any of these methods. If your best salesperson just “reads the room” on a prospect call, or your senior tech “knows when a machine sounds wrong,” you’re not going to extract that into steps. Document what you can — the setup, the checklist, the information they gather — and note explicitly that the judgment call happens here, and here’s what experienced practitioners watch for.

A partial SOP is not a failure. It’s a starting point. The alternative is no documentation at all, which means the next person has to rebuild that judgment from scratch.

For a structured approach to capturing and organizing what you extract, see our employee knowledge transfer template. It gives you a ready-made format for each type of knowledge — procedural, conditional, and tacit.

---

What Comes Next: Templates vs. Writing From Scratch

Once you’ve done the extraction — however you do it — you’ll face another decision: do you format the knowledge into a template you found online, or do you build the structure yourself?

That’s the question we tackle in the next post in this series: SOP templates vs. writing from scratch. The short version is that templates save time but fail in specific ways. Knowing which pitfall applies to your situation saves you from reformatting everything two months later.

---

Start With One Process This Week

Pick one. Book a 30-minute call with the person who owns it. Use the script above. You don’t need buy-in from the whole team, a documentation platform, or a formal policy. You need 30 minutes and a blank document.

If you want a place to store what you extract — structured, shareable, and searchable for your team — try What’s the Process For free. No per-user fees. Your whole team, one flat rate.