Signs Your Manufacturing Operation Depends on One Person

There's someone in your operation who holds it all together. You might not realise how much they carry until they're on holiday for two weeks and things start to wobble.

They know which customers need managing before they escalate. They know which suppliers to chase on a Thursday because the delivery won't arrive on Monday otherwise. They know that the system says one thing but the reality is something else, and they quietly bridge the gap every single day without logging it, reporting it, or complaining about it.

Everyone knows who this person is. Nobody talks about what would happen without them.

The Signs

Key person dependency doesn't announce itself. It builds slowly. Here's what it looks like when it's already embedded:

People go to the same person for answers, regardless of the org chart. When that person is off, the same questions get asked to three different people and nobody gets the same answer. There's a spreadsheet or a notebook that only one person maintains and only one person understands. Process documentation exists but it's out of date, and people follow the person not the process. New starters are told "just ask Sarah" instead of being given a procedure.

None of this is a failure of the person. It's usually the opposite. They're carrying the weight because they're good at it. The system has learned to route around its own weaknesses by using the strongest person available.

That works fine. Until it doesn't.

Why It's a Structural Problem

Most businesses treat key person dependency as a people risk. Succession planning. Cross-training. Knowledge transfer workshops. All reasonable things to do.

But they miss the point. The reason that person carries so much isn't because they hoarded knowledge or refused to share it. It's because the system around them never provided an alternative. Information wasn't documented because there was no system for documenting it. Processes weren't standardised because nobody made the time to standardise them. Decisions weren't formalised because it was quicker to just ask the person who knew.

The dependency is a symptom of structural weakness. The missing documentation, the informal workarounds, the undeclared processes that live in someone's head. That's where the real risk sits.

Cross-training doesn't fix it. You can train three people to do what one person does. But if the process they're learning is an informal workaround that exists because the formal process doesn't work, you've just spread the compensation wider. You haven't removed it.

What to Do About It

Start by making it visible. Ask one question: if this person didn't come in tomorrow, what would actually break? Not what would be inconvenient. What would stop working?

Then look at why. What information lives in their head that should be in a system? What decisions do they make that should be part of a defined process? What workarounds have they built that the business now depends on?

That's not a training exercise. It's a structural assessment. It tells you where the operation has drifted from its declared design into something that only works because someone is carrying it.

Fix the structure and the dependency reduces naturally. Not because the person becomes less important, but because the system stops needing a hero.

The Process Stability Assessment is designed to expose exactly this kind of hidden dependency. Not to blame the person carrying it, but to identify the structural gaps that created it. If this sounds like your operation, the diagnostic brief explains the approach: processpathwaystrategies.com/diagnostic-brief