When knowledge lives in people, your operation is fragile

In industrial environments, between 80% and 90% of operational knowledge is never documented. When the people who hold it leave, the operation loses capability immediately.

There's a technician on your shop floor who knows exactly what to do when line 3 jams during the second shift. He knows which bolt to adjust, in what order, and how tight. He didn't learn it from a manual. He learned it over fifteen years of experience.

One day that technician retires. Or moves to another company. Or is simply off sick. And line 3 stops. And nobody knows why. What used to take ten minutes to fix now takes half a shift.

This isn't an isolated problem — it's an operational risk. And it affects more industrial companies than most care to admit.

In this article, we look at why these companies still rely on specific people to function, why traditional documentation doesn't solve the problem, and how to build an infrastructure that makes knowledge outlast the people who create it.

The knowledge you can't see hurts the most when it's gone

Every industrial company has two types of knowledge. Explicit knowledge is what's written down: manuals, procedures, technical datasheets. Tacit knowledge is what lives in people: tricks, judgment calls, sequences learned over the years. The instinct that something doesn't sound right in a machine before it actually fails.

The problem is the ratio. **Between 80% and 90% of knowledge in an organization is tacit.**¹ It's not in any document. It's not in any system. It lives in the heads of operators, supervisors, and technicians who've been doing their jobs for years.

And when those people leave, they take that knowledge with them. A report by Panopto and YouGov estimates that 42% of the skills and expertise in a role are known only by the person doing the job.² When they leave, nobody can cover nearly half of what they did.

In the European industrial sector, this takes on an extra dimension. The European Centre for the Development of Vocational Training (Cedefop) estimates that the manufacturing industry will need 10.2 million replacement workers by 2030, largely driven by mass retirements from the baby boomer generation.³ And recent data shows that 57% of baby boomers admit to sharing less than half of their knowledge before retiring.⁴

In Spain, the problem intensifies. According to Randstad, 38.5% of Spanish companies experienced an increase in employee turnover in 2022.⁵ Every departure doesn't just mean finding someone new. It means losing what that person knew and never transferred.

Documenting isn't the answer (at least not the way you're doing it)

The typical reaction to this problem is obvious: "Let's document everything." Someone writes a 200-page manual, uploads it to a shared folder, and assumes knowledge is now protected.

It isn't. Because nobody reads those documents.

It's not a willpower problem. It's a format problem. Static content competes against inertia, against the urgency of the shift, and against a number that says it all: one week after a training session, the average employee has forgotten 65% of the content.⁶ If that happens with active training, imagine what happens with a PDF nobody opened.

Technical manuals, printed work instructions, and Word-based procedures serve a documentary and regulatory function. But confusing documentation with knowledge transfer is a mistake we see repeated in nearly every plant we work with. Documenting doesn't mean it's understood, and assuming someone will read a training PDF when they have ten tasks to finish before their shift ends doesn't work either.

Real knowledge transfers when it's consumed, understood, and applied. A file nobody opens transfers nothing.

Document Inertia on the shop floor

There's a concept that describes well why industrial companies remain stuck in this model. We call it Document Inertia: the tendency of organizations to keep using static formats (PDF, PowerPoint, printed manuals) for training, despite evidence that they don't work, because the perceived cost of change feels too high.

On the shop floor, Document Inertia has a very clear manifestation: it's faster to ask Juan than to look up the procedure. And as long as Juan is there, the system works. The problem is that Juan becomes a single point of failure. And the company doesn't even realize it until Juan isn't there.

McKinsey estimates that employees spend 20% of their workweek searching for internal information or tracking down colleagues who can help.⁷ Out of every five people you hire, one is looking for answers that should already be accessible. In an industrial environment with rotating shifts, distributed plants, and multilingual teams, this inefficiency multiplies.

It's not that companies don't want to change. It's that the current system, fragile as it is, seems to work while the key pieces are in place. Until one of them moves.

From people to infrastructure: the shift your operation needs

The solution isn't more documentation. It's changing how knowledge is captured, structured, and consumed.

This is what we call Knowledge Infrastructure: a system where training and procedures are always current, always traceable, and always consumable. Not a file repository. Not an LMS where documents get uploaded. A living infrastructure that makes knowledge outlast the people who generated it.

In practice, this means three things for an industrial company:

