The invisible dependency: what happens when an industrial company depends too much on “the usual people”

In many industrial companies, there is a figure who seems indispensable. Sometimes it is the production manager. Other times, a maintenance technician, someone from administration or a person who has been in the company for decades and “knows everything”. They know the machines, remember incidents from years ago, know which client prefers each procedure and solve problems almost by intuition.

And normally, while that person is still there, everything works.

The problem appears when a company discovers that a large part of its operations depends too heavily on knowledge that has never been documented, structured or shared. And this situation, although it often goes unnoticed for years, represents one of the quietest risks within the industrial environment.

When knowledge exists only in someone’s head

Many industrial companies have grown relying on the accumulated experience of certain key people. It makes sense. Industry highly values practical knowledge, real experience and the ability to solve problems on the ground.

The inconvenience appears when that knowledge stops belonging to the organisation and becomes dependent exclusively on specific individuals.

“Ask him, he always handles that.”

“She’s the only one who knows how that client works.”

“If something happens with that line, better wait until he arrives.”

These are common phrases. So common, in fact, that they often stop being perceived as warning signs.

Because while those people are available, dependency looks like efficiency. But in reality, it is often operational fragility disguised as normality.

The false security of “it has always been this way”

One of the reasons why this problem is so difficult to detect is precisely because it usually does not generate immediate incidents. The company keeps producing, customers keep receiving orders and processes continue to function.

From the outside, everything seems stable.

However, many times that stability depends on very fragile balances: people solving incidents outside procedures, decisions made “because it has always been done this way” or processes that nobody else fully understands.

The sense of control can be misleading when the system depends too much on memory, individual experience or the improvisation of certain people.

And the longer this situation goes without being reviewed, the harder it becomes to correct.

The problem does not appear when someone leaves. It starts much earlier.

There is an idea that this type of dependency only becomes a problem when someone retires, changes company or leaves. But the reality is that the consequences usually begin earlier.

It happens when delegation becomes complicated.

When certain decisions are blocked because “only one person can validate them”.

When teams stop documenting because they know there will always be someone who remembers how to do it.

Or when company growth starts demanding a more organised structure while knowledge continues functioning in a completely informal way.

At that moment, dependency stops being only a human risk and starts directly affecting operational efficiency.

The real difficulty of transferring experience

In industry, not all knowledge can be summarised in a manual. Some decisions come from experience, from years observing processes, machines or specific behaviours.

And precisely because of that, transferring that knowledge requires time, planning and a genuine willingness to share it.

The problem is that many companies postpone this task because day-to-day operations always seem more urgent.

“We don’t have time now.”

“We’ll explain it later.”

“As long as it works, better not touch it.”

But when the moment comes to transfer that knowledge quickly —due to an unexpected retirement, a sudden departure or accelerated growth— it is often too late to do it properly.

Because technical knowledge is not transmitted only through documents. It also needs support, context and time.

Dependency also wears out the person carrying it

Another aspect rarely discussed is the impact this situation has on the key people themselves.

When someone becomes indispensable, they usually end up accumulating constant pressure. Everything goes through that person. Everything requires their validation. Everything depends on them being available.

In the short term, it may even feel like recognition. But in the long term, it often generates exhaustion, burnout and difficulty truly disconnecting from work.

Furthermore, the company enters into a dangerous dynamic: protecting those people without building real alternatives.

And the more indispensable someone seems, the harder it becomes to reorganise processes around that dependency.

Growing requires depending less on specific people

Many industrial companies discover this problem precisely when they try to grow.

While the structure is small, informal communication can work relatively well. But when teams, projects or operational complexity increase, depending on “the usual people” stops being sustainable.

Growth forces companies to structure processes, define responsibilities and share knowledge in a more organised way.

Not because experience stops being important, but because the company needs knowledge to remain within the organisation regardless of who occupies each position.

In this sense, professionalising does not mean losing closeness or practical experience. It means reducing unnecessary risks.

Documenting is not bureaucracy

In some industrial environments, documenting processes is still perceived as something excessively administrative or not very useful compared to real experience.

However, documenting does not mean filling folders with procedures that nobody reads. It means ensuring operational continuity.

What is done.

How it is done.

Why it is done that way.

What risks exist.

Which decisions require validation.

When this information does not exist or depends only on informal conversations, the company loses adaptability and reaction capacity.

And in an increasingly demanding industrial environment, depending exclusively on unstructured knowledge can become a significant limitation.

Company culture also matters

Not all companies manage this situation in the same way. In some organisations, there is a culture strongly based on “controlling” information. Sharing knowledge is perceived almost as losing value within the company.

In others, the exact opposite happens: collaboration, cross-training and the progressive transfer of experience are encouraged.

The difference between both approaches usually becomes visible when an important change occurs. Companies that have worked on knowledge continuity usually adapt much better to departures, growth or internal reorganisations.

Because stability does not only depend on having highly capable people. It also depends on the organisation being able to absorb changes without collapsing.

Detecting the problem before it becomes urgent

As happens with many risks in industry, this issue rarely generates alarm until there is already a direct consequence.

A retirement.

An unexpected leave.

Growth that disrupts processes.

An incident that nobody knows how to solve without one specific person.

That is why perhaps the important question is not whether dependency on key profiles exists —because to some extent it always will— but how much the company truly depends on knowledge that has still not been shared.

An open conversation

Experience remains one of the most valuable assets within any industrial company. The problem is not depending on experienced people. The problem is building structures where everything depends exclusively on them.

Because when knowledge is not shared, the company does not gain stability: it gains vulnerability.

👉 In your company, are there processes or decisions that still depend too heavily on specific people?
👉 Is knowledge really being shared, or is there still too much reliance on “the usual people”?

As often happens in industry, the problem rarely appears suddenly. It has simply been growing silently for years.