Retiring-Expert Knowledge Transfer
When the only person who can run it is retiring
One person knows how your operation really runs: the schedule, the exceptions, why the spreadsheet has that hidden column. We rebuild the spreadsheet, database or routine only they understand as software your team runs every day, while they are still here to check it.
The business finds out what it lost the first week something goes wrong
One person runs a daily, high-stakes process nobody else can: the schedule, the dispatch board, the quote calculation. It lives in their head, a spreadsheet they built, or a desktop database nobody else opens.
They have a date. When they leave, what they know goes with them, unless it is already in the tools the team uses every day.
A quick test: what happened the last time they were out for two weeks?
Each one leaves the process depending on a person
A handoff binder
It records what the expert thought to write down, not the judgment calls they make without thinking about them. And it sits beside the work, so it goes stale.
Shadowing a replacement
It needs a replacement, enough overlap, and enough cases to see every exception. If any one of the three is missing, it falls short.
Hiring them back as a consultant
It buys time, not a fix. The process still depends on one person, now part-time.
A working system, not a binder or a chatbot
We rebuild the process as software your team runs every day, and check it against your expert while they are still here.
-
Step 1
Find the decisions
Short working sessions with your expert on real cases, not a questionnaire. They don’t write anything; we do the writing. AI handles transcription and first drafts, and your expert and your team decide what is right.
-
Step 2
Build the rules into software
The spreadsheet, the desktop database, the checklist that branches, the calculation only they understand. The software flags what breaks the rules; your people make the call.
-
Step 3
Check it against your expert
We run past and current cases through it. Your expert says where it is wrong, and we fix it. That check is the step a binder never gets.
-
Step 4
Hand it over before the date
Your team runs it while your expert is still in the building, so the first hard week is not the first week alone.
Where it starts: a bounded first phase on your real data, sized to what you ask of us. We pick the narrowest process worth building first, and we tell you if software is not the right answer.
The longer the overlap, the more cases your expert can check, so start early.
For the person who is leaving
Their way of doing it becomes the standard.
This is not documenting someone out of a job. How they run the process becomes how the team runs it after they go, and they are the one who checks that the software gets it right. Short sessions on real work, not a manual to write in their last two weeks.
When this is the right call, and when it isn't
It fits when
- One person runs a daily, high-stakes process that nobody else can.
- They have a departure date, ideally months away rather than weeks.
- What they know lives in their head, a spreadsheet they built, or a database nobody else opens.
- They are willing to help.
It doesn't fit when
- The work is occasional or low-stakes. A written handoff is enough.
- There is no date and no urgency yet.
- The person leaving won’t take part.
What we don't promise: to capture everything an expert knows, or to replace their judgment. We build the decision rules your operation depends on into software, and your people keep making the calls.
FAQ
What it asks of your expert, how it compares with the alternatives, and what it costs.
Can AI capture an expert’s judgment?
Not on its own, and we don’t ask it to. AI helps with transcription and first drafts. Your expert checks the software against real cases and corrects it, and your people keep making the calls.
Our expert doesn’t have time to write it all down. Does this need them to?
No. They don’t write anything. We work through short sessions on real work, and we do the writing.
Won’t our expert resist training their replacement?
They aren’t documenting themselves out of a job. Their way of doing the work becomes the standard your team keeps, and they are the one who checks it.
Why not bring them back as a consultant instead?
That buys time and keeps the dependency on one person. You can do both: they help while the software is built.
Why not just hire a replacement?
A new hire still has to learn the process from someone. This gives them software to run, not a person who has already left.
Where does our operational knowledge end up?
In software built for you and owned by you, which your team runs. What you get is your own system, not a third-party chatbot.
Is this only for retirements?
Retirements fit best because the date is known months ahead. The same approach works for anyone leaving on a date you know, as long as there is time to check the software against them.
How early should we start, and what does it cost?
As soon as there is a date: the longer the overlap, the more cases your expert can check. The cost depends on the process. We start with a bounded first phase on your real data, sized to what you ask of us, and scope it in writing before you commit.
Next step
Is someone retiring who is the only person who knows how part of your business runs?
Tell us about the process and the date. We'll tell you whether software is the right answer, and what we would build first.