Keep a company's judgement when senior people leave by recording its decisions and the reasons behind them
A company keeps its judgement when senior people leave by recording how they decide while they are still there: the decisions they made, the reasons, the standards they applied and the exceptions they allowed. Handover documents capture tasks and contacts, and they rarely capture why the person said no to the plan everyone else liked. Held in a structured record that people and AI systems can both read, that judgement stays with the business.
Most advice on knowledge loss is about documentation and handover checklists. Documents record what was done; the costly loss is the reasoning behind decisions, which almost no handover process captures.
When a senior person leaves, the handover usually goes well on paper. Their tasks are listed, their contacts are introduced and their files are moved. Six months later the business makes a decision they would have stopped, and nobody can say why it feels wrong until it has already gone wrong.
What left was their judgement: how they decided, not what they did.
Why handover documents miss it
Handover documents answer the question "what does this person do?" They are written at the end, often in a hurry, by someone who is already thinking about their next role. They list responsibilities, open work and useful contacts.
They rarely answer "how does this person decide?" That knowledge is hard to write on demand. It lives in reactions: the pricing request they always refused, the supplier they never trusted, the kind of hire that looked good and failed. Asked directly, most experts struggle to list it. Shown a real decision, they know immediately.
Record decisions as they happen
The practical fix is to record decisions as they happen, with their reasons, while the person is still making them. Each entry needs four things: the situation, what was decided, why, and what would have changed the answer.
Over a few months, patterns appear. The same standard shows up in five different decisions. An exception gets made twice for the same reason. That is judgement becoming visible, and it can now be taught.
Make it usable by people and AI
A record like this is useful to a new hire, who can read how similar calls were made before. It is also useful to an AI system, which can draw on the record when drafting a recommendation and name the past decision it relied on.
That second use matters more each year. Teams increasingly start their work with AI. If the AI starts from the public average, the business gets average work. If it starts from the business's own record of judgement, the departed expert's reasoning is still part of every draft.
Keep it owned by the business
The record should sit in the business's own accounts, readable by people and exportable. If it lives inside a vendor's system, the business ends up renting back its own memory.
Start with one person and one recurring decision. Record the next five times it is made and the reasons behind each one. That small record is worth more at their leaving party than any handover document.
Where we stand on this
- Mindmake builds records of how a leader decides, held in the business's own accounts, so the judgement stays when people move on.
- The most expensive thing a senior person takes with them is the reason they said no.
- A decision recorded with its reason can be reused, checked and corrected. A decision recorded without it can only be copied.
The questions that follow
Is this the same as a knowledge base?
A knowledge base stores documents and answers to known questions. A record of judgement stores decisions and the reasoning behind them, so it can help with questions nobody has asked yet.
When should a business start?
Well before anyone hands in their notice. The best time is while the person is still making decisions every week, because the reasons are fresh and they can correct the record themselves.
Does the person have to write it all down?
No. Most of it can be drawn from what already exists, such as emails, board papers and meeting notes, then checked by the person in a short review. Their time goes into correcting, which is quicker than writing.