Tacit knowledge is the expertise your employees carry that cannot be fully written down: the pattern recognition a senior engineer builds after years of watching systems fail, the judgment a customer success manager develops about when a client relationship is at risk, the calibration an experienced recruiter applies to interviews that no rubric has ever successfully captured. It exists in every organization. Almost every organization is losing it.
Tacit knowledge is intuitive, experience-based expertise that individuals cannot fully articulate or document. Unlike explicit knowledge, which can be written down and transferred directly, tacit knowledge is acquired through hands-on practice and applied instinctively. Philosopher Michael Polanyi, who coined the concept, described it as knowing more than we can tell. Researchers estimate that tacit and implicit knowledge together account for 80 to 90 percent of an organization’s total knowledge base.
Philosopher Michael Polanyi, who introduced the concept in the 1960s, framed it in a phrase that remains the most accurate summary available: “we can know more than we can tell.” That gap between what someone knows and what they can articulate is not a failure of communication. It is a structural property of how deep expertise works. And it is why most knowledge management strategies address only the surface of the problem while the most valuable knowledge continues to disappear.
This post defines what tacit knowledge is, how it differs from other types of organizational knowledge, what it costs to lose, why standard preservation methods fall short, and why the place your organization is already generating tacit knowledge every day is also the place it keeps losing it.
What Are the Three Types of Organizational Knowledge?
Tacit knowledge is one layer in a three-part framework that most knowledge management approaches treat as a single undifferentiated problem. Understanding the distinction between the layers is the prerequisite for understanding why so many preservation efforts fail.
Explicit Knowledge
Explicit knowledge is codified and transferable: standard operating procedures, onboarding guides, technical manuals, product documentation. It can be written down, stored, searched, and consulted without the original author being present. If your organization's knowledge problem were limited to explicit knowledge, a well-maintained wiki and some editorial discipline would largely solve it.
It rarely is.
Implicit Knowledge
Implicit knowledge sits a layer deeper. It is the practical wisdom built by applying rules to real situations: the lessons from a project that went sideways, the troubleshooting protocols that emerged after a string of customer complaints, the best practices that developed through trial and error rather than from any formal process. Implicit knowledge can be articulated, but only by someone who has reflected carefully on what they actually know and why it works. It does not surface automatically under time pressure.
Tacit Knowledge
Tacit knowledge is the deepest layer and the hardest to preserve. It is intuitive, personal, and often impossible to fully verbalize. The research brief that frames this distinction estimates that tacit and implicit knowledge together account for approximately 80 to 90 percent of an organization's total knowledge base. The explicit layer, the documentation layer, is the 10 to 20 percent on top.
Tacit knowledge takes three forms in organizational contexts:
- Cognitive tacit knowledge: mental models, pattern recognition, intuition developed through repeated exposure to complex situations
- Technical tacit knowledge: craftsmanship, procedural skill, the physical or operational know-how that guides practice without being fully expressible in instructions
- Social tacit knowledge: interpersonal calibration, the ability to read a room, navigate organizational dynamics, or sense when a client relationship is shifting
What these forms share is that they are acquired through experience and applied instinctively. Experts often cannot fully explain why they do what they do, because the knowledge has moved below the level of conscious reasoning. That is not a limitation of the individual. It is the nature of deep expertise.
What Are Examples of Tacit Knowledge in the Workplace?
Tacit knowledge is easier to recognize in examples than in definitions. The following are the patterns that repeat most frequently across mid-size organizations:
- A senior engineer who can diagnose whether a system is about to fail from the pattern of errors appearing in logs, before any formal alert fires. The formal runbook describes what to check. The engineer knows what it means before checking.
- A sales representative who reads a prospect's hesitation correctly as a budget constraint rather than a product objection, and adjusts the conversation accordingly. No training manual covers this. It is built from hundreds of calls.
- An account manager who knows that a particular client's procurement process has an unusual approval step that adds three weeks if triggered after the 15th of the month. That detail is not in the CRM. It was learned through one difficult renewal.
- A customer support lead who knows which engineers to contact for which classes of problem, and more importantly, how to frame the request to get a fast response. This is social tacit knowledge: relational and contextual, invisible to anyone who did not build it.
- A recruiter who has conducted forty hiring cycles and developed a precise sense of which interview signals correlate with strong performance in this specific organization's environment. The rubric she could write captures perhaps 60 percent of what she actually uses.
In each case, the knowledge is real, consequential, and being applied every day. In each case, it would survive a resignation only by accident.
What Losing Tacit Knowledge Actually Costs
The financial case is specific. Research from Panopto estimates that inefficient knowledge sharing costs organizations $4.5 million annually for every 1,000 employees. McKinsey research on knowledge work finds that employees spend approximately 20 percent of their working week searching for information or tracking down the right colleague to ask. That is nearly a full working day per person per week spent compensating for knowledge that exists but cannot be found.
Those numbers describe the cost of knowledge that is present but invisible. They do not capture the cost of knowledge that has permanently left.
Panopto's research adds the figure that anchors this problem in concrete terms: 42 percent of role-specific expertise is known only by the person currently doing that job. When that person leaves, a new hire will typically spend close to 200 hours working inefficiently, re-asking questions that were already answered, and rediscovering things the team already knew. The explicit knowledge in the documentation may still be accessible. The tacit knowledge that made it useful is gone.
The compounding effect is what organizations tend to underestimate. As explored in what your company loses when employees leave, the people who remain inherit not just additional workload but a knowledge gap that makes their own work harder. The new hire who cannot find the answer interrupts a colleague who could have been doing something else. That colleague's deep work gets fragmented. The question gets answered, but the answer does not get preserved, and the next person starts the same cycle again.
The jet engine floor case from manufacturing illustrates the stakes precisely. In the 1990s, a production line began failing leak tests with no obvious cause. The assembly process was identical, the components unchanged, the instructions unmodified. Eventually someone noticed the facility had recently replaced its uneven creosote floors with smooth concrete. The original floors had vibrated during assembly in a way that seated the seals correctly. The new floors did not. No one had written this down because no one had known it mattered. The knowledge existed entirely in the felt experience of the workers who had assembled engines on those original floors. Its loss caused production failures that took significant time and investigation to diagnose.
That is tacit knowledge loss at its clearest: invisible until it disappears, expensive to reconstruct, impossible to recover through documentation after the fact.
What Is the Difference Between Tacit Knowledge and Explicit Knowledge?
| Dimension | Tacit Knowledge | Explicit Knowledge |
|---|---|---|
| Definition | Intuitive expertise that cannot be fully articulated or written down | Codified knowledge that can be documented, stored, and transferred directly |
| How acquired | Through practice, experience, and observation over time | Through instruction, reading, or formal training |
| Can be documented? | Only partially; the most valuable layer resists articulation | Yes; can be written into manuals, wikis, and databases |
| How transferred | Through mentorship, observation, shared practice, and captured conversations | Through documentation, training programs, and knowledge bases |
| Risk of loss | High; walks out the door when an employee leaves | Lower; survives turnover if documentation is maintained |
| Share of org knowledge | ~80–90% (tacit + implicit combined) | ~10–20% of total organizational knowledge |
Most knowledge management programs are built around explicit knowledge. They create wikis, maintain documentation, run offboarding interviews, and ask experts to write things down. These interventions are not useless: they address the 10 to 20 percent of organizational knowledge that is actually codifiable.
The problem is that the 80 to 90 percent that is tacit and implicit does not respond to the same treatments. You cannot document your way out of a tacit knowledge problem. A wiki does not capture why the floors needed to vibrate. A rubric does not transfer 40 hiring cycles of pattern recognition. An offboarding interview cannot download the social calibration a senior account manager built across three years of client relationship.
The distinction between tacit and institutional knowledge matters here. Institutional knowledge is the full body of what an organization collectively holds. Tacit knowledge is the most fragile subset of it: the layer that cannot be pulled into a repository on demand, that is not captured by self-reported skills profiles, and that walks out the door when the person who holds it leaves.
This is also why tribal knowledge persists as an organizational problem even in organizations that have invested seriously in documentation. Tribal knowledge, the informal, person-to-person transmission of expertise, is the primary vehicle by which tacit knowledge circulates. When that vehicle disappears because someone leaves, the knowledge disappears with it.
Why Standard Tacit Knowledge Preservation Methods Fall Short
The research on tacit knowledge preservation identifies a range of approaches: mentorship and apprenticeship, communities of practice, storytelling and after-action reviews, video documentation, half-standardized interviews with departing employees. Each has genuine value. Each also has a structural limitation that most implementations underestimate.
Mentorship and Apprenticeship
Direct tacit-to-tacit transfer through working in parallel with an expert is the most effective method available. It is also the most resource-intensive and the least scalable. It works when organizations can afford the time and overlap. It fails when the departure is sudden, when the apprentice does not yet know what questions to ask, or when the knowledge is held by multiple people across different domains simultaneously. Most organizations cannot run mentorship programs at the scale their tacit knowledge problem actually requires.
Offboarding Knowledge Transfers
The exit interview or structured offboarding session attempts to extract years of accumulated context in a few hours. By the final week, the departing employee is mentally transitioning. The person receiving the handoff does not yet know what they do not know, so they cannot ask the right questions. And the tacit layer is precisely what is hardest to surface under time pressure: experts cannot articulate what feels instinctive. The output tends to be explicit knowledge that was already partially documented, plus whatever implicit knowledge the expert happened to remember to mention.
Documentation Mandates
Asking experts to write down their tacit knowledge runs directly into Polanyi's observation. They can know more than they can tell. The documentation they produce captures the articulable layer. The tacit layer, the pattern recognition, the contextual judgment, the social calibration, goes unwritten because the expert cannot fully access it from memory at a desk. As explored in why your most experienced employees are not documenting their insights, the incentive structure around documentation is also broken: it is a separate task with no immediate payoff, competing with work the expert is actually evaluated on.
Internal Wikis and Knowledge Bases
Wikis address explicit knowledge. They become graveyards not because teams are careless but because tacit knowledge cannot be written into a page on demand. The knowledge that would actually prevent a production incident, close a renewal without friction, or hire the right engineer is not in the Confluence page. It is in the head of the person who has been doing it for six years.
Your Experts Are Already Externalising Their Tacit Knowledge. It's Just Disappearing.
Here is the insight that changes the problem: tacit knowledge externalization is already happening, continuously, in every organization that uses Slack.
When a senior engineer explains in a thread why a particular architecture decision was made, including the two production incidents that informed it and the specific conditions under which the alternative would still be appropriate, that is tacit knowledge being externalized in real time. When a customer success manager walks a colleague through how she handled a difficult client situation, she is narrating the contextual judgment that no rubric captures. When a product manager articulates the reasoning behind a pricing change in response to a question from a new hire, the tacit understanding behind the explicit decision is briefly visible.
What makes this different from a documentation mandate or an offboarding interview is the context. The knowledge surfaces in response to a real question, from a person who demonstrably knows the answer, in the moment when the knowledge is active and fully grounded. This is precisely the mode that the research identifies as most effective for tacit knowledge transfer: narrative-based, situated, responsive to actual need. The expert is not reconstructing knowledge from memory. The knowledge is live.
The problem is not that tacit knowledge is not being shared. The problem is that the sharing disappears. Slack is a river, not a library. As explored in why async communication keeps breaking, messages flow past and vanish into the archive. The next person who needs the same knowledge has no way to find the thread, so they ask again, interrupt the expert again, and the knowledge surfaces again with no organizational benefit from either exchange.
The jet engine floor story required someone to happen to notice the connection between the floor upgrade and the failure rate. That kind of discovery should not depend on one person being in the right place at the right time. It should be the result of an organization that captured what its people knew while they still knew it, and made that knowledge findable for everyone who came after.
How Do You Capture Tacit Knowledge?
Effective tacit knowledge preservation does not require a new documentation habit. It requires intercepting the knowledge at the moment it is already being shared, rather than asking experts to reconstruct it afterward.
The Slack thread where the architecture decision was explained does not need to be rewritten for a wiki. It needs to be captured, attributed to the person who contributed it, and made searchable for the next person who needs it. The expert contributes nothing beyond what they were already doing. The knowledge stops disappearing.
Attribution matters here in a way that documentation systems have rarely understood. When a contribution is captured and attached to a named person, and when colleagues can recognize that contribution as valuable by bookmarking or explicitly flagging it, two things happen simultaneously. The knowledge becomes trustworthy, because it carries the identity of someone who demonstrably knows the domain. And the incentive structure shifts, because the expert is no longer choosing between keeping knowledge private and giving it away without recognition. They are choosing between knowledge that disappears after one use and knowledge that builds a visible, searchable record of their expertise across the organization.
That record is also what makes expert discovery possible at scale. The engineer whose Slack explanation has been bookmarked by colleagues in three different teams is not just visible within engineering. They are visible as the domain expert to anyone who searches the relevant topic, with peer validation that no self-reported skills profile can replicate.
This is the infrastructure Pravodha is built to create: capturing the tacit knowledge your team is already externalizing in Slack, attributing it to the people who generated it, and making it permanently searchable for everyone who comes after. Not a new documentation process, and not another place to put things. A system that captures knowledge at the moment it is alive, rather than asking people to reconstruct it after it has already faded.
If your organization is watching valuable knowledge disappear into the Slack archive every day, we would like to show you what capturing it actually looks like in practice.