These signs help locate a knowledge problem; they are not a scoring system or proof that an AI purchase is required. Observe recurring work, identify the source of friction and test whether better documentation, search or an assistant addresses it.
1. Finding and verifying information takes repeated effort
Watch a recurring question from start to accepted answer. Record where the user searches, how they identify the current version and how much checking is needed. Slow search may reflect poor naming, inaccessible files or missing content. There is no universal minute threshold; compare improvement against your own workflow.
2. New colleagues repeatedly need the same explanations
Ask a new colleague which questions repeatedly require another person's help. Separate missing instructions from training and experience that a document cannot replace. Create maintained guidance for the repeatable parts and test whether a newcomer can find and apply it. An assistant can help navigate evidence, but does not guarantee immediate competence.
3. You’ve Tried AI but Got Generic Answers
Inspect a generic or incorrect AI answer together with the input and retrieved sources. Did the user supply the necessary context? Was the current policy accessible? Did the tool retrieve the right passage? Better prompts, source repair and retrieval changes address different causes. A weak answer alone does not diagnose a missing KB.
4. Knowledge Leaves When People Leave
Identify decisions and procedures that depend on one person's memory. Document the rationale, exceptions and responsible role, then have another colleague validate them. Assign a continuing owner after a handover. Capturing knowledge once is not enough: the record can become obsolete as products, customers and processes change.
5. Sources conflict across systems
Multiple platforms are not inherently a problem. Conflicting versions and unclear ownership are. Map where each authoritative record lives and how users discover it without crossing permission boundaries. Federated search may be sufficient; consolidation is another option. Choose by source quality and maintenance rather than an arbitrary platform count.
What Happens When You Build the Foundation
Test whether the new arrangement reduces search and correction effort while preserving answer quality and access. Include maintenance in the assessment. The linked public case describes a project, but its measurement protocol is unpublished; do not use its reported outcomes as your forecast. Keep evidence from your own pilot.
Not Sure Where to Start?
Choose a recurring task and list its required sources, owner, users and unresolved questions. The linked guides explain why a knowledge layer can help and how to structure it. An audit should produce a scoped plan and acceptance criteria; agree its schedule after the source inventory and access constraints are known.