Make Expertise Transferable

A colleague knows how a difficult part of the system works. When it fails, they recognize the symptom. When a change is proposed, they know which assumption matters. The team benefits from their expertise and gradually routes more work through them.

That arrangement can become uncomfortable for everyone. The expert is repeatedly interrupted. Other people hesitate to act. An ordinary holiday needs a coverage plan built around one person’s memory. Asking the expert to “document everything” sounds reasonable until someone considers what everything would include.

Start with a real task that another person should be able to complete. Transfer enough knowledge to make that task possible, then widen the scope as the work requires.

First, choose a capability someone can demonstrate

“Understand the billing system” is too broad to verify. “Diagnose why a valid order did not reach billing” gives the learning a purpose. So does “make a small rule change and demonstrate that existing cases still work.”

Choose something consequential enough to matter and bounded enough to attempt safely. Agree on the access, observation, and recovery arrangements before using production behavior as teaching material. A learning exercise should not quietly expand someone’s operational authority.

The expert can first demonstrate the task while explaining their reasoning. Ask them to make the invisible decisions audible: why they looked at one signal, why they dismissed another possibility, and which condition would make them stop. Record the useful references and decision points without trying to capture every spoken word.

Then let the learner lead

On the next suitable occasion, let the learner lead while the expert observes. This changes what becomes visible. A document may appear complete to its author because they supply missing context automatically. Someone following it will discover the unexplained identifier, the inaccessible dashboard, or the step that depends on knowing who to contact.

Allow the learner to reason before supplying the answer. Intervene when an agreed boundary is approached, then explain the boundary. Constant correction can produce a successful task without producing independent judgment.

Afterward, ask the learner to explain what happened and why. They should be able to distinguish the important evidence from incidental details. If the explanation depends on copying a sequence without understanding its conditions, the team still has a fragile procedure.

The useful artifact might be a short runbook, a test that exposes the rule, a diagram of one dependency, or a decision record explaining a constraint. Choose the form that supports the task. A long document is not automatically a better transfer.

Include what the task is for, when the instructions apply, required access, expected observations, and stopping conditions. Link to maintained sources where possible. If the record contains a temporary workaround, say how someone will recognize that it is no longer needed.

Give the artifact a home near the work and an owner who can keep it useful. Knowledge spread across personal notes and forgotten chat threads may still require the original expert to retrieve it.

Finally, look for independent judgment

Completion of a training session is weak evidence that someone can act independently. A more useful check is whether they can handle a later comparable task, explain the result, and recognize when the situation exceeds their knowledge.

Independence includes knowing when to seek help. Nobody needs to pretend they can resolve every failure. The goal is to reduce unnecessary dependence while keeping consequential uncertainty visible.

Protect time for this work. An expert who is rewarded only for personally finishing urgent tasks has little room to make those tasks transferable. Include the transfer in the definition of the contribution, and acknowledge the person doing the learning as well as the person teaching.

Choose one recurring request that currently reaches the same colleague. Pair on the next instance, let someone else lead the one after that, and keep the record they actually need. Then observe whether the request can reach a dependable conclusion without the original expert carrying it again.