Where does experience go?
Businesses spend a lot of money acquiring knowledge.
They buy software, hire consultants, send people on courses, subscribe to databases and commission research. They record procedures, build knowledge bases and create training programs.
Then they let some of their most valuable knowledge walk out the door.
An experienced employee retires. Someone who has been there for twenty years accepts redundancy. A manager decides they have had enough. Sometimes the person stays, but gradually gets pushed towards the edge as younger people, new technology and new ways of working take over.
When years of accumulated judgement exist only in one person’s head, you have an operating risk. The employee may be valuable, but management has allowed part of the business’s capability to depend on that person remaining available.
Their files will remain. Their judgement disappears with them.
What experienced people know
After years in a business, you know things nobody wrote down.
You know which customer says they need delivery on Friday but will accept Monday if somebody calls them first. You know which supplier’s quote is usually cheapest and which supplier will get you out of trouble late in the week.
You know that a particular machine starts making a different noise a week before something fails. You know the monthly report showing a problem isn’t quite as alarming as it looks because you’ve seen the same pattern before.
You know which problems deserve attention.
That distinction takes years to acquire.
An inexperienced manager sees twenty things going wrong and concludes that all twenty need fixing. Someone who has seen the business through several cycles recognises that seventeen are noise, two need watching and one needs dealing with before lunch.
None of that appears in an SOP.
Businesses are poor at valuing judgement
This creates an accounting problem.
A business puts a value on its buildings, equipment, inventory and accounts receivable. It tells you what a machine tool bought six years ago is worth today.
There’s no corresponding line for the accumulated judgement of the people who spent twenty years learning how the place actually works.
You discover the value when enough of that judgement disappears.
Problems take longer to diagnose. Mistakes get repeated. Relationships lose their history. People spend hours investigating questions somebody else could have answered in five minutes. Decisions that once involved a quick conversation become meetings because nobody is sufficiently confident to make the call.
Data without accumulated context leaves people knowing what happened while still struggling to decide what it means.
Ageism has an operating cost
Ageism can destroy operating knowledge long before management notices the cost.
When you assume somebody’s value declines because their technical knowledge is dated, you discard the wrong asset.
Technical knowledge dates. The person who mastered a software package fifteen years ago often knows less about its replacement than someone who started six months ago.
Judgement behaves differently.
The experienced operator needs help with the new system, but knows straight away that the number appearing on the console is wrong.
The older salesperson is slower with the CRM, but knows the prospect everybody’s excited about has all the characteristics of a timewaster.
You can teach someone where to click quickly. Teaching them what deserves attention takes longer.
A business that confuses technical currency with commercial usefulness ends up discarding people who understand why things happen while retaining systems that merely record what happened.
Why documentation misses judgement
You should document everything.
Procedures, decisions, customer history, exceptions, failures and lessons should live somewhere other than human memory. Modern searchable text systems make this far more useful than the filing cabinets and paper manuals businesses once relied upon.
Documentation has a limit.
You can document that a customer received unusual payment terms three years ago. The experienced account manager remembers why and whether the circumstances still apply. The record tells you what happened. Judgement tells you what the record means now.
So the job is larger than getting an experienced employee to write down what they know before their retirement lunch.
You need to expose how they think.
Ask them about exceptions. Ask which customers worry them despite looking good in the system. Ask what early signs precede the failures everybody else notices later. Ask which rules they occasionally break and why. Ask what a competent newcomer is most likely to misunderstand.
Ask them what they know that nobody ever asks them about.
That last question produces uncomfortable answers.
How to preserve institutional knowledge
Businesses talk endlessly about succession for senior executives and surprisingly little about succession for accumulated judgement.
Yet the person whose departure hurts you often never appeared important on an organisation chart.
It could be the estimator who remembers why certain jobs always blow their budgets. The administrator who knows the history behind your difficult accounts. The technician who can diagnose a problem from three apparently unrelated symptoms. The salesperson who remembers the prospects everyone else has forgotten.
By the time you discover how much they knew, they are gone.
Look around your business and ask: ‘what disappears when this person leaves?’
If the answer includes knowledge, relationships, pattern recognition or judgement that exists nowhere else, you have found an asset you are failing to manage.
Capture the examples, exceptions and reasoning while they are still available. Put experienced people alongside the people who will inherit their work. Record how they diagnose unusual situations, which signals they trust and which apparent problems they ignore. Build that judgement into training, operating systems and decision processes.
If essential judgement can disappear because one person resigns tomorrow, you have already found a weakness in the system.