Knowledge Management with ISO 30401: How to Keep Expertise When an Employee Leaves

Why does expertise leave with the employee?

ISO 30401 describes knowledge as intangible and complex, created by people, and treats it as a core asset that supports decisions, process efficiency and resilience. Its introduction states plainly that critical knowledge is often siloed with particular experts and risks being lost when the organisation changes or those experts leave, a growing concern given workforce attrition and turnover. ^[3]

The problem is that most organisations know this and do little about it. In a global survey of 1,000 organisations that APQC ran with eGain and reported in 2025, only 8% of respondents said their organisation consistently captures knowledge from departing retirees, and 16% said they do not try at all. ^[5] The familiar result: a long-serving engineer or accountant leaves, procedures they ran “from memory” stall, and the team discovers that the files do not record why decisions were made.

What does ISO 30401 mean by knowledge management?

ISO 30401:2018 is a requirements standard for knowledge management systems. It was published in November 2018, applies to any organisation regardless of type or size, and its official page notes that it is to be revised. ^[1] It defines knowledge as a human or organisational asset enabling effective decisions and action in context, and notes that it can be individual, collective or organisational. ^[2]

What sets the standard apart is that it does not start with technology. Clause 4.2 requires stakeholder requirements to be framed in terms of business performance rather than knowledge management needs, and clause 4.1 reminds the reader that knowledge management outcomes are a means to organisational outcomes, not ends in themselves. ^[2] Its principles also state that knowledge cannot be managed directly: what is managed is the working environment in which it grows. Culture is critical, and implementation should be phased with learning cycles. ^[3]

Which activities must the system cover?

Clause 4.4.2 requires the organisation to show that its system covers four knowledge development activities: acquiring new knowledge, applying current knowledge, retaining current knowledge, and handling outdated or invalid knowledge. ^{[4, 2]}

Clause 4.4.3 adds the ways knowledge is conveyed and transformed: human interaction; representation (such as writing things down or leading by example); combination (such as curating and synthesising); and internalisation and learning, which turn knowledge into practice. ^[4] The enablers are human capital, knowledge management processes, technology, governance and culture. ^[4]

The practical lesson: retaining a leaver’s expertise is one activity out of four, and it fails if it is reduced to “representation”, that is, writing manuals. Interaction and learning by doing are part of the transfer, not optional extras.

How do you identify knowledge at risk?

You cannot transfer everything every employee knows. Start with a risk assessment, as TechnipFMC does in the case described in the APQC report: it looks for knowledge that is unique and critical, then maps it by context, owner, purpose and description. ^[5] Priorities can be set with four questions for each role:

A role showing two or more high-risk signs needs a written transfer plan with a named owner and a date. Retirement is not the only trigger: internal transfers, promotions, contract endings and nationalisation programmes that move roles to new national staff all deserve early planning.

How do you build the transfer plan before departure?

The APQC report describes a seven-step process used by TechnipFMC, an energy-sector company: plan the project; interview the expert and the wider community that relies on them; assess risk; map the knowledge; build a transfer plan for the largest gaps; deploy and promote the knowledge assets; and finally close out and celebrate with the retiring expert. ^[5]

When choosing a transfer method, match it to the type of knowledge:

• Stable procedures and rules: document them in a procedure manual or checklist, reviewed by someone other than the author.
• Judgement and situational decisions: formal mentoring and working alongside the expert, which APQC recommends for the tacit knowledge senior employees typically hold. ^[5]
• Stories behind decisions: recorded interviews later turned into summaries and lessons learned; AI can help summarise them and draft training material from them. ^[5]
• Relationships and networks: the successor is introduced in person to key clients, suppliers and regulators.

Hypothetical example: a head of procurement before retirement

The head of procurement at a government entity retires in ten months. The first interview reveals that only he knows the reasons for long-standing exceptions with three suppliers, and how quantities are estimated for seasonal tenders.

The entity sets a three-track plan. His successor shadows him through two full tender cycles and leads the second under his supervision. Four interviews on difficult decisions are recorded and turned into a lessons-learned note. The quantity estimation guide is updated and checked by another procurement specialist before approval. In the final month the successor is introduced to the main suppliers, and the materials are reviewed three months after he leaves to confirm the team actually uses them.

How does this link to the quality system?

Organisations certified to ISO 9001:2015 already have an obligation: clause 7.1.6 requires them to determine the knowledge needed to operate their processes and achieve conformity of products and services, to maintain it and make it available to the extent necessary, and, when needs and trends change, to consider current knowledge and determine what additional knowledge or updates are required. Among the internal sources it lists are knowledge gained from experience, lessons learned from failures and successful projects, and capturing and sharing undocumented knowledge. ^[6]

An organisation can therefore start with a register of critical knowledge inside its quality system, then grow towards a full ISO 30401 knowledge management system as practice matures. The standard itself encourages phased implementation. ^[3]

How do you know the transfer worked?

The number of documents uploaded is not a measure of success. The APQC report suggests measuring knowledge programmes from several angles: adoption and participation, cost, efficiency and quality, user engagement and satisfaction, success stories, and business outcomes. ^[5] In practice, three to six months after the expert leaves, ask:

• Does the successor perform the critical tasks without calling the person who left?
• Have errors or turnaround times increased in the processes they used to run?
• Does the team actually use the materials collected, and who keeps them up to date?

Remember that handling outdated knowledge is a separate activity in the standard. ^[4] Material gathered from the expert needs an owner who reviews it and withdraws what is no longer valid; otherwise it becomes a new source of errors.

Checklist before any expert leaves

1. Is the role on the critical knowledge register, assessed for importance, scarcity and timing?
2. Is a successor named, and have they been working alongside the expert for months rather than days?
3. Has an interview been recorded on decisions, exceptions and their reasons, not just procedures?
4. Have files been moved from personal mailboxes and devices to the organisation’s repository?
5. Has the successor been introduced to the key external relationships?
6. Is there a date to review the materials after departure, and an owner to keep them current?

Conclusion

Knowledge management does not stop people leaving, but it stops the organisation being hostage to one person’s memory. Identify critical knowledge early, transfer it through practice and conversation rather than documents alone, and make retention part of a management system that leadership reviews regularly.