Skip to main content

What Is Tacit Knowledge? Definition, Examples, and Why It Is So Hard to Capture

Tacit knowledge is what experts know but cannot fully explain. It is built from years of experience and lives entirely in a person's head. When they leave, it is gone — unless you capture it before they go.

Book Executive Continuity ReviewStart Knowledge Sprint
GDPR CompliantEU Data Residency
80%
of organisational knowledge is tacit — held in people's heads, not written down
20+ years
required to develop the level of tacit expertise a retiring senior engineer carries
5 days
Knowledge Sprint to extract and structure an expert's tacit knowledge

The Definition

Tacit knowledge is knowledge that a person holds but cannot fully articulate. It is built from experience — from years of encountering situations, solving problems, making judgments, and developing intuitions about how things work. It is expressed not through words but through action: the way an expert handles a situation that a less experienced person would handle differently.

The concept was introduced by philosopher Michael Polanyi in the 1950s. His formulation remains the clearest: "We know more than we can tell."

Tacit vs. Explicit Knowledge

Every knowledge management challenge involves both forms.

Explicit knowledge is what can be written down, codified, and transferred. Processes, procedures, specifications, case notes, training materials — these are all explicit knowledge. They can be stored in a document and retrieved by someone who was never present when they were created.

Tacit knowledge is what cannot be fully codified. It is the judgment the engineer applies when the procedure says one thing but experience suggests another. It is the instinct the project manager has that something is wrong before the numbers reflect it. It is the client relationship intelligence a key account manager carries that explains why a particular approach works with a particular client.

Most knowledge management systems are good at capturing explicit knowledge. The tacit layer — which is where most of the value is — escapes them entirely.

Why Tacit Knowledge Is the Real Risk

Explicit knowledge is replaceable. If a procedure document is lost, it can be reconstructed. If a process manual becomes outdated, it can be rewritten.

Tacit knowledge is not replaceable on any reasonable timescale. The pattern recognition an experienced engineer has developed over 25 years cannot be transferred in a handover meeting. The client relationship intelligence a key account manager has built cannot be captured in a CRM note. When someone with significant tacit expertise leaves, the organisation loses something that took decades to build and cannot be recovered quickly.

This is why senior departures — retirement in particular — are the highest-risk knowledge events most organisations face.

How askSOPia Captures Tacit Knowledge

The fundamental challenge is that you cannot ask someone to write down what they know tacitly — they cannot fully articulate it. But they can express it in context: in meetings, in conversations, in the way they describe their decisions when asked about them in structured sessions.

askSOPia captures tacit knowledge from these contextual moments. When an expert explains their reasoning in a meeting, that explanation is captured and structured. When a decision is made and the logic behind it is articulated, that logic becomes part of the knowledge base. The knowledge is surfaced from how people already work, not from documentation effort.

Frequently Asked Questions

Tacit knowledge is knowledge that a person holds but cannot easily put into words. It is built from experience and expressed through action, judgment, and intuition rather than through explicit instruction. A surgeon who knows how much pressure to apply, an engineer who can hear that a machine is about to fail, a salesperson who reads a client relationship correctly — these are all exercising tacit knowledge. The concept was introduced by philosopher Michael Polanyi, who summarised it as 'we know more than we can tell.'

Explicit knowledge can be written down, codified, and transferred through documents or training. Tacit knowledge cannot be fully articulated — it can only be shared through experience, observation, practice, and conversation. Process manuals contain explicit knowledge. The judgment an experienced person applies when following or departing from that process is tacit. Most knowledge management systems handle explicit knowledge well and tacit knowledge poorly.

An experienced project manager who knows a project is at risk two weeks before the data shows it. A senior engineer who knows which design approach will cause problems during installation based on past experience. A key account manager who understands that a particular client's aggressive contract negotiations are a pattern, not a real threat. An operations director who knows that a process technically works but will fail under certain conditions that aren't documented. None of these can be written into a procedure manual.

The most effective methods are scenario-based: rather than asking someone what they know, walk them through specific situations and have them narrate their reasoning. Critical incident interviews (describing moments when they applied unusual judgment), think-aloud protocols (narrating what they are noticing and deciding in real time), and structured exit interviews focused on past decisions are more effective than asking someone to write a knowledge document. askSOPia extracts tacit knowledge from meeting recordings and conversations — capturing the reasoning people express in context rather than asking them to surface it in the abstract.

Because it is the primary source of competitive advantage that cannot be copied. Processes can be replicated. Systems can be duplicated. The accumulated judgment of experienced people — the pattern recognition that knows which situations need special handling and why — is not transferable through documentation. When it is lost through departure, the organisation must rebuild it from scratch through years of experience.

Next Step

Ready to Secure Your Knowledge?

Less than the cost of a bad first month of a mis-hire.

20 minutes. No slides. No prep needed.

Book Executive Continuity ReviewStart Knowledge Sprint

Related Topics

How to Capture Tacit Knowledge Before Your Experts Walk Out the Door→What Is Institutional Knowledge? Definition, Examples, and Why It Leaves→Tribal Knowledge Is Your Biggest Hidden Risk→A Key Person Is Leaving Your Company. What Now?→