Why It Feels Like Reliability

Dependence does not look like risk from the inside. It looks like somebody dependable, and that perception is the main obstacle to addressing it.

The principles in “Why It Feels Like Reliability” become easier to maintain when ownership and time spent are visible. Teams evaluating the product 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.

How it builds

Somebody handles a difficult thing well, so they get the next difficult thing.

They become faster at it than anybody else, which makes giving it to somebody else feel wasteful.

They start being asked directly, bypassing whatever process existed.

And over three years they accumulate a portfolio of things only they do, each of which arrived for a good reason.

The feeling it produces

Relief. Somebody has it covered.

Trust, which is earned and genuine.

And a specific kind of comfort: not having to think about that area at all, which is valuable in a small organisation where attention is the scarcest resource.

None of those feelings is wrong. They are just not evidence that the arrangement is sound.

Why raising it is awkward

Saying "we are too dependent on you" sounds like criticism, or like a prelude to reducing somebody's role.

The person hearing it frequently takes it as a lack of confidence, which is the opposite of what is meant.

And they may resist for reasons covered in its own note: their position is partly built on being indispensable.

Framing matters: this is about what happens when you are unavailable, not about whether you are doing well.

The two-sided risk

For the organisation: an operational gap that arrives without warning.

For the person: no holidays without their phone on, no illness without guilt, no promotion because nobody can replace them in their current role.

That second list is the argument that actually persuades people. Dependence traps the person as much as it exposes the organisation, and most people in that position recognise the description immediately.

The founder version

Most acute where the dependent person owns the business.

They cannot be told they are a risk, they set the priorities, and the thing that would reduce the dependence — delegating — is the thing they are worst at.

Its own note covers the owner who cannot take a holiday, which is the diagnostic symptom.

What changes the conversation

Asking what would need to be true for them to take three weeks off without contact.

Not as a rhetorical device: actually work through it.

The list that comes out of that conversation is your dependence map, produced without anybody having to be told they are a problem.

What to check

Who in your organisation has not taken a full week off without contact in the last year?

Have you ever raised dependence with them, and how did it land?

Is the person aware of how much sits with them?

And what would they say if asked what happens when they are away?

The point

Dependence traps the person as much as it exposes the organisation.

No holiday without the phone on, no illness without guilt, no promotion because nobody can replace them.

Underlying all of this

Everything in this collection reduces to four habits: know where the dependence sits, do the cheap fixes first, use the absences that already happen as rehearsals, and decide deliberately about what remains. None of it requires a framework, a tool or a consultant, and an organisation that does those four things consistently is substantially harder to damage than one with a succession document nobody has read.