CAPTiXCapture opportunities
pl·fr·en
Book a demo
← Blog

How to retain the know-how of departing experts?

Know-how only leaves with people when it exists solely in their heads. Capture it once and it becomes a lasting company asset.

On every shop floor, there are people others describe in the same way: “Ask them, they’ll know.”

Not because they have access to a different system. Not because they have read more procedures. They have simply seen every version of the same problem. They know when a machine sounds different than it should. They know which part will “still pass” and which one will come back from quality control. They know that the instruction says one thing, but in practice, you first need to check something no one ever added to the document.

That person often does not look like a “critical asset.” They come to their shift, do the work, help others, correct small mistakes, answer questions no one even writes down anymore. As long as they are on the floor, the process works.

The problem only becomes visible when they are not there.

Vacation. Sick leave. A move to another shift. Retirement. Leaving the company. Suddenly, it turns out that a part of the process that looked stable was stable only because one specific person was standing next to it.

On paper, everything is still there. The workstation. The procedure. The replacement. The production plan.

And yet the output starts to drift.

There are more questions. More rework. More calls to the team leader. More sentences starting with: “How did they do it?” That is the moment when the company realizes it has not only lost an employee. It has lost a piece of its process.

What is the real cost of losing an expert?

The cost of losing an expert starts exactly where the initial confidence ends: “But we have a procedure.”

Because when the person everyone used to “ask” disappears, the company rarely loses only one pair of hands. It loses a point of reference. It loses the memory of the workstation. It loses someone who had already seen all those small deviations that are not in the instruction, but decide whether the process runs smoothly or starts falling apart.

On paper, everything still looks fine.

There is a machine. There is a workstation. There is an instruction. There is a replacement. There is a production plan.

But on the shop floor, small signals begin to appear.

The new person follows the document, but does it more slowly. The team leader hears questions that no one used to ask anymore. Quality control stops parts that used to pass without issue. A technician explains an exception the expert used to recognize by sound, resistance, or the machine’s behavior.

No one makes one big mistake. The person who used to correct dozens of small things every day, before they became problems, is simply no longer there.

That is the real cost of losing an expert.

Not only recruitment. Not only severance. Not only the time needed to onboard a replacement. The cost sits in hundreds of micro-pauses, corrections, phone calls, questions, and decisions that used to happen automatically.

The expert often cannot even explain exactly what they do differently. For them, it is “normal work.” For the company, it is a hidden quality-control system.

In production, experience rarely looks like academic know-how. It looks like:

That is why losing an expert hurts so much. You can hire a replacement. You can hand over the workstation. You can provide the documentation.

But you cannot transfer fifteen years of experience overnight if the company previously allowed all of that experience to live only in one person’s head.

Why does text documentation fail?

Companies usually know they should document their processes. The problem is that documentation often describes the task, but does not show the work.

The expert has to perform the task, maintain output, respond to issues, and still find time to write down what they do. In practice, three things happen.

First, the expert has no time to write. If someone truly knows a critical process, they are usually needed at the workstation, not at a computer. Asking them to “describe how you do it” sounds reasonable, but on the shop floor it competes with the production plan, breakdowns, shift changes, and quality issues.

Second, the expert does not think in paragraphs. They think in movement, sequence, context, and exceptions. A large part of their know-how is practical: “watch out here,” “don’t do this too quickly,” “if it looks like this, the previous step went wrong.” These things are hard to capture in the formal language of a procedure.

Third, a document cannot capture everything the eye sees. A photo can show the part. A video can show the sequence. A recording from the worker’s point of view can show where the expert looks, what they check, and when they make a decision. Text alone often leaves the most important part implied.

That is why many plants have documentation, but still run on people.

The binder is on the shelf. The PDF is in the system. The instruction has a version number. And when a new person arrives, someone still says: “Come, I’ll show you how it’s really done.”

That sentence is a warning sign. It means the real process does not live in the documentation. It lives in a person.

What exactly should be retained?

Not all know-how needs to be archived. And not all expert know-how has the same operational value.

