When the Expert Resists

You suggest pairing and it does not happen. Meetings get postponed, documentation stays unwritten, the client meeting somehow only involves one person. This is common and it has causes.

The principles in “When the Expert Resists” become easier to maintain when ownership and time spent are visible. Teams evaluating this detailed page 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 WHO guidance on mental health at work; the useful test is whether ownership, access and recovery remain proportionate and explainable when the usual expert is absent.

The reasons, usually unstated

Job security. Being the only person who can do something feels like protection, particularly in a small organisation with no other guarantees.

Status. Expertise is what their standing rests on, and sharing it feels like giving it away.

Time. Teaching is slower than doing and their workload has not reduced.

Standards. They believe nobody else will do it properly, which is sometimes correct.

And having been burned: somebody was trained, then left, and the effort was wasted.

Why pressure does not work

None of those reasons is addressed by being told to share.

Compliance without agreement produces the appearance of transfer: a document that omits the important parts, a pairing session where nothing is explained.

And the resistance goes underground, which is harder to see than an honest refusal.

Addressing security

Say plainly that spreading knowledge is not a prelude to removing them.

Then act consistently with that, because words alone will not carry it.

And point at what it buys them: a holiday without the phone, the possibility of promotion, not being rung during a family emergency.

That last argument is the one that most often works.

Addressing status

Make the teaching itself the recognised contribution.

Somebody who trained two people should be described as having done that, in whatever your organisation uses for recognition.

Expertise transferred is a different kind of standing and it can be made visible.

Addressing time

Take something off them, genuinely.

Asking somebody at full capacity to add teaching is asking for it not to happen.

This is the reason most often given and most often ignored.

Addressing standards

Sometimes they are right, and the answer is supervision rather than transfer: the learner does it, the expert checks.

Which preserves quality and still builds coverage.

And where they are wrong, a learner doing it once under observation settles it faster than argument.

When it is deliberate leverage

A small number of people hold knowledge as bargaining power, consciously.

That is a different problem and it is a management one rather than a knowledge one.

Recognise it, address it directly, and understand that the dependency is now also a relationship risk — somebody who uses this as leverage will use it at the worst moment.

What to check

Where has spreading been agreed and not happened?

Have you asked why, and got a real answer?

Has anything been taken off the person expected to teach?

And is teaching recognised anywhere in how you assess people?

The point

Resistance to sharing is usually rational: security, status, time, standards, or having been burned.

Pressure addresses none of 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.