Knowledge Transfer
Getting what one person knows out of their head and into a form the organisation keeps: documentation, handover and the tacit knowledge nobody writes down.
Overview
Most organisations have systems that one person understands. Everyone knows this is a risk and nobody has time to fix it, because the person who could document it is the person too busy running the thing to write about it.
The work here is extracting that knowledge without depending on the expert to write it. We interview, observe, attempt the task ourselves, and write the documentation, which they then correct. Correcting a draft takes a fraction of the time writing one does, and it produces something an outsider can actually follow.
Who this is for
- Companies whose critical systems are understood by one person
- Businesses facing a departure or a retirement
- Teams who inherited something with no documentation at all
How we approach knowledge transfer
The specific pieces of work a typical engagement covers. Scope is agreed up front — nothing here is a surprise line item later.
Knowledge audit
What is only in someone's head, and which of it would actually hurt to lose. Not everything needs documenting.
Extraction by observation
Interviews and watching the work, which surfaces the steps experts have stopped noticing they perform.
Written by us, corrected by them
We produce the draft and the expert reviews it. Reviewing is fast; writing is what never happens.
Runbooks and procedures
Step-by-step material for the operational tasks, written so someone unfamiliar can follow them under pressure.
Decision records
Why things are as they are, which is what stops a successor undoing a deliberate choice they mistook for an oversight.
Tested with a newcomer
Someone unfamiliar attempts the task from the documentation alone. This finds the assumed steps nothing else will.
From first call to measured result
The same sequence every time, so you always know what happens next.
Prioritise
Identify where key person risk actually matters, since documenting everything is neither possible nor useful.
Extract
Interview and observe, taking on the expert's time in short sessions rather than asking for days of writing.
Write and verify
Produce the documentation and have the expert correct it, then test it with someone unfamiliar.
Make it maintainable
Put it somewhere findable with an owner and a review date, so it does not go stale within a year.
Outcomes, not deliverables
A pile of artefacts isn't progress. These are the changes the work is meant to produce — and what we report against.
Key person risk reduced
The most acute organisational risk most companies carry, and the one they consistently postpone addressing.
Very little expert time
Interviewing and correcting takes hours where writing would take days, which is why this version actually happens.
Documentation that works
Testing with a newcomer is what separates usable instructions from a description that assumes the reader already knows.
Faster onboarding
The same material shortens how long a new person takes to become useful.
Common questions about Knowledge Transfer
The things people ask before they get in touch. If yours is not here, ask us directly.
Our expert has no time to document anything. Can this still work?
That is precisely the situation this is designed for. We do the writing; their involvement is a few interview sessions and reviewing a draft. Reviewing takes a fraction of the time and is a task people will actually complete.
How do we stop documentation going stale?
A named owner, a review date, and keeping it close to the thing it describes. Documentation in a wiki nobody opens decays; documentation next to the code or in the runbook people use during an incident survives.
What if the expert is leaving soon?
Then prioritise ruthlessly and start immediately. Get the operational runbooks and the decision records first; everything else can be reconstructed with more effort, but those two cannot.
How much should we document?
Less than instinct suggests. Document what would be expensive to lose and what someone would need under pressure. Comprehensive documentation of everything is never maintained and its staleness makes people distrust all of it.
Thinking about Knowledge Transfer?
Tell us what you are trying to change. If we are not the right fit we will say so, and point you somewhere better.
Looking at the wider picture?
Knowledge Transfer usually sits alongside other work in Training, Enablement & Knowledge. Browse the full area to see what it connects to.