Capital Mispricing and Structural Risk

Chapter 7: Talent Decay as Structural Fragility

The departure of context-rich engineers is not a retention problem but a structural failure. The organisation systematically selects against people who speak in mechanisms and failure modes, rewarding those who speak in roadmaps and strategic narrative. Each departure permanently destroys knowledge that was never captured in any artefact.

A principal engineer at a European insurer with approximately five hundred services and a claims management platform that has been accumulating complexity for fifteen years raises a concern about a dependency that will block the roadmap. When the concern is noted but not addressed, she escalates by flagging a risk in an architecture review. After that risk is acknowledged but deprioritised, she points out that a commitment made to the board cannot be delivered as described, only to be told to find a way.

After enough of these exchanges, she stops, not because she has lost the knowledge, but because the cost of stating what she sees has become higher than the cost of staying silent. Although she still sees the problems clearly, traces the dependencies in her head, and knows exactly which parts of the system are fragile, she stops writing the emails that would have prevented the next incident. This silence is not apathy; it is the rational response to an incentive structure that consistently penalises accuracy.

When she leaves two years later, the knowledge transfer takes zero time because no mechanism exists for it. She takes with her a deep understanding of the claims adjudication process, the policy integration constraints, the payment reconciliation edge cases, and the failure modes of the document management service, none of which is captured in any document within the organisation. Her replacement arrives with equivalent credentials and no context. He spends six months learning what she carried as working knowledge. Some of what she knew, he never learns, because it was never written down.

Eight months after she leaves, a payment reconciliation job runs at 3 a.m. and produces twelve hundred incorrect records. Her replacement traces the failure to a caching behaviour in the document management service that manifests only under specific load conditions. He does not know that she encountered this exact failure twice, identified the root cause, and fixed it both times in under an hour. The warning she wrote in a draft document, and later deleted after no one responded to the first incident, is no longer available to him. He pages two colleagues. The incident runs until 6 a.m. The same failure recurs six weeks later.

The third recurrence produces 214 incorrect records already included in a quarterly regulatory filing. The correction requires a formal amendment. The explanation offered: “a technical error in the reconciliation batch process.” The actual cause, that the organisation lost the only person who understood the failure mode and never captured what she knew, is not something the filing format accommodates. The regulator notes the correction without penalty. The regulatory file now contains a record: an organisation that could not explain its own payment process.

The organisation describes this as a retention problem; it is a structural failure: the environment systematically selected against the transmission of accurate system context. There is a further cost: the systematic destruction of the knowledge that makes the organisation legible to itself.

...

See also: Full contents · Preview chapters · Illusions of Work