We Have One Person Who Knows How Everything Works

"We have one person who knows how everything works."

This is almost always said with affection. Sometimes with pride. Occasionally, in the week after that person resigns, with something closer to panic.

The sentence describes a single point of failure that no business continuity plan covers, because it is not a server. It is a colleague. The process lives in their head, their inbox, and their memory of which supplier needs a phone call rather than an email.

What people say when you ask

This is one of the most-discussed problems on professional forums, and the consensus is brutal.

In r/sysadmin, a thread titled "Good or bad: Being a Single Point of Failure (SPoF)?" dismantles the idea that indispensability is job security. The knowledge that only one person holds is a liability for the business and a trap for the person holding it.

r/smallbusiness has a thread called "What's the biggest single point of failure in your business?" where the top answer is about the owner becoming the only person who knows where everything is — and how the fix is rarely about hiring.

And in r/ITSupport, a post titled "My best tech just quit and now I'm realizing he was the entire support..." captures the aftermath in the title itself. The realisation arrives after the departure, which is the worst possible time.

Across all of them: the risk is understood, acknowledged — and left in place, because writing it down never becomes urgent until it is too late.

Why it keeps happening

The knowledge was never written down because writing it down is a project, and the work never stops long enough for one.

The person who knows everything is also the fastest person to ask, which means they are interrupted all day, which means they never have time to document what they know. Every question they answer reinforces the dependency. It is a self-tightening loop.

Documentation attempts fail for a second reason: a process document is static, and the work is not. The document describes the normal case. The value this person carries is the exception case — the judgment, the relationship, the workaround that has to be applied differently each time.

What it costs

• Every holiday, sick day and resignation is a risk event.
• The business slows down whenever that person is at capacity.
• Growth is capped by one person's attention.
• The person themselves burns out carrying a process that should belong to the operation.

What LevelOneAI does about it

We do not try to write down everything that person knows. We move the state out of their head and into the work.

When each order, job or request has a work item that holds its own context — the history, the documents, the correspondence, what is missing, what is next — the process stops being something a person remembers and becomes something the work carries. A new colleague can pick up the queue and see what matters, because the queue holds what used to be in someone's memory.

Their judgment stays theirs. That is the point: we take on the gathering, the comparing, the chasing and the recording — the mechanics — so that the expertise is spent on decisions rather than on retrieval.

The test

Ask the person who knows everything what they would need to hand over if they were away for three weeks. The list they give you is the specification for the work queue. That is where we start.