Embed
Knowledge that stays in the company
The knowledge is there. It just sits with individuals – and leaves with them.
Do you recognise any of these?
- A key person leaves – and with them everything that was never written down.
- Onboarding takes months – and everyone still asks the same two people.
- The knowledge is there – but tied to individuals, not to the organisation.
- There is documentation – it just does not help at the decisive moment.
- A generational handover is coming – and nobody has planned it.
- Learning happens on the side – or not at all, because the day job leaves no gap.
What this is really about
Demographic change makes the topic urgent, but it did not invent it. The pattern is structural: knowledge is there – and it sits with people. Not only with the long-serving, but precisely in key positions, team leads and specialised roles. When that knowledge disappears or is inaccessible, friction follows immediately: longer onboarding, dependencies, quality risks, pressure on those who remain.
The real risk is not the missing document. It is the tacit experience – knowing whom to call, how a particular customer ticks, why a process runs this way and not another. That is in no filing system. And it cannot be written into one; it can only be passed from person to person – if that is done in a structured way and in time.
Knowledge is not secured by systems but by clear structures in everyday work: who passes what to whom, in what form, by when? How is learning built into the work instead of on top of it? That is where I start – pragmatically, without big programmes, with effect where it counts: in the everyday work of the teams. Where the topic needs continuity, also as an interim or project-based mandate.
What I actually do
- Identify critical knowledge – regardless of role or hierarchy. What must not be lost under any circumstances?
- Name dependencies and risks clearly: where does too much hang on one person?
- Secure experience in key positions and at handovers – with experience interviews, structured handover, accompaniment through the transition.
- Shape knowledge transfer between employees, teams and generations – so that it works in everyday practice.
- Treat onboarding and offboarding as what they are: the two moments when knowledge arrives and leaves. Clear processes, buddy systems, learning paths, respectful handovers.
- Integrate learning into everyday work instead of adding it as a burden – scalable formats from pragmatic to structured.
- Build internal learning structures or an academy – sized to the organisation, not to a provider’s catalogue.
- Use AI so that knowledge becomes findable and onboarding faster – where searching used to mean asking.
What changes as a result
Stability
Less dependence on individuals. Less knowledge lost at handovers. More stable processes despite change.
Efficiency
Noticeably faster onboarding. Knowledge is found and used more quickly. Leaders are visibly relieved.
Development
Employees develop from within the company. Internal know-how becomes usable and scalable.
Ways of working together
One day for clarity and first delivery – two or three central topics, concrete solutions, directly applicable. Two days for a full view of knowledge and learning in the company, with a roadmap you can work with. Project accompaniment when structures are to be built and embedded – up to a mandate for a fixed period.
Frequently asked
We have a wiki. Is that not enough?
A wiki secures documentable knowledge. The critical knowledge is usually the other kind: experience, judgement, relationships. That cannot be written down, only passed on – and that needs structure, not software.
Is this not HR’s job?
HR carries the process, but the knowledge sits in the departments. Securing knowledge only works when both work together – and when someone brings the experience of what that looks like in practice. I built exactly that inside a company.
When should we start?
Before someone leaves. The most common enquiry comes six weeks before a key person’s departure – too late for structure, but not too late for a targeted handover. Better still is to know your critical knowledge before the case arises.
Can you take this on as an interim mandate?
Yes. When building knowledge or learning structures needs responsibility over months, I take it on for a fixed period – as the person responsible in-house, not as an outside adviser.
How does this relate to onboarding?
Directly. Offboarding is the moment knowledge leaves; onboarding the moment it has to arrive. The two belong together – a structured transition measurably shortens onboarding time.
If you know which two people nobody could replace, a conversation is worthwhile.
Half an hour to clarify where the critical knowledge sits – and how it stays in the company.