A finance operations manager prepares to leave. Her successor notices that payments to one supplier follow a different approval route. The procedure describes the steps but gives no reason for the exception. The outgoing manager remembers an earlier dispute over invoice accuracy, although she is unsure whether the supplier has since corrected the underlying problem.
The successor needs more than a story or a set of instructions. He needs to establish what the arrangement protects, which evidence supports it, who can change it, and whether the original conditions still apply. That is the practical problem of organisational memory: making relevant experience available and interpretable when someone faces a new decision.
Middle managers can contribute because their work connects teams, decisions, and relationships over time. They are one source among many. Specialists, frontline staff, records, systems, and recurring routines also retain knowledge. A resilient arrangement connects these sources rather than making a long-serving manager the only person who can explain how the organisation works.
Memory Is Distributed Across People and Work
Walsh and Ungson’s conceptual paper, Organizational Memory, examines how organisations acquire, retain, and retrieve information. It provides a way to think about memory beyond individual recollection. It is a theoretical account, rather than evidence that a particular management layer is the necessary repository of organisational knowledge.
In the payment example, the procedure retains a sequence of actions. An old dispute record may retain the evidence behind the exception. A colleague may know how the supplier relationship changed. The system configuration may reveal which invoices the rule actually affects. Each source answers a different question.
A manager may help connect those sources because she knows who participated and where the records sit. That connecting knowledge is useful, but it should be made easier for others to navigate. A shared index of decisions and current contacts can reduce repeated dependence on the same person.
The purpose is not to preserve every conversation. It is to retain enough trustworthy context for people to operate, challenge an assumption, and recognise when a decision needs reconsideration. Information that cannot be found or understood at the relevant moment contributes little to that purpose.
Preserve Reasons Alongside the Current Instruction
The supplier exception should have a concise account of its purpose, scope, authorisation, and review conditions. That might explain that additional approval was introduced after discrepancies in a particular invoice category, with removal dependent on a period of verified improvement.
Such a record distinguishes the reason from the rule. A future manager can then ask whether the discrepancies continue, rather than assume that the extra step is permanently necessary or obviously wasteful. The record should also identify the evidence and the role able to authorise a change.
A decision can be sound when made and become inappropriate later. Record the conditions that would justify revisiting it: a supplier system change, a contract renewal, a new source of assurance, or a planned review date. This gives organisational memory a role in adaptation as well as continuity.
Not every historical detail belongs in the active procedure. Keep the instructions people need now clear, and link to the rationale and supporting material. Mixing years of discussion into operational guidance can make the current requirement harder to identify.
Use Conversation to Reveal What a Record Omits
The outgoing manager may know that a supplier contact resolves discrepancies quickly, or that an apparently minor invoice description signals a recurring problem. Some of this can be written down. Other parts become clearer when someone works through an example and explains what they notice.
A useful handover therefore includes demonstration and questions. The successor can process a representative exception, explain his understanding, and identify where he would seek help. The outgoing manager can correct a missing assumption or point to a source the written procedure did not make obvious.
NASA’s Knowledge Continuity guide for supervisors recommends building knowledge sharing into routine work and planning for transitions. Its practical suggestions include documentation, mentoring, and shadowing. These are NASA’s continuity practices, not a guarantee that following a checklist will preserve every form of expertise.
For the finance team, a short overlap involving real cases may reveal more than a final presentation. If overlap is impossible, recorded walkthroughs, a shared question log, and introductions to relevant colleagues can still help. The organisation should set realistic priorities rather than expect a departing employee to capture an entire career in their last week.
Decide What Is Important Enough to Transfer
Begin with work that would be difficult to continue or recover without a particular person’s knowledge. Consider payment approvals, unusual customer commitments, operational recovery, regulatory records, and dependencies on external parties. Importance depends on consequences, frequency, and the availability of another reliable source.
For each area, identify the people and material already available. The departing manager may be the best person to explain the supplier dispute, but the procurement lead may hold the current contract and an analyst may know the system configuration. Knowledge transfer should connect them rather than duplicate everything in a separate management archive.
Assign time to the work. If the outgoing manager remains fully committed to ordinary delivery until departure, the handover plan may be unrealistic. The sponsor needs to choose which work can move, who will receive it, and what uncertainty remains after the transfer.
The same principle applies when the service or team changes ownership. A transfer should describe unresolved issues and outstanding decisions alongside the current operating state. Ownership and stewardship connects that handover to continuing responsibility for the asset and its users.
Test Whether the Knowledge Is Usable
A folder full of documents does not establish that the successor can find the relevant answer. Test a few representative situations. Ask where the supplier exception is documented, what evidence supports it, and what to do if the designated approver is absent.
The test may reveal that access permissions remain tied to the former manager, links point to obsolete records, or several versions claim to be current. These are practical defects that can be fixed before a consequential case depends on the information.
Avoid making recall alone the test. A successor who knows how to locate a reliable record may be better prepared than someone who memorises an old explanation. The organisation needs an appropriate combination of understanding, accessible evidence, and contacts with relevant expertise.
Review unresolved gaps explicitly. If nobody can verify why the supplier route exists, record the uncertainty and arrange a proportionate review. Do not invent a confident explanation to complete the handover. An identified gap is easier to investigate than a plausible story later mistaken for fact.
Let Historical Knowledge Be Challenged
Experience can prevent repeated mistakes, but it can also preserve outdated restrictions. The outgoing manager’s memory of a dispute should prompt investigation. It should not end the conversation about whether the supplier exception remains justified.
Compare recollections with available records, distinguish facts from interpretations, and involve people who saw different parts of the event. Disagreement does not make every account worthless. It may reveal that participants were working with different information or that a later decision changed the original arrangement.
Make corrections visible. If a review finds that the supplier problem was resolved, update the procedure and the rationale together. Archive the earlier version so people can reconstruct the history without accidentally treating it as the current instruction.
This is one reason to avoid describing organisational memory as a store that only needs protecting from deletion. It also needs maintenance. A confident but inaccurate account can be more misleading than an acknowledged absence of information.
Preserve Access Without Copying Everything
A knowledge transfer can fail even when the explanation is accurate if the successor cannot access the supporting material. Confirm that records sit in an appropriate shared location and that authorised colleagues have the permissions needed for their work. Credentials should follow the organisation’s access process, rather than be passed on informally as part of a personal handover.
Keep information handling proportionate. The finance team does not need a duplicate archive of every sensitive email to understand the supplier exception. It needs the approved record, relevant evidence, and a route to restricted material where justified. Existing retention and confidentiality requirements still apply. The manager can coordinate the transfer while the appropriate records or security specialists advise on how material should be preserved.
Build Continuity Into Ordinary Management
The team can record significant exceptions when they occur, review critical procedures after material changes, and introduce colleagues to important external contacts before a departure is announced. These habits spread the work over time and reduce reliance on emergency offboarding.
Keep the approach proportionate. Routine decisions do not all need extensive histories. Concentrate on choices whose reasons will otherwise be difficult to reconstruct and whose consequences matter to future work. Give each active record a clear owner and a trigger for review.
After a transition, ask what the successor could not find and which assumptions needed correction. Use that feedback to improve the next handover. The aim is a team that can understand and revise its own arrangements with evidence, rather than remain dependent on whoever happens to remember the last exception.





