Somewhere in your building is the person everyone walks toward when a job goes sideways. Twenty-two years in, never written a procedure, carries most of the operation between their ears. The business runs on this arrangement and calls it experience. It is also a single point of failure with a truck payment.
The queue you cannot see
Spend one day watching the floor and count how often somebody crosses the shop to ask that person a question. Each trip looks like thirty seconds. Each is actually a queue: the parts counter is waiting on the answer, a tech is holding on a callback, dispatch has a ticket open that cannot close. The veteran's actual job — the one printed on the org chart — happens in the gaps between interruptions. None of this appears in any report, because interruptions are not a line item anywhere. The cost only becomes visible on the days the person is not there to absorb it.
The week they're at the lake
The most honest audit of your operation is free: write down what actually went wrong the last week that person took off. The list tends to look like this. A parts order stalled for two days because nobody else knew the supplier rep's direct cell, or that the catalog part number superseded to a different one two years ago. A tech drove forty minutes and got turned away at a plant gate, because nobody knew that account requires a safety orientation and long sleeves before anyone walks past the fence. An invoice bounced, because that customer's accounts payable rejects anything without a PO number — which the veteran always added, unprompted, and never mentioned to a soul. Each item is small. A week of them, compounding, is the real measure of what the person is worth, and a preview in miniature of the first quarter after they retire.
The three layers of what they actually know
The first layer is procedure: how this boiler gets flushed, how the warranty claim gets filed with that manufacturer. Some of it may even exist in a binder from 2014. The second layer is exceptions: the unit that takes the older gasket despite what the manual says, the alarm code that means a failed sensor and not a fire. The third layer is customer quirks: which property manager wants photos before and after every visit, which farmer pays after harvest but always pays, which gate code opens which yard, who expects a call before a truck rolls.
The layers are not equally replaceable. Procedures can be rebuilt from manuals and suppliers. Exceptions can be relearned, expensively, one callback at a time. But the customer layer, once lost, tends to cost you the customer — because from the customer's side, that knowledge was never information. It was the relationship. That is the layer to go after first, and it is the one no manufacturer's documentation will ever contain.
Why they will never write it down
Handing this person a laptop and asking for documentation produces three thin pages and a mutual grudge. Writing is a different skill from knowing, and after twenty years they genuinely cannot see their own knowledge — what registers to them as obvious does not register as worth recording. There is a structural problem too: a written SOP captures the procedure but almost never the exceptions, because exceptions only surface when something concrete triggers the memory. A blank page triggers nothing. A question does.
Capture by talking, not typing
So the method that works inverts the assignment: they talk, something else types. Sit them down for forty-five minutes with a recorder running and a junior employee whose entire job is to ask the obvious questions. Walk the shop. Work back through last month's strangest tickets. Drive the customer list account by account and ask what a new person would get wrong at each one. The transcript then becomes drafted documents — procedures, exception notes, customer notes — which the veteran corrects rather than writes. Correcting a wrong draft is easy, and for most veterans quietly satisfying; producing a blank-page document is neither. Forty-five minutes of talking reliably yields more usable material than a month of "please document your job."
From transcripts to answers people can find
A folder of transcripts is still a binder — better than nothing, unread within a year. The point of capture is retrieval: the material goes into a searchable internal knowledge base, so that when the question is actually asked — by a new hire, by dispatch, from a truck at 7am — the answer surfaces on its own, citing the walkthrough it came from. The citation is not decoration. An answer that shows its source can be checked and corrected; an answer with no source is just a new rumor with better formatting. And every question that comes back empty gets logged, which hands you the agenda for the next recording session.
What this cannot capture
Judgment does not transcribe. The sound a bearing makes the week before it lets go, the sense of when a customer is about to walk, the call to stop a job that looks fine on paper — those transfer through mentorship and time, not documents, and it would be dishonest to suggest otherwise. This is also not succession planning. It does not train a replacement, negotiate a retirement, or preserve the relationships that were personal rather than procedural. And the veteran has to review what comes out: transcription mishears part numbers, and a knowledge base with a wrong part number in it is worse than no knowledge base at all. What this buys is narrower, and worth stating plainly: the operational floor stops dropping to zero every time one person is unreachable.
Where to start
Write down the ten questions that only one person in your company can answer. If you stall before ten, ask your newest hire — they will finish the list in two minutes, because they live in the queue behind that person. That list is the agenda for the first recorded walkthrough, and getting it on paper costs you a legal pad and an honest half hour.