Tacit Knowledge vs Documented Knowledge: Closing the Gap

Two very different kinds of knowledge, treated as one

Ask most business owners what their company "knows" and they will point to the documented layer: SOPs, policy manuals, onboarding decks, a shared drive of files. This is documented knowledge, sometimes called explicit knowledge, and it is real and useful. It is also a small fraction of what actually keeps the business running.

The larger, harder-to-see layer is tacit knowledge: the judgment, pattern recognition, and situational instinct that experienced people carry but rarely articulate, because it was never something they consciously learned as a rule, it was something they absorbed through repetition until it became automatic. A senior salesperson who can tell within the first two minutes of a call whether a lead is serious. An operations manager who knows, without checking a manual, which client complaints need immediate escalation and which can wait until tomorrow. None of this shows up in a policy document, because it was never written as a policy, it developed as instinct.

The mistake most companies make is treating documentation as a solved problem once the explicit layer exists, without recognising that the tacit layer, the part actually driving most day-to-day judgment calls, remains almost entirely uncaptured.

Why tacit knowledge is so hard to document

People do not know what they know. This sounds paradoxical, but it is the central difficulty. An experienced employee often cannot fully articulate why they made a particular call, because the reasoning happened fast, intuitively, drawing on years of accumulated pattern recognition rather than a conscious, step-by-step process they could describe if asked directly.

It only surfaces in context. Tacit knowledge tends to appear only when someone is actually doing the task, or actively troubleshooting a real problem, not when they are sitting down separately to write documentation. Ask someone to write an SOP in the abstract and you get the clean, general-case version. Watch them actually handle a messy real situation and you see the exceptions, judgment calls, and shortcuts the clean SOP never mentioned.

It resists simple written form. Some tacit knowledge really is difficult to reduce to a checklist, because it depends on reading subtle cues, weighing several factors at once, or a feel for a situation that took years to develop. This does not mean it cannot be captured at all, but it usually requires a different approach than writing a standard procedure document.

Nobody asks for it directly. Most documentation efforts ask "what is the process," which reliably produces the explicit layer, the official steps. Almost nobody asks "what do you actually pay attention to that is not in the process," which is the question that would surface the tacit layer, and it rarely gets asked because it does not occur to most people that there is a gap between the two.

Why the gap is dangerous, specifically

A company that has documented its explicit knowledge well can feel falsely confident that its knowledge is "captured." This is exactly where the risk sits. New hires trained purely on the documented layer learn the rules but not the judgment for when the rules do not quite fit, which is most real, messy situations. They follow the SOP correctly and still get the outcome wrong, because the SOP was never the whole picture, it was the visible fraction of a much larger, undocumented layer of judgment that experienced staff apply automatically without realising they are doing it.

This is also exactly what disappears fastest when an experienced employee leaves. The explicit documents stay behind. The tacit judgment, the part that actually made that person good at their job, walks out the door, because it was never captured anywhere durable in the first place.

Practical ways to actually surface tacit knowledge

Ask about exceptions, not procedures. Instead of "what is our refund policy," ask "tell me about the last three times you made an exception to the refund policy, and why." Exceptions are where tacit judgment lives, because they are precisely the cases the written rule did not anticipate.

Capture reasoning in the moment, not in a retrospective interview. The richest source of tacit knowledge is an experienced person explaining a real decision as they make it, or shortly after, while the reasoning is still fresh and concrete. A structured interview weeks later tends to produce a cleaned-up, generalised version that has already lost most of the specific, situational detail.

Use real, recent examples as prompts. Rather than asking someone to describe their judgment in the abstract, which tends to produce vague generalities, walk through a specific recent situation they handled and ask them to narrate their thinking at each step. Concrete examples reliably surface detail that abstract questions do not.

Watch for the phrase "it depends," and dig in. Whenever someone answers a question with "it depends," that is almost always a signal of tacit knowledge sitting just under the surface. Follow up specifically: depends on what, and how do you tell which situation you are in. That follow-up question is usually where the actual valuable judgment lives.

Interview your best performers specifically, not just whoever is available. Tacit knowledge is unevenly distributed. The person who has been quietly excellent at handling a certain type of client for six years holds far more valuable tacit knowledge about that specific situation than a broader survey of the whole team would surface.

Turning captured tacit knowledge into something usable

Capturing tacit knowledge is only half the work. The other half is making it usable for someone who does not yet have the instinct the original person developed over years. This usually means translating instinct into something closer to a decision framework: not a rigid rule, but a structured way of thinking through the same kind of judgment call, including the signals an experienced person would notice and the questions they would ask themselves.

This is harder than documenting a straightforward process, and it is exactly the layer most companies skip, because it takes real effort to draw out and structure. It is also, not coincidentally, the layer that provides the most value once it exists, because it is the layer a generic course or a competitor's playbook can never replicate. It is specific to how your best people actually think, which is precisely what makes it valuable and precisely why it is worth the extra effort to capture properly.

Why this has become more achievable recently

Historically, systematically capturing and structuring tacit knowledge required a trained interviewer, real time investment, and a formal knowledge management process most SMEs could never justify. That barrier has genuinely lowered. A structured, well-designed set of prompts, combined with a system that can turn a spoken or written explanation into something queryable, makes this kind of capture realistic for a company that has never had a knowledge management function and never will.

The remaining bottleneck is not technology, it is discipline: someone has to actually sit down with the people who hold the knowledge and ask the right questions, consistently, over time, rather than treating it as a one-off project.

A worked example of the gap in practice

Picture a small B2B services firm with a documented sales process: qualify the lead, send a proposal within 48 hours, follow up on day three, close within two weeks. On paper, this is complete. Any new salesperson can read it and follow it exactly.

Now watch the top-performing salesperson actually work a lead. She skips the standard 48-hour proposal timeline for a lead that mentions a specific competitor by name, because she has learned, over dozens of similar deals, that this particular signal means the prospect is already comparing vendors seriously and a same-day response wins disproportionately more often. She spends extra time on a discovery call with a certain kind of hesitant, detail-oriented prospect, because she has learned rushing them to a proposal backfires, while a more decisive-sounding prospect gets moved faster than the documented timeline suggests. None of this appears anywhere in the documented process. It is not written because it was never consciously formalised as a rule, it is a set of pattern-matched judgment calls she makes automatically after years of doing this specific job.

A new hire following only the documented process will hit reasonable results on average, and will also make exactly the mistakes she learned to avoid years ago: the same-day-response signal she now catches automatically, the pacing mismatch with hesitant prospects. Capturing her tacit knowledge specifically, through the kind of exception-focused questioning described above, and turning it into an explicit decision framework new hires can actually query, is what closes a gap the original SOP was never going to close on its own, no matter how well it was written.

Closing the gap deliberately

The companies that manage this well treat documented and tacit knowledge as two separate capture problems, not one. Explicit knowledge gets written down through standard SOPs and policies. Tacit knowledge gets deliberately drawn out through the kind of specific, exception-focused, example-driven questioning described above, and then structured into something the rest of the team can actually query and learn from.

This distinction sits at the core of how Decisionlore is built: a structured boss-interview process specifically designed to surface the tacit layer, the exceptions and judgment calls a standard SOP walkthrough would miss, alongside straightforward document ingestion for the explicit layer you already have written down. If the gap between what your company has documented and what your best people actually know in practice feels wider than it should be, our pricing page outlines how the capture process works in practice.