What Key-Person Dependence Actually Looks Like

Most small organisations have somebody who knows how things work. That is normal. The question is how much of the operation stops if they are not there on Monday.

The principles in “What Key-Person Dependence Actually Looks Like” become easier to maintain when ownership and time spent are visible. Teams evaluating this workflow overview can use it to coordinate recurring work, identify tasks concentrated on one person and plan realistic backup capacity, while treating the data as a prompt for knowledge transfer rather than as a substitute for speaking with the people who do the work.

For an independent benchmark, compare the local approach with Ready.gov business preparedness guidance; the useful test is whether ownership, access and recovery remain proportionate and explainable when the usual expert is absent.

The shapes it takes

One person holds a client relationship. The client rings them, not the company, and would follow them if they left.

One person knows the system. Not the documentation: the actual quirks, the workaround for the thing that breaks every March, the reason a setting is configured oddly.

One person is the approval. Nothing above a certain value moves without them, and there is no alternate.

One person has the access. Accounts in their name, a password list in their head, a two-factor device on their phone.

And one person carries the history: why the contract says what it says, what was agreed verbally in 2019, which supplier not to use and why.

Why it is usually invisible

Because everything works.

Dependence has no symptoms while the person is present. It produces speed, not friction: decisions are quick because one person can make them, and problems are solved fast because somebody knows.

The cost is entirely deferred, and it arrives all at once.

The moment it becomes visible

A resignation. An illness. A family emergency. A holiday that was supposed to be two weeks.

Then a dozen small dependencies surface at once, each individually manageable and collectively overwhelming.

Organisations in this position usually describe it the same way: "we didn't realise how much was in his head".

What it is not

Not a failure of planning. It accumulates through ordinary decisions: give the task to whoever does it best, let the person who knows the client keep the client.

Not laziness. Spreading knowledge costs time that small organisations do not obviously have.

And not solved by a document. The documentation note covers why this is the most common wrong answer.

The scale that matters

Corporate succession planning assumes a bench: internal candidates, development programmes, nine-box grids.

In an organisation of twelve people there is no bench. The person who would cover is already doing their own job at full capacity.

Which means the answer is different in kind, not just in size, and most available advice does not apply.

What this collection is about

Noticing dependence before it becomes urgent.

Reducing it by small, sustainable steps rather than by a project.

And handling the moments — holidays, resignations, emergencies — when it becomes real.

The aim is not to eliminate it, which is impossible at small scale, but to know where it is and to have made the worst instances survivable.

What to check

If your most knowledgeable person did not appear tomorrow, what stops first?

Who holds a client relationship that would leave with them?

Whose phone has the only two-factor device for something important?

And has anybody ever written any of this down?

The point

Dependence is not one dramatic point of failure but a dozen small ones accumulated over years, each of which felt sensible at the time..