Internal Knowledge
You cannot retrieve what nobody ever wrote down.
What is internal knowledge?
Internal knowledge means the understanding an organisation depends on and does not hold in writing, which requires capturing before it can be retrieved, since retrieval technology cannot reach what was never recorded.
The knowledge that actually keeps an organisation running is mostly in people. Why that customer gets different terms, which supplier to call when the usual one fails, what happens if you run the month end in the wrong order.
None of it is written anywhere. When somebody leaves, it leaves with them, and the organisation discovers what it depended on by finding out what now goes wrong.
Every tool in this area promises to make knowledge findable. That only helps with knowledge that exists in writing, which is the easier half. The valuable half has to be captured first, and capture is a people problem rather than a software one.
What retrieval cannot reach
Duara works on internal knowledge in Kenya, and starts with capture rather than with search.
We say plainly that retrieval tools cannot reach undocumented knowledge. Clients arrive wanting to search what they have, and what they have is usually the documented minority. Selling search over that produces a system that answers the easy questions and nothing else.
Who this is for
- Key knowledge sits with a few individuals
- Somebody experienced is leaving or retiring
- New starters take months to become useful
- Documentation exists and does not cover what matters
Industries we serve
- Manufacturing
- Professional services
- Financial services
- Engineering and technical services
- Public sector
- Family businesses
Problems this solves
These are capture problems, and treating them as search problems is why most knowledge projects disappoint.
- Knowledge held in individuals. What keeps things working is understood by three people and written down by none of them.
- Departure as discovery. The organisation finds out what somebody knew by observing what stops working after they leave.
- Documentation covering the wrong things. Procedures describe the standard path while the valuable knowledge is about exceptions and judgement.
- Slow new starters. People take months to become useful because what they need to learn is not written anywhere they can find it.
What we deliver
Capturing undocumented knowledge from the people who hold it, prioritising by what would hurt most to lose, then making the result findable rather than starting there.
Undocumented knowledge captured from the people holding it
Prioritisation by what would hurt most to lose
Capture through conversation rather than forms
The result made searchable once it exists
A view on what remains uncaptured
A process for capturing knowledge as it forms
Features
- Capture before search. Retrieval cannot reach what was never written, and clients usually want to search a documented minority that is not where the value is.
- Prioritised by risk of loss. What would hurt most if that person left tomorrow, rather than what is easiest to document.
- Captured by conversation. Experts do not fill in forms, and asking them to produces documentation of the standard path rather than the judgement.
- Exceptions valued over procedures. The standard path is usually already written. What is worth capturing is what happens when it does not apply.
- Honest about what remains. What is still uncaptured is reported, since believing knowledge is safe when it is not is worse than knowing it is at risk.
Benefits
- Departures stop being crises. Knowledge captured before somebody leaves means their notice period is a handover rather than a countdown.
- New starters become useful sooner. What people actually need to know exists somewhere findable rather than only in a colleague head.
- Fewer avoidable mistakes. The exceptions and judgement calls that were never written down stop being rediscovered the expensive way.
- Dependency becomes visible. Knowing which knowledge sits with one person is useful even before you capture it.
Technologies we use
- Knowledge risk mapping. Identifying what is held by too few people and what losing it would cost.
- Conversational capture. Structured interviews with the people who hold knowledge, since they will not complete forms.
- Exception documentation. Recording what happens outside the standard path, which is where the value concentrates.
- Retrieval over captured material. Making the result findable once it exists in writing.
- Ongoing capture. A process for recording knowledge as it forms rather than only before departures.
Search tools address the documented minority. The undocumented majority is where organisational risk sits, and no amount of retrieval capability reaches it until somebody has had a conversation with the person who knows.
How the process works, step by step
Knowledge work usually takes eight to fourteen weeks, and most of it is conversation rather than software.
-
Step 1
Free knowledge risk review
We identify what sits with too few people and what it would cost to lose, which is usually uncomfortable reading.
-
Step 2
Prioritised by exposure
Capture starts with the highest risk knowledge rather than the easiest to write down.
-
Step 3
Captured by conversation
Structured interviews with the people who hold it, since experts do not fill in documentation forms.
-
Step 4
Made findable
Retrieval is built over the captured material, which is the point at which search becomes useful.
-
Step 5
Ongoing process agreed
How knowledge gets captured as it forms, so this does not become a one off exercise.
Quality assurance and how we work
The commitments attached to work that depends on people cooperating.
- We start with capture, not search. Retrieval cannot reach undocumented knowledge, and selling search over the documented minority produces a system that answers only the easy questions.
- Capture is voluntary and framed as such. Somebody who feels they are documenting themselves out of a job will withhold the valuable part, and you will not know they did.
- We prioritise by risk rather than ease. What would hurt most to lose, not what is simplest to write down, which are rarely the same thing.
- We report what remains uncaptured. Believing knowledge is safe when it is not is worse than knowing it is at risk.
- We do not record people without consent. Capture sessions are agreed with the individual, and material stays under your control rather than ours.
Frequently asked questions about internal knowledge
Can AI search our internal knowledge?
It can search what is written down, which is the documented minority. The knowledge that matters was never recorded and cannot be retrieved.
So what comes first?
Capture. Getting undocumented understanding into writing is a people problem, and no retrieval capability substitutes for it.
Why do knowledge projects disappoint?
Because they are treated as search problems. Search over the documented minority answers the easy questions and nothing else.
How do you capture knowledge?
By conversation. Experts do not fill in forms, and asking them to produces documentation of the standard path rather than the judgement.
What should be captured first?
What would hurt most to lose, rather than what is easiest to document. Those are rarely the same thing.
Why are exceptions more valuable than procedures?
Because the standard path is usually already written. What is worth capturing is what to do when it does not apply.
Will staff cooperate with this?
Mostly, if it is voluntary and framed properly. Somebody who feels they are documenting themselves out of a job withholds the valuable part quietly.
How do you handle that risk?
By framing capture as reducing dependency on them rather than replacing them, and by making participation genuinely voluntary.
What if somebody is already leaving?
Capture during a notice period is possible and worse than doing it earlier. The best time is before anybody is going anywhere.
How long does capture take?
Eight to fourteen weeks, and most of it is conversation rather than software.
Does it help new starters?
Considerably. What people need to learn stops living only in a colleague head, which is what makes onboarding slow.
Will it capture everything?
No, and we report what remains. Believing knowledge is safe when it is not is worse than knowing it is at risk.
Where does a knowledge base fit into this?
A knowledge base is where captured material lives. This is the work of getting the valuable material into it in the first place.
Can it work for a family business?
Yes, and family businesses frequently carry the most concentrated knowledge risk, since decades of understanding sits with one or two people.
Do you record the sessions?
Only with the individual consent, and the material stays under your control rather than ours.
What happens to captured material?
It stays in your systems and becomes searchable, which is the point at which retrieval technology finally has something to work with.
Can we do this ourselves?
Yes, and some organisations should. The method matters more than who runs it, and we would say if you have somebody capable internally.
How does captured knowledge stay current?
Through a process for capturing knowledge as it forms, otherwise this becomes a one off exercise that ages.
Who can see captured knowledge?
Whoever you authorise. Some of it is sensitive about how decisions are really made and deserves careful access.
What does knowledge work cost?
The number of people and depth of capture determine it, quoted after the knowledge risk review.
Glossary of terms
Knowledge terms in plain language.
- Tacit knowledge
- Understanding held by people and not written down, which is where most organisational risk sits.
- Knowledge risk
- Exposure created when too few people understand something important.
- Capture
- Getting undocumented understanding into a form that can be retrieved later.
- Exception knowledge
- What to do when the standard procedure does not apply, which is rarely documented and most valuable.
- Handover
- Transferring knowledge before a departure, which works far better before a notice period than during one.
- Single point dependency
- Something only one person understands, which is a risk whether or not they intend to leave.
Related services in AI Solutions
Talk to us about internal knowledge
Name the person whose resignation would worry you most, and what specifically you would lose. That is the capture list.
Start your project