Glossary
Tacit knowledge in business
Michael Polanyi described it in eight words in 1966. The business consequence is that your documentation is an accurate map of where your expertise is not.
Tacit knowledge (noun). Knowledge a person uses but cannot fully state: pattern recognition, standards, and the judgment that arrives ahead of its own explanation. Named by Michael Polanyi in The Tacit Dimension, 1966.
In a business, it is the portion of an operator's expertise that is systematically absent from every place the business keeps knowledge, because those places capture what was sayable.
Polanyi's line is the whole thing: we can know more than we can tell. You may know it as unconscious competence. You know what to do. You cannot fully explain how you know, or reduce it to steps someone else could follow and get the same result.
The surgeon's hand recognises a pressure no paragraph teaches. The negotiator feels the moment to stop talking. You read a proposal that checks every box and know the deal is wrong before you can say why. In each case the judgment arrives first and the explanation follows, late, partial, and sometimes never.
Read your knowledge base backwards
Every business over a certain size has a place where knowledge is kept. A wiki, a drive, a process library, an onboarding pack, a folder of standard operating procedures.
The usual reading is that this is the company's knowledge. It is worth reading it the other way.
Which makes the whole thing a record of the easy half.
Nothing was excluded on purpose. There is no gatekeeper filtering out the valuable material. The filter is upstream of anyone's intent: a thing can only be documented if it can first be put into words, and the parts of expertise that resist being put into words are exactly the parts that took longest to acquire.
So the knowledge base is accurate and it is a negative image. Where it is thick, the work was explainable, which usually means it was already close to teachable, which usually means it was never your advantage. Where it is thin or missing, either nobody got round to it, or somebody tried and found there was nothing to write.
The second case is the one to go looking for. It is where the business is carrying real expertise, and it is the region that no documentation project has ever reached, in any company, in any decade.
The tell is written in your own procedures
There is a five minute version of this. Search your process documents for two phrases.
- Use your judgment.
- Escalate if needed.
Both are honest. Whoever wrote them reached a point in the process where the next step depended on something they could not specify, and rather than pretend, they marked it.
Every hit is a coordinate where the transfer failed. And it is never the trivial part of the process. The place a procedure gives up is reliably the highest stakes moment in it, which is why the documents identify their own gaps better than any audit would.
Why this became urgent rather than merely interesting
Tacit knowledge has been a known problem in management literature for decades and it stayed academic for a simple reason. There was nothing to do about it. The only transfer mechanism was one person standing next to another for years, which does not scale in any direction and dies with the person.
What changed is not that the knowledge became sayable. It did not, and it will not. What changed is that capture stopped requiring articulation.
The judgment becomes visible for a few seconds every time it is applied to a real case. Approve, reject, correct, make an exception, explain why something technically correct is still not good enough. Those seconds were always there. They were simply never recorded, because recording them required something present at every decision, paying attention, that could hold what it saw.
That is the part that now exists. The knowledge is no more sayable than it was in 1966. It is just no longer necessary to say it.
Frequently asked
What is tacit knowledge in a business context?
The knowledge someone uses to run the business but cannot fully state. Pattern recognition, standards, the sense that a proposal is wrong before the reason arrives. Michael Polanyi named it in 1966 with eight words: we can know more than we can tell. In a business it shows up as the difference between what the person does and what the person is able to explain about what they do.
How is tacit knowledge different from undocumented knowledge?
Undocumented knowledge is knowledge nobody has written down yet. Tacit knowledge is knowledge that resists being written down at all, by the person who has it, with unlimited time and every intention of being helpful. The first is a backlog. The second is a property of the knowledge itself, and no documentation project closes it.
Why does documentation systematically miss it?
Because documentation captures what was sayable. Every entry in your knowledge base got there because somebody could put it into words, which pre-selects for the easy end of the expertise. The result is accurate, useful, and a negative image of where your real advantage lives.
How was tacit knowledge transferred before now?
By proximity, over years. Someone stands next to the expert long enough to see the exceptional cases, not just the routine ones. That is what an apprenticeship is, and the length of it was never about instruction time.
If it cannot be stated, how can it be captured?
By not asking anyone to state it. It becomes briefly visible whenever a decision is made: an approval, a rejection, a correction, an exception. In those few seconds the judgment is applied to a real case, which is a completely different thing from being described in the abstract. Capture the moment and you get the judgment without anyone having to articulate it.
Where this sits
Tacit knowledge is the problem the whole category is a response to. The category is defined at What is Imprinted AI. The historical solution, and why it took so long, is at apprenticeship without the decade.
Related terms
- Apprenticeship without the decade. The only method that ever moved this knowledge, and the reason it took so long.
- Imprint. What captured tacit judgment becomes once there is somewhere to put it.
- An Imprint vs an SOP. What happens to the reason when you write the steps down anyway.
- Imprinted AI vs a Custom GPT. Why asking someone to describe themselves hits the same ceiling.
Where the term comes from
This is one entry in the vocabulary of a longer argument. The full glossary has fifteen terms. The case they belong to runs about 23,000 words, it is free, and there is no email gate on it.
Read The A.I. Business Manifesto
Nothing on this page is for sale. Quote it, argue with it, or pass it on.
Last updated: 28 July 2026