Findability
Give people a sensible starting place, consistent structure and language that matches the questions they actually ask.
Knowledge systems, handover and key-person risk
Make important knowledge easier to find, trust and keep current.
You get help turning scattered documents, repeated questions and expert memory into a usable knowledge system with clear ownership. The aim is not more documentation. It is fewer avoidable interruptions and less dependence on who happens to be available.
If the answer is “ask the person who knows”, the system has borrowed their memory.
Experienced people will always hold valuable judgement. The risk appears when routine answers, current instructions, important decisions or exception handling can only move through them. A useful knowledge system protects expertise without turning every thought into a document.
- New starters ask the same questions repeatedly.
- People cannot tell which version of a document is current.
- Important work slows during leave or role changes.
- Teams recreate material because the existing answer cannot be found or trusted.
- A knowledge base exists but has no clear owner or review rhythm.
- Search or AI is being proposed before the information underneath it is reliable.
- Sensitive or important information is stored in inappropriate places.
What you can improve
Trust
Make authority, version, scope and review dates visible so people can judge whether an answer is current.
Ownership
Name who maintains each important area and what event should trigger a review.
Use in the workflow
Put the answer where the decision or task happens. A knowledge system that depends on people remembering to visit it will quietly age.
Handover and resilience
Capture recurring work, decisions, exceptions and relationships in a form another capable person can use.
Typical engagement outputs
- An inventory of important knowledge and sources
- Evidence about repeated questions, search failures or dependencies
- A usable information structure and source-of-truth decisions
- Content patterns, ownership and review rules
- A handover or onboarding working kit
- A tested knowledge workflow or bounded AI-assisted retrieval prototype
- Clear deletion, archival or escalation actions where appropriate
A practical sequence
Start with the work and repeated questions.
Do not begin by migrating every document.
Choose the trusted sources.
Mark what is current, duplicated, uncertain or obsolete.
Design for retrieval and action.
Organise answers around the work people need to do.
Make ownership visible.
Name who can approve, change and retire information.
Test with real questions.
Find out whether people can retrieve and use the answer without extra explanation.
Add AI carefully.
Retrieval or drafting can help only when the underlying information and review are good enough.
Ways to get help
- Use it: Complete the free Knowledge Handover Checklist.
- Work it through: Use a Working Session to choose a source of truth, owner or first knowledge area.
- Build it in: Use a Capability Sprint to structure, test and embed a usable knowledge system.
Start with the question people keep asking.
Describe the answer that is hard to find, the person everybody depends on or the work that becomes fragile when somebody is away.