Every company has an undocumented API named Bob.
Bob might work in operations.
Or finance.
Or customer service.
Or purchasing.
Nobody is entirely sure what Bob actually does.
What is clear is that if Bob goes on holiday for two weeks, the business enters what can only be described as a controlled systems failure.
Orders stop moving.
Reports stop updating.
Customers stop getting answers.
Three spreadsheets become inaccessible because only Bob knows where they are.
And suddenly everyone discovers that “the process” was actually just a person holding the organisation together with experience, memory, and increasingly concerning levels of patience.
The strange thing is this situation is incredibly common.
Not because businesses are careless.
But because humans are excellent at building invisible systems.
Most operational gaps do not begin with bad intentions.
They begin with somebody helpful.
A process is awkward.
A system cannot quite do what is needed.
A report takes too long.
An approval chain is clunky.
So somebody creates a workaround.
At first, it is temporary:
And to be fair, these things often work brilliantly.
The problem is not the workaround itself.
The problem is what happens next.
The workaround survives.
Then it grows.
Then people start depending on it.
Then nobody documents it because it still feels temporary.
Then eventually the workaround becomes more operationally important than the original system it was designed to support.
At that point, the business has quietly created human middleware.
In many organisations, the most important operational component is not:
It is the person translating between them.
The person who:
These people become operational translators.
And because they are competent, the business often mistakes resilience for stability.
Things appear to work.
Until they do not.
There is a dangerous moment in many businesses where undocumented knowledge stops being convenient and starts becoming infrastructure.
Usually nobody notices when this happens.
Because the business adapts around the person.
People stop asking why the process works.
They just learn who to ask.
That creates a hidden dependency graph:
“Ask Sarah for stock figures.”
“Mark handles supplier corrections.”
“Jenny knows how the invoicing export works.”
“Bob updates the master sheet.”
The organisation starts routing operational logic through individuals instead of systems.
This works surprisingly well right up until:
Then suddenly the company discovers that institutional knowledge was never institutional.
It was personal.
This is where automation conversations often go wrong.
The objective is not to “replace people.”
Good businesses are built around experienced people.
The objective is to remove fragile dependency.
There is a huge difference.
A healthy operational system should mean:
That does not reduce the importance of skilled people.
It actually increases their value.
Because instead of acting as human glue holding broken processes together, they can focus on improvement, judgement, and strategy.
You probably have hidden human middleware if:
None of these are unusual.
But collectively they tell a story.
The organisation has started compensating for process gaps with people instead of systems.
The good news is most of these problems are solvable without massive transformation projects.
Usually the biggest gains come from relatively small changes:
Operational maturity is often less about technology and more about visibility.
You cannot improve systems you cannot see.
If your business would struggle because one person took two weeks off, that person is not the problem.
They are the symptom.
And in many cases, they are the only reason the business works as well as it currently does.
The real issue is that the organisation accidentally turned helpful people into critical infrastructure.
That works for a while.
Until Bob goes on holiday.
Technology evolves at breathtaking speed, but the people using it remain gloriously, frustratingly human. The real challenge of innovation has never been technology — it's trust.
Read →Curiosity rarely disappears overnight. More often, it fades quietly beneath routine, certainty, and the comforting belief that we've seen it all before.
Read →Most splinter spreadsheets do not begin with bad intentions. They begin with urgency. Over time, unofficial tracking files quietly fracture operational truth across the business.
Read →