Knowledge gap definition
A knowledge gap is missing, incomplete, outdated, or inaccessible information that prevents someone from understanding a situation, making a sound decision, or performing important work. In a handover, it is the difference between what the next owner needs to know and what has been transferred successfully.
Where knowledge gaps appear
Knowledge gaps often hide between documented steps. A procedure may say what to do without explaining the trigger, expected result, exception path, or person authorized to decide. The document exists, but the next owner still cannot act confidently.
Gaps also appear when correct information exists but is inaccessible, scattered, out of date, or understandable only to its author.
Knowledge-gap example
A departing account manager provides customer contacts, contract links, and renewal dates. During review, the new owner cannot determine why the customer received a nonstandard service commitment or who approved it. That missing decision context is a high-priority gap because it could affect the next renewal conversation.
Closing a knowledge gap
Name the unanswered question, its impact, the person most likely to answer it, and the date by which it matters. Use knowledge extraction for knowledge still held by an expert, then capture the answer in its durable home.
Finally, use knowledge validation or receiver-led practice to confirm that the gap is truly closed rather than merely marked complete.
Frequently asked questions
What are examples of knowledge gaps?
Examples include an undocumented exception, a decision with no recorded reasoning, a recurring deadline known by only one employee, missing system access instructions, an unidentified stakeholder, or a procedure that omits how to verify the result.
How do you identify a knowledge gap?
Compare critical responsibilities with the available knowledge, ask targeted follow-up questions, review recent exceptions and decisions, and have another person try to explain or perform the work. Unanswered questions and failed practice reveal gaps more reliably than document length.
How should knowledge gaps be prioritized?
Prioritize by business impact, urgency, likelihood of disruption, number of people who hold the knowledge, and difficulty of reconstruction. Resolve gaps tied to critical operations, compliance, customers, safety, or near-term deadlines first.