The most important know-how is what affects quality, safety, onboarding time, and process stability.

A good starting point is to ask:

This is not an HR exercise. It is an operational risk map.

If a company does not know where its critical know-how is, it only discovers it when that know-how leaves.

How do you capture gestures and context, not just words?

The best method is not an interview at a desk. The best method is observing the work.

The expert should perform a normal task, in the normal environment, at the real workstation. That is when you see things they often cannot describe themselves: where they look before starting, what they check automatically, when they slow down, when they speed up, which elements they ignore because they know they are not critical.

A recording from the worker’s point of view makes it possible to capture several layers of know-how at once.

Hand movements. Sequence of actions. Workstation context. Machine sound. The moment of inspection. The difference between correct and incorrect positioning. The response to a deviation.

This is precisely the know-how that usually disappears in traditional documentation.

Text says: “Install the component according to the instruction.”

Demonstration says: “Hold here, don’t press too early, check this angle, and if you hear this sound, go back to the previous step.”

In production, that difference determines quality.

Why should expert know-how not remain a video in a folder?

A recording alone is not yet a standard.

Many companies already have training videos. The problem is that after a few months, no one knows where they are, which version is current, or whether they show the exact work variant that applies today.

A video in a folder is an archive. An instruction at the workstation is a tool.

The difference is simple. An archive is watched when someone remembers it exists. A tool guides a person while they are working.

That is why expert know-how needs to be turned into short, practical steps:

Such an instruction does not replace the expert one-to-one. It does something more important: it turns their way of working into a reference point for the whole team.

How do you make that know-how available to others?

Know-how retained in the company only has value when someone can use it.

Not next week in training. Not after logging into the quality system. Not after finding the right PDF.

At the moment the work is being done.

If a replacement is standing at the workstation, the instruction should be available at the workstation. If a new person is performing a step for the first time, they should see that step in context. If an employee speaks another language, the standard should be possible to follow without translating the entire binder.

This is especially important in plants with mixed teams: senior experts, younger operators, agency workers, people from different countries, and employees moved between lines.

In that environment, know-how cannot remain the private asset of the best people. It must become part of the work system.

The point is not for every employee to become an expert on day one. The point is for everyone to have access to the best available reference before they make an expensive mistake.

How do you measure whether know-how transfer works?

If retaining know-how does not change the numbers, it was probably just a documentation project.

Four things are worth measuring.

The last point matters most. Averages can hide the problem. One shift may still achieve excellent results because an experienced person works there. Another shift may struggle with the same process every week.

Know-how transfer only works when the standard moves from the person into the process.

It is worth collecting a baseline before the expert leaves or before the organizational change. For two to four weeks. Without it, any discussion about impact will be a discussion about impressions.

How does Aikando help retain expert know-how?

Aikando does one thing in this process: it helps capture the way the best people work and turn it into instructions available to others.

This is not about writing long procedures. It is about capturing practical know-how in a form that can be used at the workstation: step by step, visually, in the context of the work.

In practice, Aikando helps to:

It does not replace experts. It removes the most repetitive part of know-how transfer from their shoulders.

The expert is still needed for difficult cases, process improvement, and teaching people the context. But they no longer need to explain the same sequence of steps for the tenth time only because the company never captured it properly.

The most important point is that the know-how stays in the company.

Not as a memory of the best employee. As a standard people can return to.

Where should you start?

Not with a company-wide “know-how management” program.

With one person and one workstation.

Choose an expert whose departure would create a real problem. Choose a process that generates questions, rework, or dependence on that person. Record how the work is done during a real task. Turn it into a short instruction. Make it available to the replacement or to another shift. After one month, compare the numbers.

One workstation, one expert, one month. That is enough to check whether know-how is starting to move from the person into the process.

Companies do not lose know-how because people leave. People will always leave: for retirement, for other companies, for other departments, for other roles.

Companies lose know-how when they allow it to exist only in people’s heads.

If the best way of working is captured, demonstrated, and made available at the workstation, the departure of an expert stops being an operational disaster. It becomes a change the process is prepared for.

Book a demo: info@captix.eu