What Experts Know But Cannot Articulate

Ask a senior sales engineer how they qualify a deal in the first ten minutes of a call. They will give you a list: budget, authority, need, timeline. Ask them to watch a recording of themselves qualifying a deal and narrate what they are actually thinking at each moment. You will get a completely different answer — one with texture, with pattern matching, with reads on tone and hesitation that they never mentioned in the list. The list is their explicit model of what they do. The narration is what they actually do. The gap between those two things is tacit knowledge.

1. Explicit Knowledge Articulable, documentable, transferable through instruction. "The process has five steps." "The formula is X divided by Y." "The rule is: if A, then B." Explicit knowledge is already structured. The work of capturing it is transcription, not extraction.
2. Tacit Knowledge Embodied, contextual, and resistant to verbalization. "I just know when the deal is real." "Something felt off about the architecture." "That customer is a flight risk — I can tell." Tacit knowledge lives in pattern recognition built through years of experience. The expert cannot hand it to you because they do not know they are using it.
3. The Extraction Gap Most knowledge capture efforts operate entirely in the explicit layer. They ask experts to describe their process and document what they say. The result is a sanitized, idealized account that omits everything the expert considers too obvious to mention — which is exactly the knowledge you need. The extraction gap is the difference between the stated process and the actual process.
4. Why It Matters When the expert leaves, the explicit knowledge stays in the documentation. The tacit knowledge walks out the door. The new hire follows the documented process and produces systematically worse results, not because the document is wrong but because the document is incomplete. Knowledge extraction is the discipline of closing that gap before it costs you.