Business Analysis
When knowledge leaves the organisation
Knowledge that exists only in people's heads leaves the organisation the moment those people go.
Most organisations hold a great deal of knowledge. About clients, about projects, about decisions made years ago. The problem is rarely the amount. The problem is where that knowledge actually lives.
It rarely lives in a system. It lives in people's heads – with the project lead who has been there for eight years, with the external partner who knows the starting situation, with the person who made a decision three years ago and knows why.
Knowledge is not the same as context
Minutes show what was decided. They rarely show why. A file shows which document was last valid. It does not show which exception was accepted in daily practice, or why. That context is exactly what makes a decision traceable later – and it is exactly what gets lost first.
Three points where knowledge leaves the organisation
Staff turnover is the most obvious one. Someone resigns, retires or moves into a different role internally – and with them, part of the reasoning behind past decisions disappears.
Less obvious are the boundaries between teams. Knowledge that forms in one team often does not cross the line into the next department. Not out of ill intent, but because nobody is explicitly responsible for passing it on.
And then there are partners and external staff. A fixed-term mandate ends, the contract runs out – and with it a piece of experience that formed during the collaboration but was never written down anywhere.
Why this is a decision-making problem
Missing context is at first a matter of convenience: you search longer, ask someone who might still remember. It becomes a real problem once a decision needs to build on an earlier one – and nobody can say anymore what that earlier decision was actually based on.
Either a new decision gets made without knowing the old reasoning. Or the old decision simply gets carried forward incorrectly, because the assumption behind it is no longer visible.
Organisational memory instead of accidental knowledge
What an organisation needs is not another filing system. It is an organisational memory: the ability to hold knowledge, decisions and their reasoning in a way that stays accessible independent of specific people – for the next person, the next decision, the next handover.
Internally, I sometimes call this principle a "company brain" – a working term, not a product name. Externally, the more fitting term is organisational memory: what an organisation knows about itself, independent of who happens to be there right now. QUENARIS is one of the tools my business partner Ralph Mattli works with on exactly this question.
That does not mean storing everything. It means keeping experience connectable – prepared in a way that lets someone joining later build on a decision instead of reinventing it. And it means linking a decision to its later impact, instead of documenting the two separately.
Knowledge that leaves an organisation rarely comes back on its own. Anyone who wants to keep it has to deliberately set things up for that.