Every process business has one or two people who are the answer to too many questions. When they go, the facts mostly survive in documents. The judgement, the context and the mental map of where everything is usually do not. This is a strategic problem, not an IT one, and it is worth naming plainly before it becomes urgent.
The demographic reality
Process industries skew experienced. A large share of the deep operational knowledge sits with people who have been doing the job for decades and are closer to the end of their careers than the start. That is not a criticism, it is the shape of the workforce, and it means a predictable amount of hard-won knowledge is going to leave over the next several years. The only question is whether it leaves with the person or stays with the business.
What actually gets lost
It is rarely the documented facts. It is three harder things:
- Judgement. Not the facts, which are usually written down somewhere, but the sense of which fact matters when, and how to weigh a trade-off that the manual does not cover.
- Context. Why a process is run a particular way, what was tried before and abandoned, which customer has a quirk that is not in the system. The reasons behind the decisions, not just the decisions.
- The map. Where things are. A thirty-year veteran does not remember every detail, but they know exactly which folder, which colleague, and which old study to reach for. That index is often the most valuable thing of all.
Want to keep the map, not just the files?
We help capture the judgement and context, and make your existing archive answerable with citations, so one person’s memory is not a single point of failure. A short call, no pitch.
Book a technical callWhy documentation projects usually fail
- They ask for a data dump. Sitting someone down to "write everything down" produces a document nobody reads and that captures the easy, explicit knowledge while missing the tacit judgement that was the point.
- They happen too late. The project starts when the retirement date is announced, which is exactly when the person is least available and most checked out. The knowledge walks out on schedule.
- The output is not usable. Even good notes become another unsearchable archive. If nobody can find the answer at the moment they need it, the knowledge has not really been retained.
The common thread is that a documentation project treats knowledge as content to be dumped, rather than as something to be captured in use and made findable. Making the result searchable and answerable is as important as capturing it in the first place.
What capturing it while people are still employed looks like
The version that works is undramatic. Capture happens as part of the normal work, not as a farewell project: decisions and their reasons recorded as they are made, the old archive brought into one searchable place, and the veteran’s answers captured when they are actually asked rather than in an artificial sit-down. The goal is not a perfect record. It is that when the person is on holiday, or gone, the next colleague can find the answer and, just as importantly, the reasoning behind it. That is the same source-of-truth idea that runs through the whole chemical and process industries approach.
Frequently asked questions
Is this not just a documentation problem?
Partly, but the hard part is not the explicit knowledge that documents capture well. It is the tacit judgement and context that people carry and rarely write down. A pure documentation push tends to capture the easy half and miss the valuable half.
How does AI help with knowledge retention?
It does not replace the person, and it does not magically extract judgement. What it does is make the knowledge you do capture, and the archive you already have, searchable and answerable with citations, so the map in someone’s head is less of a single point of failure. The capture still needs to happen while the person is employed.
When should we start?
While the person is still in post and engaged, not when the leaving date is set. The best capture happens as a normal part of the work, not as a rushed handover.
Does this touch process safety?
No. Capturing operational knowledge and making documents searchable is separate from safety decisions, HAZOP, LOPA or control systems, which stay with the qualified people and existing methods.