Knowledge that doesn’t disappears as soon as someone leaves.
Not a collection of miscellaneous news articles, but a permanent place for explanations, guides, models, and tools. You'll also see how knowledge moves through a company — and where it gets lost along the way.
memory
Where is knowledge disappearing in your business?
Click a familiar situation. You’ll immediately see why it’s vulnerable and which knowledge path can help.
Key knowledge is in one person's head.
When someone is ill, leaves, or gets busy, it’s not just that person who’s gone. Exceptions, customer context, and decision rules disappear too.
From “someone knows” to “the company knows.”
Click or scroll through the steps. A business memory isn’t a folder of documents; it’s a closed loop of knowledge flowing into execution and back again.
1. Knowledge forms in people’s minds
Experience, customer context, and exceptions often start out implicit. That’s normal. The risk arises when they stay that way.
Knowledge never exists in isolation.
Touch a node. You’ll see which relationship is needed to turn information into actual business knowledge.
Move from scattered to safeguarded.
Use the slider. On the left, you'll see disconnected sources of truth; on the right, how the same knowledge becomes organized, findable and transferable.
You don’t have to read the entire knowledge base.
Choose what feels most recognisable right now. We’ll highlight the relevant route.
Start with knowledge retention and continuity.
First make visible which knowledge is business-critical, where it is, and who or what depends on it.
What would you like more control over?
Start with the problem you recognize. From each topic, you can go from an explanation to a concrete next step.
Getting knowledge out of people’s heads
Document what only colleagues know right now: agreements, exceptions, ways of working, customer knowledge, and decision rules.
Start with Bedrijfsgeheugen →02 · AIMake AI useful and manageable
From isolated experiments to applications, ownership, governance and measurable value.
View AI adoption →03 · SYSTEMSStop retyping
Understand which data should be authoritative and how to prevent duplicated work and errors.
Read about connecting systems →04 · CONTINUITYLess dependent on one person
Make visible what becomes vulnerable if a key person is unavailable or leaves.
View continuity →05 · DATAKnow where your data stays
Practical explanations of data flows, ownership, privacy and suppliers.
Read about data sovereignty →06 · REGULATIONSRules without a legal quagmire
What the AI Act and governance mean in practice for teams using AI.
View the AI Act guide →The core of Bedrijfsgeheugen
Three reliable sources for understanding where knowledge leaks away, where automation helps, and how change is sustained.
Use knowledge in four steps
A knowledge base is only useful if you use it to make a change.
Recognize
Start with searching, retyping, dependency, errors or unclear AI agreements.
Understand
Identify the root cause, not just the visible symptom.
Measure
Use a scan, benchmark or index to make impact and priority concrete.
Improve
Tackle one manageable change and embed it in the process, system and ownership.
Don't just read. Measure too.
Use the established tools to turn intuition into a concrete starting point.
Self-scan
Seven questions to see where knowledge and execution are vulnerable.
Start the self-assessment →Benchmark
Compare your situation with companies facing the same growing pains.
View your position →Completion index
Make visible what was started once but still doesn't really work or isn't finished.
Measure what's left undone →New insights are on the Blog.
The knowledge base is intentionally stable and organized by topic. For recent articles, observations, figures and developments, go to the Blog.
Know where the friction is, but not what to tackle first?
In a Fresh Perspective session, we look at processes, knowledge, systems, and AI opportunities. No sales pitch; just a clear first picture.