The Target’s Best Engineer May Be the System

The target’s most valuable technical asset may be a person management describes as indispensable.

They know why the architecture differs from the diagram, which customer cannot tolerate an update, how to recover the database and which script must run before billing.

Diligence the knowledge concentration

Ask the engineer to explain failure and change, not the happy path. Compare their account with documentation and other staff.

Value object — The Human System Inventory

- Decisions held in memory.

- Credentials and provider relationships.

- Critical manual actions.

- Systems only they can recover.

- Named successor.

- Transfer evidence and retention need.

Do not solve only with retention

Retention buys time. Pair it with observed handover, independent recovery and removal of personal ownership.

A brilliant engineer can be a competitive advantage. Depending on their continued availability is a liability the model must price.

Where this breaks

Management may believe documentation captures the engineer’s knowledge because diagrams and runbooks exist. The missing asset is judgment about which exception matters under pressure.

The operating move

Observe the engineer handling change and failure. Record decisions, customer constraints and provider relationships, then make a successor perform the work independently.

Capture why, not only how.

Transfer personal accounts.

Exercise unfamiliar failure.

Measure decisions still escalated.

The test

Remove the engineer from one maintenance window. If the team can follow the plan but cannot handle deviation, the human system remains.