When people talk about tacit knowledge they usually picture a workshop: the engineer who can hear a bearing going, the operator who knows the machine trips on cold mornings. That is real. But the same thing is happening at every desk in the building, and it is harder to see, because desk work looks as if it is all in the system.
It is not. The system holds the records. The people hold the way the work gets done.
Month-end close in finance
The close has a checklist. It lists the journals, the reconciliations and the deadlines. It does not say which supplier always invoices late and needs an estimated accrual, which intercompany balance never matches first time and why, or that a particular report from the sales system double-counts credit notes and has to be adjusted by hand. One person knows. When they are off at month end, the close runs late and nobody can quite say why.
Customer service escalations
Every service team has a written escalation path. Every experienced agent also knows the real one: which complaints go straight to a named person because the policy will not fix them, which phrases from a customer mean they are about to leave, what you can offer without asking and what you cannot. New agents follow the written path, escalate things that did not need it, and miss the ones that did.
Planners and schedulers
A planner's spreadsheet looks like the plan. The real plan is in their head: which jobs can slip and which cannot, which customer will accept a late delivery if you ring them first, which crew is quietly slower than the system thinks, which two orders must never land in the same week. The tool records their decisions. It does not record the reasons.
Account managers
An account manager knows who really signs off at a client, who to copy and who to leave out, what was promised two years ago that never made it into the contract, and which topics to avoid this quarter. The CRM has the contact names and the meeting notes. The relationship lives in one person. When they move on, the client notices before the company does.
IT support
The ticketing tool holds thousands of closed tickets. What it rarely holds is the actual fix. "Resolved" covers a lot. The experienced person knows that a certain error on a certain laptop model means a driver, not a hardware fault, that one application has to be restarted in a particular order, and that one department's printer problem is really a network setting. They know because they found it once, and they never wrote it down because fixing it was quicker than explaining it.
Why it stays invisible
Desk knowledge hides for three reasons.
- The system looks complete. Everything is logged, so it feels documented. But a log of what happened is not an account of how to decide.
- One person covers the gaps quietly. The planner adjusts, the finance lead corrects, the support engineer fixes it before anyone notices. The work looks smooth because someone is absorbing the difficulty.
- Nobody asks until they need it. The knowledge only shows when it is missing: someone is on leave, off sick, or has handed in their notice. Then the close slips, the escalation goes wrong, the big client gets an awkward email, and everyone realises how much one person was carrying.
What to do about it
Treat desk work exactly as you would a shop floor. Pick the processes where one or two people seem to be the only ones who really know how it goes. Ask them about the last real case: the last close, the last difficult escalation, the last week the plan fell apart. Ask why at each step. Ask what a new person would get wrong. Then ask the others who do the same work, and compare.
You will find the same pattern you find anywhere: steps everyone does, steps one person does that should be shared, and places where people quietly disagree. Each of those is worth knowing before the person who holds it is away.
That is what our product is built for. A company describes the problem, an AI drafts the questions, and each person talks or types with an AI interviewer for five to twenty minutes, on their phone or laptop, in their own language. You read every answer in English and get a ranked report of what goes wrong, with how many people raised each point and their own words, plus procedures, handover docs and a knowledge base. Nobody is rated.
The finance team, the service desk and the planners are as worth asking as anyone on the floor. Usually nobody ever has.
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.