When 30 Years of Experience Walks Out of the Door

Introduction

Imagine someone has worked in a company for 30 years. They know the systems, the people, the old problems, the shortcuts, the mistakes that should never be repeated and basically all the little things that are not written anywhere. Then one day, they retire. Everyone says, “We will manage.” But a few months later, someone asks, “Wait, how did they used to solve this?” And nobody knows.

So, the company did not just lose one employee. It lost years of experience. This is one of the biggest problems HR can face when experienced employees retire. Like, the person's job description can be replaced, but their knowledge may not be that easy to replace. This is why succession planning and knowledge management need to work together.

NASA describes this type of knowledge as critical knowledge. It is knowledge that is important for the organisation to perform its work and make good decisions, and much of it comes from individual and organisational experience. NASA specifically focuses on keeping this knowledge available when experienced employees retire or move to another role.

Problem

The problem is that employees do not only carry information in documents. They also carry experience in their heads. An engineer may know that a machine usually makes a particular sound before it fails. A manager may know which supplier can handle an emergency order. A senior HR employee may know why an old policy was created and what happened when the company tried to change it before.

So, when that person leaves, the organisation may still have files, policies and reports. But it may not have the thinking behind those documents. This is called tacit knowledge. It is knowledge that comes from experience and is often difficult to explain or write down completely.

The other type is explicit knowledge. This is knowledge that can be written, stored and shared, like manuals, checklists, policies, reports and training documents. The problem is that companies often focus on explicit knowledge because it is easier to store. They may forget that some of the most useful knowledge is sitting inside an experienced employee's head.

This can create a serious continuity problem. A new employee may technically have the same job title as the person who retired, but they may not have the same experience. So, mistakes can increase, decisions can take longer and employees may spend more time trying to figure things out from the beginning.

Analysis of the Problem

The first important concept is knowledge continuity. Basically, knowledge continuity means making sure important knowledge does not disappear when people move, retire or leave. It connects succession planning with knowledge management. So, succession planning should not only ask, “Who will replace this person?” It should also ask, “What does this person know that the replacement needs to learn?”

The second concept is critical knowledge mapping. This means identifying which knowledge is actually important for the organisation and where that knowledge currently exists. So, instead of trying to document everything, HR can ask simple questions. What knowledge would be difficult to replace? Who has it? Who needs it? What would happen if we lost it tomorrow?

The third concept is tacit and explicit knowledge. Explicit knowledge can be stored in documents, while tacit knowledge is connected to experience, judgement and personal understanding. So, a 50-page technical manual may explain how something should work, but a person with 30 years of experience may know what usually goes wrong in real life.

This is where the SECI model becomes useful. Developed by Ikujiro Nonaka and Hirotaka Takeuchi, the model explains how organisations create and share knowledge through four processes: socialisation, externalisation, combination and internalisation. In simple words, people learn from each other, turn experience into something that can be explained, combine information and then use that knowledge themselves.

So, imagine a senior engineer teaches a younger engineer how to identify a problem by watching the machine. That is socialisation. If the senior engineer then explains the signs and creates a checklist, the experience becomes more explicit. The younger employee uses the checklist and combines it with other information. Finally, after handling similar problems themselves, the knowledge becomes part of their own experience.

Another useful concept is a community of practice. This is basically a group of people who share knowledge because they work in the same area or deal with similar problems. The group does not need to be a formal department. Engineers from different projects, for example, can share lessons and solutions with each other. This means knowledge does not stay with only one person.

There is also reverse mentoring. Traditional mentoring usually means an experienced employee teaches a younger employee. Reverse mentoring adds another direction. A younger employee can also teach the experienced employee about newer technology, tools or ways of working. So, knowledge transfer becomes two-way instead of being only “senior teaches junior.”

Real-Life Case: NASA and the Knowledge That Could Walk Out the Door

NASA is a very strong example because its work depends heavily on technical experience. NASA has openly recognised that many of its experienced technical employees have retired or are approaching retirement. Its own knowledge-management material says that the lessons learned by people involved in major programmes need to be retained and passed to the next generation.

NASA even recorded an early warning about this problem. A NASA lesson from 2001 described a reduction in the organisation's knowledge base because experienced employees were leaving while less-experienced employees were being hired. The lesson noted that there was no systematic effort at the time to capture the knowledge of experienced employees before they left. NASA recommended active mentoring and stronger development support so newer employees could become productive more quickly.

So, the issue was not simply retirement. The bigger issue was what retirement took with it. NASA had people who had worked on major programmes and had learned from situations that could not easily be recreated. Some of that knowledge came from failures, unexpected problems and decisions made under pressure.

NASA later became much more systematic about this. Its Safety and Mission Assurance organisation, for example, created knowledge-capture activities involving retiring experts. In 2005, NASA held knowledge-capture events featuring retiring fellows who shared lessons from programmes including the Space Shuttle, Apollo and Skylab, with the goal of making those lessons useful for future work.

