One expert is the only person who understands a critical component. What should we do?

Single-person dependency

Reduce the dependency through shared work, usable documentation, and demonstrated backup capability. Do not assume that asking the expert to write a document creates real resilience.

What to do now

Identify the critical knowledge and tasks
Pair another person on real work
Document operationally useful procedures
Test whether the backup can perform independently

Recommended action flow for single-person dependency: Identify the critical knowledge and tasks then Pair another person on real work then Document operationally useful procedures then Test whether the backup can perform independently. Escalate when the expert's unavailability would stop a critical service or milestone.

When to escalate

Escalate when

The expert's unavailability would stop a critical service or milestone.

Who decides

The team lead and appropriate line manager

Example

A second engineer performs a supervised deployment and then repeats it independently.

Mistake to avoid

Adding knowledge-transfer work without freeing any capacity.

Prevent a repeat

Review whether working agreements improve delivery and raise people concerns through the appropriate channels.

Suggested ApprovedFlow setup

Tasks
Resources
Documents

Make agreed responsibilities and follow-up tasks visible while keeping sensitive people matters in the authorized confidential process. See the platform