Knowledge Loss: What Leaves When Experienced Staff Leave

Picture an engineer who retires after thirty years. Her files stay. Her procedures stay. What leaves is harder to name: which supplier to call when the usual one fails, why a valve is never set to its rated maximum, which kind of complaint signals a real problem. Months later, the team discovers what it did not know it knew.

This is knowledge loss, and most organisations meet it unprepared. A bigger shared drive will not fix it. The fix starts with knowing what kind of knowledge walks out the door.

The knowledge that leaves is the hardest to write down

In The Tacit Dimension, first published in 1966, the philosopher Michael Polanyi started from a simple observation: "we can know more than we can tell." A skilled person recognises a face, a fault or a risk without being able to list the rules they used.

Ikujiro Nonaka built on this distinction. In a 1994 paper in Organization Science, he argued that organisational knowledge is created "through a continuous dialogue between tacit and explicit knowledge." With Hirotaka Takeuchi, in The Knowledge-Creating Company (1995), he described four modes of conversion, now known as the SECI model.

• Socialisation: tacit to tacit, through shared experience and conversation.
• Externalisation: tacit to explicit, when experience is put into words, models or procedures.
• Combination: explicit to explicit, when documents are merged and reorganised.
• Internalisation: explicit to tacit, when people learn from documents and make the knowledge their own.

The model explains why exit paperwork rarely works. Most handovers attempt only combination: moving explicit documents from one folder to another. The knowledge that matters most needs socialisation and externalisation, and both take time with the person who holds it.

We see a quieter version of the same loss on the front line. New staff learn by watching colleagues. When those colleagues work in different ways, the newcomer copies the difference, and the gap passes from one intake to the next. Nobody left. The knowledge still did not travel.

How common the gap is

David DeLong's 2004 book, Lost Knowledge: Confronting the Threat of an Aging Workforce, framed the risk early. He argued that the departure of experienced professionals and managers would make it hard for organisations to sustain past performance. He also noted that retirement is only part of it. Mid-career people leave unexpectedly too.

Two decades later, the gap remains. In a 2025 report based on a survey of 1,000 organisations, APQC found that only 8% consistently capture knowledge from departing retirees. Another 16% do not attempt it at all. In every group surveyed, fewer than one in ten respondents said they were not at all concerned about knowledge loss.

The concern is widespread. The practice is not.

What NASA chose to capture from the Space Shuttle

When a programme ends, its knowledge is at greatest risk. As the Space Shuttle Program moved towards retirement, NASA ran a Space Shuttle Tacit Knowledge Capture Project. In 2008, it interviewed 20 former key members of the programme at NASA centres in Florida, Mississippi, Alabama and Houston. NASA describes the interviews as reflecting "details of critical program decisions," along with management tools, processes and lessons learned.

Look at what was chosen. The procedures were already documented. The interviews went after decisions and the reasoning behind them. A procedure tells the next team what to do. The reasoning tells them when the procedure no longer fits.

Five practical ways to retain critical knowledge

1. Identify critical knowledge holders early. Do not wait for a resignation letter. Review each role with two questions: how hard would this person's knowledge be to replace, and how soon might they leave? Retirement eligibility is one signal. Being the only person who understands a system, a client relationship or a process is another. Start where both answers are worrying.

2. Run structured handover interviews, not exit forms. A form asks what someone did. An interview asks how and why. Prepare questions from the person's actual work: the decisions they made, the exceptions they handled, the people they called. Ask for stories about specific cases. Record the conversation with consent, and turn it into notes a successor can use. Hold several shorter sessions over weeks, not one long session on the last day.

3. Capture decisions and their reasons, not just procedures. Ask: what did you decide that someone else would not have known to decide? Which options did you reject, and why? Which rules have exceptions, and when do they apply? Write each answer as a short decision record: context, options, decision, evidence and expected outcome. This is the part of employee knowledge transfer that procedure manuals miss.

4. Pair and shadow before departure. Tacit knowledge transfers best through shared work, which is socialisation in Nonaka's terms. Have the successor work alongside the expert on real cases. Then swap roles, so the expert watches the successor. Gaps become visible quickly, while there is still time to fill them.

5. Make after-action reviews routine. The US Army's after-action review, or AAR, is a short structured discussion after an event. It asks what was supposed to happen, what actually happened, why, and what to do differently next time. Army guidance describes it as "neither an evaluation nor a critique." Run regularly, AARs turn tacit knowledge into shared knowledge all the time, so less depends on a single exit interview. Our article on lessons learned that change the next project shows how to make the results stick.

Make knowledge retention part of the work

The common thread is timing. Knowledge captured during the work is richer, and cheaper, than knowledge extracted in a final week. Four habits do most of the work.

• Every significant decision gets a short record when it is made.
• Every project milestone includes a brief review.
• Every critical role has a named successor who has shadowed the work.
• Every planned departure has a handover plan that starts weeks, not days, before the last day.

Documents keep what people did. Decision records keep why they did it.

How Prism helps knowledge stay

Prism keeps an organisation's decisions and knowledge as items with a stated trust level: ratified, evidenced, observed or inferred. Handover notes, interview insights and Pause and Learn lessons link to the decisions, steps and evidence they explain. When someone leaves, their reasoning stays attached to the work it shaped. The assistants your team already uses can help a successor find it. People judge what matters. Prism keeps it findable.

Sources

1. The Tacit Dimension (first published 1966; edition with a foreword by Amartya Sen). University of Chicago Press (M. Polanyi), 2009.
2. A Dynamic Theory of Organizational Knowledge Creation. Organization Science 5(1) (I. Nonaka), 1994.
3. Lost Knowledge: Confronting the Threat of an Aging Workforce. Oxford University Press (D. W. DeLong), 2004.
4. Navigating the Great Retirement with KM & AI. APQC, 2025.
5. Space Shuttle Tacit Knowledge Capture Project (oral histories). NASA History Office, 2008.
6. After Action Reviews: Current Observations and Recommendations (Research Report 1867). U.S. Army Research Institute for the Behavioral and Social Sciences (M. S. Salter, G. E. Klein), 2007.

Comments

Your nameYour comment

Comments appear after our team reads them. Please do not include patients' or colleagues' personal details.

Post comment