NASA also recognised that simply asking people to “write everything down” would not be enough. Its current knowledge-management approach includes lessons learned, knowledge-sharing communities, recordings, technical resources and other ways of capturing knowledge. NASA says its knowledge community helps capture, store, reuse and share knowledge across the organisation.

HR Theories, Frameworks and Concepts Reflected in the Problem

The first concept we can see is tacit knowledge. A large part of an experienced employee's value may come from knowledge that is difficult to write down. They know what to do because they have seen the situation many times before. So, replacing the employee does not automatically replace the knowledge.

The second concept is the SECI model. NASA's knowledge-sharing activities show why organisations need ways to move knowledge from individual experience into something that other people can understand and use. Interviews, discussions, lessons learned and technical documentation can help turn personal experience into organisational knowledge.

The third concept is critical knowledge mapping. Not every piece of information has the same value. HR needs to identify the knowledge that would create the biggest problem if it disappeared. This helps the organisation focus its time instead of asking retiring employees to document every single thing they have ever done.

The fourth concept is communities of practice. Knowledge becomes safer when it is shared by a group instead of sitting with one person. If five experienced employees understand a process, the organisation is less dependent on one individual. People can also learn from each other's experiences instead of starting from zero.

The fifth concept is reverse mentoring. A succession plan should not assume that younger employees only need to receive knowledge. They can also bring new technology, new tools and new ways of working. So, knowledge transfer can happen in both directions.

The final concept is knowledge continuity planning. This means making knowledge transfer part of the employee transition process instead of waiting until the employee's final week. NASA's current guidance recommends transition planning, shadowing, continuity books, interviews, panels, video capture and transferring important files before an employee leaves.

Solution Using HR Theories, Frameworks and Concepts

The first step should be to identify critical roles and critical knowledge. HR can work with managers to ask which roles would create the biggest problem if the person suddenly left. Then they can identify what that employee knows that is difficult to replace. This is where critical knowledge mapping becomes useful.

The second step is to create a proper knowledge-transfer plan. So, instead of saying, “Please train your replacement before you leave,” the organisation can create a simple plan. What does the employee need to teach? Who needs to learn it? How will they learn it? When will the transfer happen? How will we know that the new person can actually do the work?

The third step is shadowing. A younger employee can work alongside the experienced employee and watch how they handle real situations. This is especially useful for tacit knowledge because some things are much easier to learn by watching than by reading.

The fourth step is to use the SECI model. HR can encourage experienced employees to explain their decision-making, record important lessons and turn repeated problems into guides or checklists. Then younger employees should actually use those resources in real work. Otherwise, the knowledge may be stored but never really learned.

The fifth step is to create communities of practice. Instead of keeping knowledge inside one team, organisations can create regular knowledge-sharing sessions where employees discuss difficult cases, mistakes, solutions and lessons. So, when one expert leaves, the knowledge is already spread across a wider group.

Finally, HR can use reverse mentoring. A senior employee can teach the younger employee about the history and practical side of the job, while the younger employee can help the senior employee with new digital tools or newer ways of working. This also makes the transition feel less like “old employee versus new employee” and more like two people learning from each other.

Actual Solution Implemented at NASA

NASA has built a much more formal system around knowledge continuity. Its Knowledge Capture and Transfer programme was created to help organisations retain important knowledge when experienced employees transition out. NASA's working group found that there had been no systematic approach across its Safety and Mission Assurance organisation for capturing and sharing the knowledge of retiring employees, so it developed recommendations for making this part of the transition process.

The recommendations included better information about upcoming retirements, regular opportunities to capture lessons and technical expertise, and planned knowledge-capture interviews. NASA also developed a process that connects knowledge discovery and capture with learning and onboarding, so the information does not simply sit in a database. It can actually become part of how new employees learn their jobs.

NASA's practical tools include transition plans, shadowing, continuity books, interviews and panels, short video recordings, and transferring files and records before the employee leaves. It also suggests keeping communication possible after retirement when appropriate.

NASA also uses a Lessons Learned system where reviewed lessons from programmes and projects can be stored and searched. The purpose is basically to make sure that one team's experience can become another team's learning instead of the organisation repeating the same mistake.

NASA has even used phased retirement as a way to support succession planning, maintain important skills for a period of time and allow retiring employees to mentor others and transfer knowledge before fully leaving the organisation.

What HR Can Learn From This

The biggest lesson is that succession planning should not start when someone submits their retirement paperwork. By then, HR may already have very little time. It should start much earlier by asking which knowledge is critical, who has it and who needs to learn it.

So, when a person with 30 years of experience walks out of the door, the organisation should not be left thinking, “We will figure it out.” It should already have the next person learning from them, important knowledge captured, lessons shared and responsibilities slowly transferred.

Like, employees will always leave. People retire, change companies, move cities and take new opportunities. HR cannot stop that. But HR can make sure that when people leave, they do not take the organisation's most important knowledge with them. That is what real talent continuity looks like. It is not just replacing a person. It is making sure the knowledge behind the role continues.