He has thirty years of process knowledge. None of it is written down. Ask him to document his workflows. He produces nothing, or a page only he understands.
What Happens
- He agrees to write documentation. A week passes. Nothing arrives.
- He hands you a document that skips every step he considers obvious. Most steps are obvious to him.
- When you point out a gap, he explains it verbally, clearly and in full. He does not update the page.
- He trains people one-on-one. He will not formalize what he teaches.
- He says: “It’s all up here,” and points to his head.
- He retires or leaves. The knowledge leaves with him.
Why It Happens
Knowing what no one else knows is a position. If the process lives only in his head, he stays necessary. This is Knowledge Hoarding. It is not always conscious. It connects to Need for Relevance. He does not think “I will protect my job.” He thinks “no one else understands this system.” Both things are true.
He built his expertise by doing. Documentation is not his craft. He is The Expert. Experts execute. Sitting at a keyboard to describe a ten-minute task feels wrong to him. The page takes longer to write than the task takes to run.
Writing also forces him to look at what he actually does. He fears the page will reveal one of two things. The first: his process is simpler than people assume. The second: his workarounds are improvised and look wrong. Neither is safe. The Fear of Vulnerability is real and it runs in both directions.
A written page transfers authority. If anyone can read it and do his job, he becomes replaceable. He knows this. That collides with Authority Preservation. He is The Reluctant Mentor at the documentation level. He will teach you in person. He will not write it down.
What You Can Do
Ask for one task, not everything. “Document your role” is an impossible request. “Walk me through the Monday morning check” is something he can do in ten minutes. Start with one process. Record it if he agrees.
Write the first draft yourself. Interview him. Take notes. Build the document. Then give it to him to correct. He will mark it up. He will fix your errors. He will add what you missed. He authors nothing. He corrects everything. Say: “I’ll write the first draft. Tell me where I got it wrong.”
Quick Tip
Put a deliberate small error in your draft. Experts correct mistakes. He will fix it, expand around it, and return something more complete than anything he would write from scratch.
Use video for hands-on work. A five-minute phone video at the machine captures more than a page of written instructions. Ask him to show you once while you film it. That is documentation.
Put his name on the page. List him as the owner and reviewer of every document he touches. Include “Owner: [His Name]. Last reviewed: [Date].” The document does not replace him. It records him. Say this directly: “You’re the only one who knows this. Let’s make sure you get credit for it.”
Set a narrow deadline for a narrow thing. Do not ask for a documentation project. Ask for one page, on one process, by a specific date. Publish it. Then repeat.
See also: Documenting Institutional Knowledge