KnowledgeCapital

KnowledgeCapital › Guides

Succession planning: organising the succession of knowledge, not only of positions

A succession plan that starts from critical knowledge: who leaves, what leaves with them, who can take over, and proof that the successor is ready.

In short

A classic succession plan names a successor per position. It forgets that the position is not the knowledge: the successor can hold the job without holding the rare skills. KnowledgeCapital builds succession one piece of knowledge at a time, proposes the closest successor and only considers the succession ready once the successor has been assessed.

The position is not the knowledge

Naming a successor settles the org chart. It does not settle the fact that the person leaving was the only one who could calibrate the spectrometer or negotiate with a long-standing supplier. The succession plan must therefore list knowledge, not functions.

Building the plan in four lists

Who leaves, and when

Planned retirements over five years, person by person. On the demonstration: 161 departures, ranked by what they take away.

What leaves with them

For each departure, the knowledge where the person is the single holder or one of two. Those are the transfers to organise urgently.

Who can take over

The decision board proposes a successor: close in skills, in the same structure when possible, with the number of pieces of knowledge to bring up to level and the estimated ramp-up time.

What is missing

When no internal successor exists, the recruitment need is created from the knowledge at risk, and external CVs are compared against the same knowledge.

Succession is ready when it is measured

An action plan sets the pair and the deadline. The internal academy carries the training, level by level, each level validated by a test. Risk only drops once the successor is assessed at the required level: never because a box was ticked.

For the executive committee

An exportable report: retirement wave, urgent transfers, health of the base, with a plain-language interpretation in the reader's language.

To build a succession plan on sound foundations, the set-up order matters: building a knowledge management system from scratch.

Frequently asked questions

How is this different from HR succession planning?

The HR plan reasons by position and potential. This one reasons by knowledge and measured mastery. The two complement each other.

Can several successors be prepared for the same knowledge?

Yes, and it is recommended for the most critical knowledge: availability rises with each assessed successor.

How long does a ramp-up take?

The board estimates it from the level gap and the transferability of the knowledge; it is an indication, to adjust with the pair.

No card. A space pre-filled with five years of demonstration data.

Try it free for 14 days   Watch the guided tour

Going further

Updated on

The other guides

Knowledge transfer before retirement: the method

How to organise know-how transfer before an employee retires: spot what leaves, measure the risk, train a successor, prove it is done.

Knowledge management software: how to choose

Knowledge base, wiki, document management or knowledge mapping: which knowledge management software answers which need, and the five questions that decide.

Knowledge management system: a 12-point evaluation grid

Twelve criteria to compare knowledge management software without solving the wrong problem: tacit knowledge, criticality, connectors, sovereignty, cost.

Skills mapping: method and software

How to map an organisation's skills: reference list, mastery levels, criticality. What separates an Excel matrix from a living map.

How to build a knowledge management system from scratch

The exact order for building knowledge management on a blank space: org chart, people, knowledge catalogue, processes, holders, criticality, assessments.

Key-person risk: knowledge held by one person

Spot knowledge that depends on one person, measure the exposure and organise a successor before the incident: the single point of failure of knowledge.

Lessons learned software with validation

Capture lessons learned from the field: contribution, validation by a committee, links to knowledge, search across four languages.

Industrial knowledge management for maintenance

Knowledge management for industry, mining and energy: maintenance know-how, rare skills, departures, and a method that holds up on site.

Sovereign knowledge management with local AI

Self-hosted knowledge management software: no outbound connection, local AI, built-in video conferencing, isolated data, full reversibility.

A knowledge ERP: what your ERP does not manage

An ERP manages stock, orders and payroll. It does not know who is the only person able to restart the line. KnowledgeCapital is the ERP of that resource.

Internal expert network: find who knows

Locate expertise in the organisation: an expert network based on measured mastery, questions routed to who knows, answers captured.

Succession planning for critical knowledge

A succession plan that starts from critical knowledge: who leaves, what leaves with them, who can take over, and proof that the successor is ready.

SharePoint knowledge base connector: setup and limits

The SharePoint connector reads your site pages and document libraries via Microsoft Graph, read-only, and links each file to the knowledge it describes.

DMS and knowledge management: Alfresco, Nuxeo, CMIS, WebDAV

Your DMS keeps documents; it does not say who knows. The connector reads Alfresco, Nuxeo or Nextcloud through CMIS or WebDAV, read-only.

Notion as a company knowledge base: a practical guide

Notion is great for writing together. How to structure a Notion knowledge base, and connect it to learn who actually masters what it describes.

Intranet knowledge management: map knowledge, no migration

Your intranet publishes procedures; it does not say who can apply them. The connector reads its pages, even without a sitemap, and feeds the knowledge map.