Can tacit knowledge be fully captured?

No. Some of it stays a skill that only comes with practice. The goal is to capture enough of the reasoning that others can handle most situations on their own and know when to ask.

What is the difference between tacit and implicit knowledge?

The terms are often used loosely. Implicit knowledge is usually knowledge someone could put into words if asked; tacit knowledge is harder to articulate at all. Interviews about real cases tend to surface both.

When should a company start capturing it?

Before anyone announces they are leaving. Capture works best when the expert has time to explain and to review what was written, not in their last two weeks.

What is tacit knowledge, and how do you keep it when experts leave?

Updated 8 October 2026 · 7 min read

Tacit knowledge is the know-how people build through experience but rarely write down: which supplier needs a reminder two weeks early, how a site handover really runs, why a clause sits in the standard contract. Every company runs on it, and it is the knowledge most likely to disappear when someone retires, changes roles or resigns.

Tacit knowledge vs. explicit knowledge

Explicit knowledge is what is already written down: procedures, contracts, specifications, the project plan. Anyone with access can read it. Tacit knowledge lives in judgement. It is knowing which of the ten steps in the procedure actually matter, what a warning sign looks like before it shows up in a report, and who to call when the official route is too slow.

We can know more than we can tell.

Michael Polanyi, The Tacit Dimension (1966)

Polanyi's point still holds: experts often cannot list what they know until someone asks them the right question about a real situation.

What it looks like in practice

Project management: when a subcontractor's missed milestone is a one-off and when it is the start of a slide.
Procurement: which suppliers pass every formal audit but still deliver late in the busy season.
Quality: what a borderline inspection result looks like, and when to stop the line.
Finance: how progress payments are really negotiated with a particular client, beyond what the contract says.
Operations: the workarounds that keep a process running when a system or a person is unavailable.

Why documentation alone doesn't capture it

Experts don't know what they know. Asked to write everything down, they produce the obvious steps and skip the judgement calls that make them experts.
Writing takes time experts don't have. The people with the most valuable knowledge are usually the busiest, and documentation is the first thing to slip.
Documents answer the author's questions. A procedure covers the cases its author anticipated. Colleagues get stuck on the cases nobody thought to write down.
Documents age. The process changes, the document doesn't, and people quietly stop trusting it.

Signs your company depends on tacit knowledge

The same few people get the same questions every week.
Work waits until one person is back from leave.
New hires take months to work independently, even with good documentation.
Procedures exist, but experienced people don't follow them as written, and things still work.
A resignation or retirement announcement causes a scramble to “get everything out of their head”.

Practical ways to capture tacit knowledge

Ikujiro Nonaka and Hirotaka Takeuchi described the move from tacit to explicit knowledge as externalization: it happens through dialogue, examples and reflection, not by asking someone to fill in a template. The methods that work all follow that idea.

Structured interviews by role. Ask about real situations (“When did you reject a supplier who passed every check?”) rather than general processes.
Shadowing. A colleague follows the expert through real work and writes down the decisions, not just the steps.
After-action reviews. Short reviews after a project phase: what we expected, what happened, what we would do differently.
Pairing and mentoring. The successor works alongside the expert well before a planned departure.
Capturing decisions in meetings. Many explanations are said once in a meeting. Recording the decision and the reason behind it keeps them.

How to start, in five steps

Find the people whose absence would stall work. In most mid-sized companies it is a handful of senior experts.
Log the questions they get for one week. The repeats show you which knowledge is in demand.
Map their topics. List the areas each expert owns and mark where nothing is written down.
Interview, then let the expert check. Use role-specific questions about real cases, and have the expert review what was captured.
Keep it current. Review the questions that couldn't be answered, regularly. That is where the remaining gaps are.

Where an AI expert twin fits

Hypha follows the same steps with software. A 20 to 30 minute AI interview asks role-specific questions about real situations, the expert's documents and meetings fill in the rest, and the result is a twin of that expert that colleagues can ask. Every answer shows its sources, the expert sees the questions and verifies or corrects the answers, and the questions the twin can't answer become a short weekly list for the expert. Before someone leaves, Handover mode runs an intensive 2 to 4 week capture so the role's knowledge stays with the company.

Frequently asked questions

Can tacit knowledge be fully captured?: No. Some of it stays a skill that only comes with practice. The goal is to capture enough of the reasoning that others can handle most situations on their own and know when to ask.
What is the difference between tacit and implicit knowledge?: The terms are often used loosely. Implicit knowledge is usually knowledge someone could put into words if asked; tacit knowledge is harder to articulate at all. Interviews about real cases tend to surface both.
When should a company start capturing it?: Before anyone announces they are leaving. Capture works best when the expert has time to explain and to review what was written, not in their last two weeks.