Knowledge Concepts
What is tacit knowledge? A clear explanation for team leads and ops people — what tacit knowledge is, why it's the hardest knowledge to transfer, and practical methods to make it explicit.
Tacit knowledge is knowledge that is difficult or impossible to express in words or documentation — the know-how embedded in experience, intuition, and judgment rather than explicit rules — such as how an expert recognizes a problem pattern instantly, why a senior engineer's code review catches what others miss, or how an experienced manager reads a room to sense conflict before it surfaces.
The term was coined by philosopher Michael Polanyi in 1958 with his famous aphorism: "We can know more than we can tell."
Michael Polanyi, a Hungarian-British scientist and philosopher, introduced the concept of tacit knowledge in his 1958 book Personal Knowledge and developed it in The Tacit Dimension (1966). His starting observation: human expertise consistently exceeds what can be written down or communicated explicitly. A trained doctor can recognize illness in a patient's posture before any diagnostic test; a chess grandmaster sees patterns invisible to skilled amateurs; a master craftsman produces outputs that no manual of their technique can fully explain.
Polanyi's insight became foundational in organizational theory, cognitive science, and knowledge management. Ikujiro Nonaka and Hirotaka Takeuchi extended the concept in The Knowledge-Creating Company (1995), arguing that tacit knowledge is the source of sustained organizational competitive advantage — because it can't be easily copied or documented.
The practical consequence for organizations: when an experienced person leaves, they take knowledge that was never captured and may be impossible to fully transfer. This is the "knowledge drain" risk that knowledge management, mentorship programs, and documentation efforts try to address.
| Explicit knowledge | Tacit knowledge | |
|---|---|---|
| Expressibility | Can be written, documented, transmitted | Hard or impossible to fully articulate |
| Transfer method | Documents, training materials, manuals | Observation, mentorship, practice, experience |
| Examples | Procedures, formulas, codes, policies | Intuitions, pattern recognition, judgment calls |
| Can be copied? | Yes — easily reproduced | No — must be developed through experience |
| Organizational risk | Low (documented = preserved) | High (leaves with the person) |
The distinction matters practically: explicit knowledge can be captured in a wiki or process document; tacit knowledge cannot. The manager who "just knows" which customer is about to churn, the developer who "just knows" where a bug is likely to live, the negotiator who "just knows" when to push and when to hold — these are tacit knowledge in action.
Tacit knowledge operates through several mechanisms:
Pattern recognition. Expert practitioners have built up a large library of recognized patterns through experience. When a senior engineer looks at a pull request and immediately spots the architectural problem, they're pattern-matching against thousands of past code reviews — a library of patterns that was never formally compiled.
Procedural memory. Skills learned through practice become automatic — cycling, typing, driving. These are tacit in the sense that the practitioner can execute them without conscious attention, but can't easily translate the execution to words a beginner could follow.
Embodied heuristics. Experienced practitioners develop intuitions — rough rules of thumb that aren't precise enough to be codified but guide reliable judgment. A project manager's "this one feels off" about a timeline is an embodied heuristic, not a data point.
Contextual sensitivity. Experts know when rules apply and when they don't. The novice follows the rule; the expert applies the principle with judgment for context. The difference is tacit.
A senior customer success manager at a SaaS company has tacit knowledge about customer churn risk. She can often predict, in a client meeting, which accounts are at risk of not renewing — months before any dashboard metric turns red.
What she knows explicitly: She can articulate some signals — "when they stop bringing business stakeholders to calls, that's a warning sign."
What she knows tacitly: The way an account manager's tone changes when things are going badly; the specific combination of frequency + tone of support tickets that signals frustration, not just usage; the difference between a strategic champion and a political champion and which type of champion departure matters more. She couldn't write these down precisely enough for a new hire to apply them.
What the organization loses when she leaves: The model she's built in her head — trained on 300+ accounts over 5 years — cannot be fully transferred through documentation. A new hire with access to all the same data will still spend 2-3 years building a comparable model.
Tacit knowledge can never be fully captured, but it can be partially externalized:
1. Shadowing and apprenticeship Have novices observe experts in action and ask "why did you do that?" for each decision. The articulation required to answer these questions surfaces tacit knowledge the expert didn't know was implicit.
2. Think-aloud protocols Ask experts to verbalize their thought process while solving a representative problem. Cognitive psychology research shows that think-aloud protocols capture significantly more of an expert's decision process than post-hoc interviews.
3. Case documentation Record edge cases and non-obvious decisions as they happen — not just "what we did" but "what we considered and why we decided against it." Post-mortems and case studies capture the judgment layer, not just the outcome.
4. Structured debriefs After significant decisions, conduct structured interviews with the decision-makers: What signals did you notice? What alternatives did you consider? What made you choose this path? This is more effective than asking experts to write their knowledge — the interview surfaces what self-documentation misses.
5. Communities of practice Wenger (1998) identified communities of practice — groups of practitioners who share work and talk about it — as the primary mechanism for tacit knowledge transfer between peers. Not formal training; informal shared practice with discussion.
Remote teams face a specific tacit knowledge risk: the informal transfer mechanisms that work in co-located teams — watching over someone's shoulder, overhearing how a senior person handles a difficult call, absorbing office culture through proximity — are absent.
The research is consistent: knowledge transfer in remote teams defaults to explicit knowledge only. Tacit knowledge either fails to transfer at all, or transfers much more slowly. This is one driver of the longer time-to-competence for remote new hires.
Mitigation strategies for remote teams:
For knowledge managers and team leads trying to document institutional knowledge — the explicit layer — WebSnips can support the web research input to those documentation efforts:
Tacit knowledge itself requires the human knowledge elicitation methods above. WebSnips handles the explicit web research and external context that enriches the documentation you do create.
Can tacit knowledge ever be fully made explicit? No — Polanyi's original argument was that all knowledge has a tacit dimension that cannot be fully articulated. Even the most detailed procedure manual requires tacit knowledge to apply correctly (judgment about when the procedure applies, how to handle exceptions, how to recognize when something is "not quite right" even when no rule is violated). The goal of knowledge management is to externalize as much of the useful tacit knowledge as possible, not to eliminate the tacit dimension.
Why is tacit knowledge hard to transfer through documentation? Documentation captures what can be said; tacit knowledge is precisely what can't be fully said. A manual can tell you the 12 steps to make a soufflé; it can't transfer the feel of when the batter is exactly right. A best practice document can list what signals to watch for in a difficult customer; it can't transfer the judgment about which combination of signals, in which context, from which type of customer, means what.
What's the biggest organizational risk from unmanaged tacit knowledge? Key person dependency. When critical tacit knowledge is concentrated in one or two individuals who have no successor and no knowledge transfer plan, the organization is exposed to significant risk from turnover. This is the scenario knowledge management programs are most often created to address.
Is AI good at capturing tacit knowledge? AI tools can observe patterns in data — which is useful for explicit, measurable signals (engagement metrics, behavioral data). They struggle with the same things humans struggle to articulate: the intuitive, contextual, pattern-based judgment that constitutes deep tacit expertise. AI assistants can help elicit tacit knowledge (through structured questioning) but cannot replace the apprenticeship and community-of-practice methods that transfer it.
Tacit knowledge is knowledge we carry but cannot fully tell — the expertise, judgment, and intuition that makes experienced practitioners irreplaceable and that no documentation effort can fully capture.
For remote team leads and knowledge managers, tacit knowledge is both the most valuable organizational asset and the most fragile one. The methods that surface it — apprenticeship, structured shadowing, think-aloud protocols, deliberate case documentation — require investment but protect against the knowledge drain that accompanies every significant departure.
The goal is never to eliminate the tacit dimension. It's to make enough of it explicit that your organization doesn't have to start from scratch every time an expert moves on.
More WebSnips articles that pair well with this topic.
What is citation management? A clear explanation for researchers and academics — how citation managers work, the best tools, and how to avoid the most common mistakes.
What is a commonplace book? A clear explanation of the centuries-old knowledge collection practice, famous examples, and how to build a modern digital version for writers and researchers.
What is a knowledge graph? A clear explanation of the technology, how Google's knowledge graph works, and what personal knowledge graphs in tools like Obsidian actually do.