Documenting the informal know-how that long-tenured employees hold, so the company stops depending on a few people and the work no longer runs through their personal knowledge.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
At a regional bank, three senior underwriters approved nearly all commercial real estate loans over $5 million. Their judgment was good, none of it was written down, and two of them were within four years of retirement. The new chief credit officer started a project to codify their approach: a scoring template, written rules for rent rolls and tenant concentration, and a library of forty past decisions with the reasoning behind each. She told the three plainly that the point was to reduce the bank's reliance on them, and offered each a retention bonus tied to finishing the work and training two junior analysts. One refused and left within the year. The other two finished. Eighteen months later the junior analysts were approving mid-size loans with the template, at loss rates matching the old ones.
Why it works
Once informal expertise is mapped and absorbed into a process, the incumbent's unique value (the reason colleagues had to come to them and managers could not let them go) shrinks, so keeping the knowledge private is worth less. Resisting documentation also becomes costly, since it starts to read as hoarding, key-person risk, or poor audit readiness. It depends on real discipline in doing the codification, with dedicated roles and tools, and on junior staff who gain from the documented system and become its constituency. It fails when the knowledge is irreducible craft judgment or the incumbents can leave and take it with them.
The thinking behind it
Oliver E. Williamson Oliver Williamson's The Economic Institutions of Capitalism (1985) describes asset specificity: knowledge specialized to one firm's systems or customers loses value outside it, and once such investments are made the parties depend on each other. Underwriters whose judgment exists only in their heads hold a specific asset that gives them bargaining power. Codifying it reduces the bank's dependence, and paying for it recognizes the value being transferred.
George A. Akerlof George Akerlof's The Market for "Lemons": Quality Uncertainty and the Market Mechanism (1970) showed how the side that knows quality can shape what the other side receives. Incumbents asked to document their knowledge know which parts are load-bearing and the company does not. That is why selective compliance is the main failure mode, and why testing whether the system runs without the incumbent is the only reliable check.
When it fits
Codify when the company depends on a few people for work it cannot afford to lose, the knowledge can be at least partly written down, and you have authority over process and staffing. It needs budget for the work, juniors who will use the result, and either money for the incumbents or a plan for working without them.
How to use it well
Treat the project as a purchase of knowledge.
- Say what the project is for. Incumbents will read the shift in power accurately anyway, and candor costs less than discovered spin.
- Pay for the knowledge: retention bonuses, consulting arrangements after retirement, credit as authors, a role training the next people.
- Dedicate people and tools to the work; codification done in spare time captures the obvious steps and misses the judgment.
- Build the junior constituency early by pairing juniors with incumbents on real cases.
- Before relying on the system, test whether it runs without the incumbent.
Expect selective compliance. The obvious gets documented first and the load-bearing nuance last, if ever.
What it costs and where it backfires
Incumbents may resent it, comply selectively, or leave early, sometimes taking the judgment that mattered most. Some craft judgment can only be approximated on paper, and a system built on the approximation can fail in ways nobody sees until losses appear. A push that stalls halfway leaves resentful incumbents and no system. Honesty and fair dealing are the limit. Telling people documentation is for their benefit while planning to push them out once it's done is deception, and the rest of the company will learn from how they were treated.
When it is used on you
A documentation mandate aimed at exactly the workflows you control, with resistance described as hoarding or key-person risk, is the sign. Negotiate: codifying your knowledge transfers value, and the company can pay for it in money, a role, or credit. Outside options strengthen your hand. Then document fully and well, so the result carries your name.