Capturing Tribal Knowledge: Why SOPs Aren't Enough and What to Build Instead

Your best employee's expertise isn't in any document. It's in their head, their habits, their judgment calls. Here's how to get it out before it walks out the door.

Mom's Apple Pie Recipe vs. Grandma's Kitchen

Jon LoDuca, who spent 25 years as an intellectual capital advisor extracting wisdom from industry veterans, has a metaphor that stopped us in our tracks the first time we heard it.

He holds up a recipe card, your standard apple pie recipe. Ingredients, steps, oven temperature. "This is a perfectly good outline," he says. "Especially if you know how to make a pie. If you've made one before, you could follow this. But if you've never seen a pie, if you're a brand new employee with zero background, they wouldn't make a pie out of this. It'd just be some mess in a bowl."

That recipe card is your SOP.

Then he shows the alternative: grandma in the kitchen, shoulder to shoulder with you. When you're in the kitchen with grandma, a whole lot more happens than just ingredients and directions. She's telling you stories. She's pouring values and culture into you while you learn a discrete activity. You're getting what Jon calls tribal knowledge, the stuff that makes the difference between someone who follows steps and someone who actually gets it.

"After years of learning shoulder-to-shoulder with grandma," Jon says, "you wouldn't just make pies like grandma. You'd come out of there thinking like grandma."

That's the gap. SOPs are great at documenting tasks: here's the standard, here's what it looks like when done right. What they're not good at is everything in between: the judgment, the principles, the values that inform how to do it. You only get that from apprenticing with the master.

Or at least, that's what most people assume.

The Tribal Knowledge Problem

Every company has tribal knowledge. It's the estimator who can price a job in half the time because she's seen a thousand of them. It's the sales rep who knows exactly when to call and when to wait. It's the maintenance guy who can diagnose a problem by the sound the machine makes.

This knowledge is your most valuable operational asset. It's also your most fragile. Because it lives in people's heads, and people leave.

Most companies aren't that lucky. They wake up to the tribal knowledge problem after the damage is done, after the veteran leaves, the key person gets sick, the expert retires. Then they scramble to reconstruct what that person knew, usually from the incomplete memory of the people left behind.

The cost isn't just the knowledge itself. It's the compounding degradation. The replacement trains the next person from an incomplete understanding. That person trains the next. Within two or three generations, you're operating on a faded photocopy of what was once a sharp, detailed picture.

Why SOPs Fail at Capturing Tribal Knowledge

If SOPs worked for this, you wouldn't be reading this article. But let's be specific about why they fail, because understanding the gap is the first step to filling it.

What SOPs Capture	What Tribal Knowledge Includes
The steps to complete a task	Why certain steps matter more than others
The standard outcome	What to do when things don't go according to plan
Which tools to use	The workarounds when tools aren't available
The correct sequence	The judgment calls that change the sequence depending on context
Pass/fail criteria	"We tried that approach three years ago and here's why it doesn't work"

There's also a practical problem. When companies try to close the gap by making SOPs more detailed, those SOPs balloon to 10, 14, 20 pages. And then nobody reads them. Jon nails this tension: "Folks get frustrated because there's not enough information in their SOPs, so they write really good ones. Then they're 14 pages long and nobody reads them. You're damned if you do, damned if you don't."

SOPs exist on a frustrating spectrum: too thin and they're useless for anyone who doesn't already know the job, too thick and they become shelf-ware that nobody opens.

The Video-First Approach to Knowledge Capture

The breakthrough is simpler than you'd expect: video. Not polished, professionally produced video. Phone video. The subject matter expert, standing at their workstation, showing you how they do what they do.

Why video works where documents fail:

• It captures context. You see the environment, the tools, the body language. You see what "right" looks like in motion, not as a static description.
• It's fast to create. A 2-minute video takes 2 minutes to make. Writing the equivalent SOP takes an hour.
• It preserves judgment and reasoning. When a subject matter expert talks through what they're doing, they naturally explain why: "I check this first because..." That's the tribal knowledge. It comes out in speech far more naturally than in writing.
• AI can extract the SOP from it. Modern platforms like Playbook Builder transcribe the video and auto-generate written work instructions. So you get both (the rich video for deep learning, and the quick-reference text) from a single recording.

