What is tacit knowledge, and why does it matter?

A plain explanation, with examples from the floor and the office

By The Human Union team · 12 Oct 2026 · 4 min read

Tacit knowledge is what someone knows but has never been asked to say. It sounds like this:

  • "You can tell the termination's going to fail before you test it."
  • "That machine trips on cold mornings, you let it warm up ten minutes."
  • "Don't send Dave to flats, send him to the farms."
  • "Month-end never balances until you chase the Leeds depot's credit notes."
  • "That customer says urgent about everything. Ring them before you escalate."

None of it is in the procedure. All of it is why the work gets done.

Where it lives

It lives with whoever has done the job longest, on the floor and at a desk alike. The engineer who knows which fault code lies. The planner who knows which supplier always ships a day late. The finance lead who knows which accounts to check first when the numbers look wrong. It is rarely written down, because the people who hold it are busy, because it feels obvious to them, and because nobody asks.

Why it matters now

People move on. Some retire, some change roles, some leave for a competitor, and each time part of how the work is done goes with them. New starters learn by shadowing whoever is free, and pick up that person's habits along with the knowledge. And every team is being asked what could be automated or handed to software, which only works if someone can say how the work is really done, exceptions and all.

Three kinds of step

When we map how a piece of work is done, we sort every step three ways:

  • Routine. Anyone, or a system, could do it with the right information: booking a slot, filing a certificate, chasing a status.
  • Procedural. A trained newcomer can do it with good instructions. This is where most of the hours are, and where a written procedure pays back fastest.
  • Judgement. It needs experience you cannot hire in a week: signing off a permit, calling a borderline result, deciding which customer to ring first. This is where the real risk sits, and the first thing to write down.

Capturing tacit knowledge is not a documentation project. It is how you find out which steps are which, and make sure the judgement does not walk out of the door.


See it with your own example. Thirty minutes with our team, using a question from your own work. Book a demo, or try the ROI calculator first.

See it with your own example

Thirty minutes with our team, using a question from your own work.

Book a demo