What the fifteen-year technician knows becomes a training module that any new operator can consume without needing that technician to be available. Knowledge decouples from people.
When a procedure, safety protocol, or regulation changes, the content updates without re-recording, reprinting, or redistributing. Updating stops being a project.
It doesn't matter which plant you're at, which shift you're on, or what language you work in. Training is consistent across all locations.

The concrete process to get there has a name: Visual SOP Refactoring. It's not about "turning a PDF into a video." It's about analyzing the structure of the original document, identifying the knowledge blocks, and restructuring them into visual modules optimized for comprehension and retention. The transition to this model is supported by Knowledge Infrastructure solutions (like Vidext), which decouple expert knowledge and transform it into digital assets by analyzing the source document's hierarchy and generating 3-to-7-minute modules without traditional audiovisual production.

According to Deloitte, companies that implement knowledge management systems reduce their operational costs by 23%.⁸ That's not just an efficiency metric. It's the cost of continuing to depend on the right people being in the right place every single day.

If your organization needs to systematize this shift, our guide on how to transform industrial SOPs into structured training is a good starting point.

What this looks like in practice

Thinking about Knowledge Infrastructure can feel abstract. But on an industrial shop floor, it translates into very concrete situations.

Onboarding that doesn't depend on who's on shift. The new operator shows up on Monday and has access to safety modules, line procedures, and quality protocols. They consume them at their own pace, on video, in their language. No one needs to spend hours with them, and the supervisor doesn't need to have a free day.

Updates without production. An ISO standard or health and safety protocol changes. Instead of reprinting the manual and scheduling an in-person session, the module updates and redistributes automatically. Consumption records are tracked for auditing, meeting SCORM or xAPI requirements.

Consistency across plants. A company with four factories in two countries can guarantee that safety training is identical everywhere. No reliance on the local trainer's interpretation, no variation between shifts, no risk of one plant running on an outdated version of a procedure.

Multilingual knowledge from day one. Teams with workers from different nationalities receive the same content, each in their own language. Knowledge Infrastructure platforms solve this with automatic translation into 40+ languages, including regional languages like Catalan, Galician, and Basque.

These aren't hypothetical scenarios. They're the problems that industrial companies solve every day when they move from relying on people to building an infrastructure that works regardless of who's around. If you want to see how to design this transition step by step, our guide for training managers looking to digitalize with AI walks through the entire process.

Conclusion: your operation shouldn't depend on who's in today

The technician who knows how to adjust line 3 won't be there forever. Neither will the supervisor who used to train the new hires. And every time someone with critical knowledge leaves without that knowledge being transferred, your operation becomes a little more fragile.

The question isn't whether it will happen. It's whether, when it does, you'll have an infrastructure that sustains the operation — or a gap that nobody knows how to fill.

Building that infrastructure doesn't require a multi-year transformation project. It requires changing the format in which your team's knowledge is captured and transmitted. And doing it before that knowledge walks out the door.

Request a demo and we'll show you how industrial companies are making this transition with Vidext.

Frequently asked questions

What is tacit knowledge and why is it an operational risk?

Tacit knowledge is everything an employee knows how to do but that isn't documented anywhere: technical tricks, diagnostic criteria, sequences learned through experience. In industrial environments, it represents between 80% and 90% of total operational know-how. When the person who holds it leaves, that knowledge disappears with them.

Why don't manuals and PDFs work for knowledge transfer?

Because static documentation doesn't get consumed. Technical manuals serve a regulatory function, but they don't transfer knowledge effectively. One week after a training session, the average employee has forgotten 65% of the content. If the format requires reading a long document with no visual context or interaction, retention drops even further.

What is Document Inertia?

It's the tendency of organizations to keep using static formats (PDF, PowerPoint, printed manuals) for internal training, despite evidence of low retention. It happens because the perceived cost of change feels higher than the actual cost of continuing with the status quo. In practice, it shows up when asking a colleague is easier than looking up the procedure.

How can an industrial company capture its employees' knowledge?

Through a process called Visual SOP Refactoring: analyzing existing operational documents, identifying the key knowledge blocks, and converting them into visual training modules that any employee can consume. The goal is to turn knowledge that currently lives in people into content that is accessible, updatable, and traceable.

What is Knowledge Infrastructure?

It's a system where training and operational procedures are always current, always traceable, and always consumable — without depending on specific individuals. Unlike an LMS or a document repository, Knowledge Infrastructure keeps content alive: it updates when procedures change, adapts to the user's language, and records who has consumed what for auditing and compliance.