Jon demonstrated this live during one of our sessions. He recorded a 35-second video playing "grandma" explaining her apple selection: which varietals, why, where to source them, what to check for. Hit a button. The AI stripped the video, transcribed it, and generated formatted work instructions: "Select apple varietals: Braeburn, Spy, Granny Smith, and Rome. Obtain from Coffey's non-GMO pesticide-free orchard. Check for grubs and worms before adding to filling."

The video captured the full context and reasoning. The AI extracted the actionable steps. Both from a 35-second phone recording.

How to Extract Tribal Knowledge from Your Team

You don't need a documentary crew. You need a process and the right questions.

1. Identify your subject matter experts. These aren't always the people with the fanciest titles. Jon's advice: "Don't pick yo-yos. Somebody might have a title but not be a credible expert. Pick someone who's engaged, wants to mentor, and is respected by the team." Look for the person everyone goes to when things break. That's your SME.
2. Start with the highest-impact process. Don't try to capture everything at once. Pick the process that causes the most pain, costs the most money, or has the most risk if the current expert leaves. One playbook at a time.
3. Use the AI architect to create a first draft. Tools like Playbook Builder can generate a process outline from a simple description. You can also upload existing SOPs and let AI build a framework from them. Either way, you're starting with 80%, not a blank page.
4. Interview the SME on camera. Walk through the process step by step. For each step, ask: "Why do you do it this way?" and "What's the most common mistake you see?" These questions pull out the tribal knowledge that would never make it into a written SOP. Keep videos short: 1-3 minutes per step.
5. Let AI generate the written instructions. Transcribe the videos, auto-generate work instructions, and now you have a multimodal training asset: video for deep learning, text for quick reference, both from the same source recording.
6. Add QR codes for just-in-time access. Print QR codes and stick them where the work happens, on equipment, in the warehouse, at workstations. Your team can scan and immediately access the relevant training video on their phone, right when they need it. No logging into an LMS, no hunting through a drive.

What Happens When You Capture Tribal Knowledge Successfully

When Miles at Dietz Property Group recorded his HVAC videos, something interesting happened beyond the obvious knowledge preservation. The new technicians didn't just learn the steps. They learned Miles's approach. They understood why he checked certain things in a certain order. They got the benefit of 22 years of pattern recognition compressed into short, accessible videos.

We see this pattern repeatedly:

• New hire ramp-up drops dramatically. Instead of months of shadowing and absorbing by osmosis, new employees get structured access to the same expertise, on demand, repeatable, at their own pace.
• Consistency goes up. When everyone is trained from the same source (the actual expert), you stop getting ten different versions of how the job should be done.
• The experts get freed up. Your best people spend a massive amount of time answering the same questions, mentoring, and cleaning up other people's mistakes. Capture their knowledge once and they get that time back.
• Institutional knowledge becomes a real asset. It's no longer fragile. It doesn't depreciate when people leave. It appreciates as you add to it. If you ever go to sell the business, that knowledge library is a tangible, demonstrable asset that makes your company more valuable.

Stop Treating Knowledge Like It's Infinite

Here's the uncomfortable truth: your tribal knowledge has an expiration date. It expires when the person carrying it leaves, retires, gets sick, or simply forgets. Every day you don't capture it is a day you're gambling that those people will be around tomorrow.

The tools exist to make this fast. A subject matter expert can record a 2-minute video in less time than it takes to write an email. AI can turn that video into structured documentation. A platform can deliver it to the right people at the right time and track who's actually engaged with it.

The methodology exists too. Jon LoDuca and the team at Playbook Builder have spent a quarter century refining this process: from identifying the right SMEs to interviewing them effectively to building the delivery system that ensures the knowledge actually gets used.

What's missing isn't technology or process. It's the decision to start. Pick one expert. Pick one process. Hit record. Get the first 80% captured, push it to your team, and iterate from there.

Your grandma won't be in the kitchen forever. The question is whether you'll capture her recipes (the real ones, with all the stories and judgment and wisdom) before she's gone.