Knowledge transfer succeeds when the recipient can perform the needed task or make the relevant decision. Organise current references around operating questions, explain important exceptions and let the recipient practise. A complete folder export preserves material but does not establish usable understanding or continuity.
Identify the work that must continue
List the recurring tasks and consequential decisions the recipient will inherit. Start with the next operating cycle: a month-end close, supplier escalation or customer review. Ask what must be reliable when the previous owner is unavailable. Prioritise by consequence and timing rather than by the size of the existing folder. Some old documents may be useful history, while a short undocumented approval rule may be essential tomorrow.
Create a small index organised around questions such as “How do I prepare the monthly review?” and “Who may approve an exception?” Link to current sources rather than duplicating every file. Give each reference a status and owner. Mark historical examples clearly so an old project arrangement is not mistaken for the current rule. Include where to find authorised help when the task falls outside the documented boundary.
Expose judgment and exceptions
Ask the outgoing owner to explain one normal case and one difficult case. Focus on the cues that change the decision, the information they check and the people they consult. Capture reasons for important boundaries. A recipient who knows that a supplier request requires qualified review can act more safely than one who only copies a previous answer without understanding why it applied.
Transfer access through the appropriate private process and confirm that the recipient can open the required systems. Avoid placing passwords in the knowledge index. Separate personal working notes from operating records, and remove unnecessary private details before sharing examples. Identify knowledge that depends on external expertise rather than trying to reproduce specialist professional advice in a hurried handover. Give unresolved questions owners and dates so they do not disappear into an archive.
Use a recipient-led exercise and a short follow-up
Let the recipient lead a representative task while the previous owner observes. Ask them to find the right reference, describe the decision and identify the escalation point. Note where they need information that exists only in someone’s memory. The exercise may reveal a missing permission, ambiguous term or outdated contact. Fix those gaps in the current index rather than adding another separate summary that creates competing instructions.
Schedule a check after the first real operating cycle. Record what worked, what required intervention and which guide needs revision. Confirm who maintains the material after the transfer. NIST’s Baldrige commentary treats knowledge management as an operating concern; the index and exercise are practical ways to connect information with the work people need to perform.
Keep the package deliberately small at the point of use, with deeper history available when relevant. A recipient should not need to read several years of meeting notes to find today’s approval route. Measure transfer by demonstrated capability and clear support ownership, while recognising that unusual situations may still require experience and consultation.
Fictional worked example
A fictional scenario to explain the method, not a customer result or a market benchmark.
At the fictional firm Tide Oak, an operations lead prepares to leave behind hundreds of notes. The team identifies three immediate needs: month-end review, supplier escalation and approval exceptions. It builds a concise index linking current procedures and labels older project records as history. The recipient receives the appropriate system access privately.
In a practice exercise, the recipient can prepare the review but cannot explain who approves an unusual supplier payment. The outgoing lead realises that the exception route was never documented. They record the authorised decision role and test the route with the responsible owner before departure. Tide Oak schedules a first-cycle check rather than declaring transfer complete after a folder copy. The invented case demonstrates how practice exposes missing context.
TAKE THIS INTO YOUR NEXT CONVERSATION
A practical next-step checklist.
- Prioritise the next recurring tasks and decisions.
- Build a current question-based reference index.
- Explain normal cases, exceptions and escalation.
- Run a recipient-led exercise and first-cycle review.
Common questions.
Should we delete historical documents?
Retain them according to appropriate responsibilities, but separate them from current operating instructions. Clear status and links reduce accidental reliance on an obsolete example.
What if there is no time for full training?
Prioritise consequential near-term tasks, confirm access and establish a named support route. Record gaps explicitly rather than describing an incomplete transfer as comprehensive.
Further reading & source context.
These primary references provide background. They are not evidence for the fictional example above and do not endorse AccelerateLink.
Found an error or a missing qualification? Send an editorial correction.
Find my next move.
Use a practical tool to turn this idea into a clearer starting point.
Find my next move