EPISODE · Jun 18, 2026 · 51 MIN
Knowledge that walks
from Compound Conversations · host Jesse Flores and Julie Mann
Most organizations don't lose institutional knowledge when people leave. They lose it the day they stopped treating it as an asset.In this episode, Jesse and Julie break down the knowledge transfer problem that sits underneath nearly every stalled AI implementation and why it isn't an HR problem or a succession planning problem. It's a design problem. You'll walk away able to do three things: Identify the load-bearing roles in your organization before someone walks out the doorRun a structured knowledge capture interview that surfaces the judgment, exceptions, and rules of thumb that never make it into a job description. Sort what you've captured using the TML framework so your agents actually have what they need to execute.They also walk through the difference between documentation and capture, why transcripts are the highest-leverage starting point for any knowledge management discipline, and how to calculate the opportunity cost of the institutional knowledge that's currently living in someone's head without a backup. There's a downloadable interview worksheet with the questions — what decisions do you make that nobody else makes, what exceptions have you handled, what would a new hire get wrong — so you can run this on a real role before the week is out.TakeawaysInstitutional knowledge doesn't show up on the balance sheet, but it carries a real opportunity cost. The production you aren't getting from your AI agents is often a direct result of the knowledge you haven't captured yet.The load-bearing role in your organization isn't always the one with the most visible title. It's the one whose absence would cause the most people to stop working — the signature, the translator, the person everyone already knows to route things through.You cannot automate what lives in a person's head. The discipline of knowledge capture isn't a nice-to-have for successful AI implementation. It's the prerequisite.Chapters 00:00 The context problem underneath every AI failure02:24 The "Charlie" scenario07:05 When knowledge walks: a real story11:49 Institutional knowledge as a balance sheet asset18:52 Onboarding drag and why we don't have to accept it23:38 Knowledge isn't a continuity risk. It's the cake.33:13 Finding your load-bearing roles40:33 The interview questions that surface judgment47:45 Design before deployRegister for Live Conversations via the link.
What this episode covers
Most organizations don't lose institutional knowledge when people leave. They lose it the day they stopped treating it as an asset.In this episode, Jesse and Julie break down the knowledge transfer problem that sits underneath nearly every stalled AI implementation and why it isn't an HR problem or a succession planning problem. It's a design problem. You'll walk away able to do three things: Identify the load-bearing roles in your organization before someone walks out the doorRun a structured knowledge capture interview that surfaces the judgment, exceptions, and rules of thumb that never make it into a job description. Sort what you've captured using the TML framework so your agents actually have what they need to execute.They also walk through the difference between documentation and capture, why transcripts are the highest-leverage starting point for any knowledge management discipline, and how to calculate the opportunity cost of the institutional knowledge that's currently living in someone's head without a backup. There's a downloadable interview worksheet with the questions — what decisions do you make that nobody else makes, what exceptions have you handled, what would a new hire get wrong — so you can run this on a real role before the week is out.TakeawaysInstitutional knowledge doesn't show up on the balance sheet, but it carries a real opportunity cost. The production you aren't getting from your AI agents is often a direct result of the knowledge you haven't captured yet.The load-bearing role in your organization isn't always the one with the most visible title. It's the one whose absence would cause the most people to stop working — the signature, the translator, the person everyone already knows to route things through.You cannot automate what lives in a person's head. The discipline of knowledge capture isn't a nice-to-have for successful AI implementation. It's the prerequisite.Chapters 00:00 The context problem underneath every AI failure02:24 The "Charlie" scenario07:05 When knowledge walks: a real story11:49 Institutional knowledge as a balance sheet asset18:52 Onboarding drag and why we don't have to accept it23:38 Knowledge isn't a continuity risk. It's the cake.33:13 Finding your load-bearing roles40:33 The interview questions that surface judgment47:45 Design before deployRegister for Live Conversations via the link.
NOW PLAYING
Knowledge that walks
No transcript for this episode yet