Tacit Knowledge

Tacit knowledge is knowledge that cannot be fully articulated, codified, or transmitted through explicit instruction — the know-how, intuition, and contextual judgment that experienced practitioners possess but cannot readily explain. The concept originates with Michael Polanyi, who argued that "we can know more than we can tell": a scientist knows how to design a good experiment, a craftsperson knows how to shape material by feel, and a physician knows when a patient's presentation is abnormal before tests confirm it, all without being able to specify the exact rules underlying their competence. Tacit knowledge is not hidden explicit knowledge waiting to be extracted. It is a distinct epistemic category, embodied in practice rather than propositions, and learned through apprenticeship, imitation, and shared experience rather than formal training.

In institutional memory, tacit knowledge is the most valuable and the most perishable component: it leaves when its carriers leave, and no document can replace it. The attempt to render tacit knowledge explicit — through documentation, process engineering, or knowledge management systems — often destroys the very competence it seeks to preserve, replacing situated judgment with rule-following that fails when contexts shift.

See also: Domain Knowledge, Institutional Memory, Epistemology == Tacit Knowledge and Distributed Cognition ==

The conventional framing of tacit knowledge treats it as an individual property: something a person possesses but cannot articulate. This framing is incomplete. Tacit knowledge is also a distributed property — it exists in the relationships between people, in the coordination practices of teams, and in the material environments that skilled practitioners inhabit.

Consider a surgical team. The lead surgeon's tacit knowledge — the feel of tissue, the timing of an incision — is individual. But the team's tacit knowledge — who moves when, who anticipates what, how the room is arranged — is collective. It is not possessed by any single member but emerges from the interaction pattern. The same is true of software engineering teams: the knowledge of when to refactor, when to ship, when to reject a pull request is not in any individual's head but in the team's collective practice. When a team member leaves, the individual's tacit knowledge is lost, but the collective tacit knowledge may persist or may reconfigure depending on the team's adaptability.

The systems lesson: tacit knowledge is not merely epistemic. It is organizational. It is a property of the system (team, institution, practice) as much as of the individual. Attempts to capture tacit knowledge through documentation often fail because they target individual knowledge while the valuable knowledge is collective. The repository of tacit knowledge is not the person but the pattern.

The Embodiment Problem in Systems Design

Tacit knowledge poses a specific challenge for systems design: how do you build systems — organizations, technologies, institutions — that depend on knowledge that cannot be codified? The answer, most often, is that you do not build them to replace tacit knowledge but to support its exercise.

Consider the cockpit of a commercial aircraft. The flight management system does not contain the pilot's tacit knowledge of how to handle turbulence. It provides information — altitude, airspeed, weather radar — that the pilot interprets using tacit knowledge. The system is designed not to eliminate the pilot's judgment but to augment it. When designers forget this — when they automate away the contexts in which tacit knowledge is exercised — the system becomes brittle. The ironies of automation literature documents this: the more a system is automated, the less the operator practices the skills needed when the automation fails.

The systems insight is that tacit knowledge is not a design obstacle to be overcome. It is a design resource to be preserved. Systems that treat all knowledge as explicit and codifiable are systems that have not yet encountered the contexts where explicit knowledge fails. The failure is not a bug in the system. It is a design assumption that was wrong from the start.

Tacit Knowledge and Institutional Design

The perishability of tacit knowledge has implications for institutional design. Organizations that depend on tacit knowledge must design for continuity, not merely for efficiency. This means longer tenure, apprenticeship structures, and environments that allow tacit knowledge to be transmitted through practice rather than documentation. It also means accepting that some knowledge cannot be captured in a database and that the attempt to capture it may be counterproductive.

The systems critique of modern knowledge management is that it has confused information with knowledge and knowledge with competence. Information is data with context. Knowledge is information with judgment. Competence is knowledge with practice. Tacit knowledge operates at the competence level, and competence cannot be downloaded. It can only be developed, and development requires time, practice, and the social contexts that make practice meaningful.

The attempt to render tacit knowledge explicit is not always wrong. But it is always incomplete. The systems that succeed are those that know the difference between what can be codified and what must be cultivated — and that design for cultivation rather than extraction.