In 1966, philosopher Michael Polanyi proposed an idea that has since become one of the most important — and most ignored — insights in organizational theory: "We know more than we can tell." He called this tacit knowledge, and he was describing something every experienced professional intuitively recognizes. The surgeon who can sense a complication before the monitors show it. The account manager who knows exactly how to frame a difficult conversation with a long-standing client. The plant engineer who hears something wrong in a machine before it fails. None of these people can fully write down what they know. But the knowledge is real, and it is extraordinarily valuable.
Organizations have built entire disciplines around managing explicit knowledge — the documented, searchable, transferable kind. Wikis, intranets, knowledge bases, SOPs. These systems have real value. But they capture, at best, the surface layer. The deeper layer — the judgment, the pattern recognition, the relational intelligence, the accumulated intuition — remains almost entirely unmanaged. And in most organizations, it remains almost entirely unprotected.
The Tacit–Explicit Spectrum
It helps to think of organizational knowledge not as a binary but as a spectrum. At one end sits fully explicit knowledge: the process document anyone can follow, the contract template in the shared drive, the formula in the spreadsheet. This knowledge can be written down, transferred, and used by someone who has never met the person who created it. It is, by definition, the easiest kind to preserve.
At the other end sits knowledge that resists articulation entirely — the kind Polanyi was pointing at. A master glassblower who can judge the temperature of molten glass by its color and luminosity, in ways that no thermometer or manual can fully replicate. A senior negotiator who reads the room in ways that defy a checklist. This knowledge is embodied, experiential, and deeply personal.
In between lies the territory most organizations fail to navigate: knowledge that is partially articulable — where an expert, under the right conditions, can surface more than they think — but that will never be fully captured by a documentation mandate. This middle ground is where most enterprise tacit knowledge lives, and it is where the greatest opportunity for systematic preservation exists.
What Tacit Knowledge Looks Like in Practice
Abstract definitions are useful. But it is the concrete examples — the ones that appear in enterprise settings every day — that clarify the scale of what is at risk.
- Expert judgment under uncertainty: The risk analyst who can assess whether a counterparty is likely to default based on conversational signals that never appear in a credit file. The investment banker who knows which deals will actually close, beyond what the pipeline numbers suggest.
- Pattern recognition built over years: The IT security lead who can identify a social engineering attempt in an email from subtle linguistic tells. The procurement officer who recognizes a supplier in financial distress months before it surfaces in audited accounts.
- Relationship context: The account director who knows that a key client stakeholder has a particular sensitivity about being surprised in executive meetings — and navigates accordingly. The knowledge of how to work with specific people, across specific histories, is almost never documented.
- Unwritten rules and institutional memory: Why a particular policy exists the way it does. Which decision two years ago shaped the current architecture. Why the organization doesn't pursue a specific category of deal, even though it looks attractive on paper. These are the invisible guardrails that experienced people carry and new hires spend years learning by collision.
Why "Write It Down" Is the Wrong Answer
The standard organizational response to tacit knowledge risk is the documentation mandate. Before you leave, fill in the handover notes. Complete the knowledge transfer form. Do an exit interview. The intent is right. The method is chronically inadequate.
The first problem is cognitive. Much tacit knowledge is, by definition, below the threshold of conscious awareness. Experts don't know what they know — not fully. Asking them to document it is asking them to articulate something they have never needed to articulate, under time pressure, at the end of their tenure. The results are inevitably thin.
The second problem is motivational. Documentation feels like overhead, separate from the "real work." In organizations where documentation is not culturally embedded — which is most of them — it gets deprioritized, abbreviated, or delegated to someone who does not actually hold the knowledge.
The third problem is structural. Even when documentation happens in good faith, it captures what without the why. It records decisions without the reasoning that produced them. It describes outputs without the judgment that shaped them. The resulting document may be accurate as far as it goes, but it is not transferable in any deep sense. A new hire reading it can follow the steps. They cannot yet make the calls.
How Ambient Capture Changes the Equation
The shift that has made tacit knowledge preservation newly tractable is not a change in human behavior — it is a change in the environment in which humans work. The modern enterprise produces an enormous ambient record of its own intelligence: emails, meeting transcripts, decision threads, Slack conversations, project retrospectives, client notes, proposal drafts, and commentary that accumulates across every system of work.
This record is imperfect. It is noisy, unstructured, and distributed across dozens of platforms. But embedded within it, at scale, is something that has never before been systematically extractable: the tacit knowledge of the organization, partially surfaced through the traces of how its people actually think and decide.
AI inference applied to this ambient record can identify patterns that no individual knowledge audit would surface. It can recognize which experts are the real decision nodes — not by title, but by the structure of who gets consulted on what. It can extract the reasoning chains behind past decisions, not as clean narratives, but as the actual sequence of considerations that shaped an outcome. It can flag when institutional knowledge is concentrated in single individuals and model the risk that represents.
This is not documentation. It is knowledge archaeology — working with what already exists rather than adding burden to people who are already too busy. And it represents the first genuinely scalable approach to the problem Polanyi identified six decades ago.
Making Tacit Knowledge an Organizational Priority
The organizations that will pull ahead on this are not the ones that run better exit interviews. They are the ones that treat tacit knowledge as a strategic asset requiring active stewardship — not a byproduct to be captured at departure, but a resource to be identified, mapped, and preserved continuously.
That means understanding where critical knowledge is concentrated. It means building systems that learn from the ambient record of organizational work, not just from what people choose to document. It means creating conditions where tacit knowledge can be partially surfaced through structured interaction — not because experts are asked to write manuals, but because the right questions, at the right moments, can draw out what would otherwise remain implicit.
Polanyi's insight was that the gap between what we know and what we can tell is fundamental and irreducible. No technology changes that. But the gap between what organizations currently preserve and what they could preserve, with the right approach, is enormous — and it is closing. The organizations that recognize tacit knowledge as their most valuable and most vulnerable asset, and act accordingly, will find themselves with a durable advantage that their competitors cannot easily replicate. Because the knowledge that makes organizations exceptional is, almost by definition, the knowledge that cannot be written in a manual and handed to the next person.
Scirevance was built for exactly this problem — not to replace the human knowledge that makes organizations exceptional, but to ensure that knowledge does not simply disappear when the people who carry it move on.
See how Scirevance captures and preserves tacit knowledge across your organization — explore why enterprises choose Scirevance.