From archiving to activating: how knowledge moves from people's heads into a living knowledge base

Most knowledge management projects start with the best intentions and end in the same quiet loss. Senior employees are asked to write down their knowledge. Templates are made, wikis set up, manuals written. A few months later the material is outdated and nobody reads it anymore. The cycle repeats every five to seven years.

The problem is not that people don't want to document. The problem is that documentation is not what knowledge is.

Documentation is the most expensive way to lose knowledge. A document is a photograph. Knowledge is a film that is continuously being updated. We have spent thirty years trying to capture films in photographs and are surprised every time they no longer match.

And the clock is ticking. By 2030, nearly a third of the Dutch workforce will retire, even more in technical sectors. The knowledge those people carry walks out the door with them, and most organisations have no plan for what comes next. Doubling down on documentation now means rebuilding from zero later, with fewer people, less experience and less time.

What traditional knowledge management misses

Real business knowledge is not made of facts but of context. It is the relationship between two things that on paper have nothing to do with each other, but in practice have everything. If supplier Y reports more than two days of delay in the third quarter, the senior production planner knows it will impact deliveries to client Z, because client Z runs on minimal inventory in that period. Try capturing that in a manual.

It is the largest unaccounted-for liability on Dutch corporate balance sheets: knowledge held in one person's name. It appears nowhere as a depreciation, but every retirement silently writes it off. What does show up are the symptoms, not the loss itself: longer lead times, more errors, slower onboarding, declining customer satisfaction. Death by a thousand cuts.

Most companies try to solve this by documenting even harder. But the problem isn't too little documentation. It's the assumption that documentation is the right medium for knowledge at all.

From archiving to activating

BEP turns knowledge management around. People no longer have to write down their knowledge in the hope that someone will read it later. The knowledge is elicited and made available straight away, at the moment it is needed. It works in three steps.

Step 1: a digital intake colleague that asks the questions

Instead of writing manuals, BEP has a conversation. A digital intake colleague talks to the senior production planner, the operator or the account manager and asks the questions others don't always dare to ask. Why do you do it this way? What do you do when something goes wrong? And how do you recognise problems that have come up before?

The difference from a regular questionnaire is that the intake colleague keeps probing. When the senior planner says he "always quickly checks if a warning from zone 3 has come in by email", the colleague follows up: which zone, which warning, where in the email, and what do you do next? The answers go straight into a structured, living knowledge base, ready to be reused and easy to find for the rest of the team.

Knowledge that normally takes twenty years to build up surfaces this way, organised rather than scattered.

Step 2: passive indexing of what is already there

Alongside what comes up in those conversations, BEP also indexes the work that is already happening. This is done with permission and within the privacy boundaries of the organisation. It typically includes emails, documents, systems, processes, procedures, project reports, decisions and meeting notes.

That way the knowledge base grows organically alongside daily work, without anyone having to maintain it separately. What a team decides about a customer question, how a project reaches a conclusion, which exceptions are made and why: all that context becomes part of a shared memory the entire organisation can draw on.

Step 3: active retrieval by other digital colleagues

The knowledge that emerges isn't a dusty archive nobody ever opens again, but an active, shared source of knowledge. Colleagues in sales, HR, planning or on the shop floor consult the knowledge base throughout the day from Slack, Teams or WhatsApp. Not only when they remember to search, but at the moment they need an answer.

The new planner asks: "supplier Y reported three days of delay for week 34. What does that mean for us?" The digital colleague checks Y's delivery history, the production schedule for week 34, the inventory positions of the dependent clients, and answers within seconds with the same patterns the senior planner knew intuitively.

The account manager prepares for a meeting with a top-20 client. The digital colleague immediately surfaces the unwritten rules for that client, the earlier agreements that aren't in the CRM, and the sensitivities from past email threads.

The operator notices a machine sounds different. They ask the digital colleague, which has indexed every maintenance report and conversation note from senior technicians. The answer arrives with sources and a suggestion of what to check.

The difference is in who queries it

A document waits for a human to open it. A living knowledge base waits for no one. It is continuously queried by digital colleagues working alongside the team, and every answer reflects the most current context, drawn from your own unique business information. No generic models, your own data.

That is what a living knowledge base does that a document never can: it is consulted while work is happening, not only when someone thinks to open it. The knowledge comes to your employees at the moment it is relevant.

The next generation of organisations will not be defined by who has the best people. That round is over. It will be defined by who keeps their knowledge alive as the people leave.