Topic starter
08/07/2026 6:50 pm
TL;DR: Fragmented knowledge across SharePoint, Confluence, file shares and local repositories pushes employees into repetitive support requests even when the answer exists, according to Efecte. AI knowledge discovery only reduces that pressure when access, provenance and document quality are governed well enough for retrieval to be trustworthy.
Editorial analysis by NHI Mgmt Group, based on content published by Efecte: “AI-assistent för kunskapsutvinning”.
By the numbers:
- 60% minskning av direkta frågor till supportteamen.
Key questions
Q: How should organisations govern AI-assisted knowledge discovery in service teams?
A: Treat it as a content governance problem with identity implications.
Q: Why do employees still open tickets when policy content already exists?
A: Because content availability is not the same as content accessibility.
Q: What are the signs that knowledge discovery is failing in practice?
A: Look for repeated questions, heavy reliance on manual support, and users leaving the self-service flow to search elsewhere.
Practitioner guidance
- Inventory authoritative knowledge sources Map which repositories are allowed to answer employee questions, then identify duplicates, stale pages and orphaned documents that weaken retrieval quality.
- Assign content owners and refresh cadences Tie each policy, SOP and HR knowledge page to a business owner and review cycle so AI retrieval pulls from content that is current and approved.
- Embed self-service into existing workflows Place retrieval where employees already work, such as Teams or the service portal, so question handling does not depend on a separate search journey.
Bottom line: The core issue in AI knowledge discovery is governed access to trusted content, not a shortage of information.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
08/07/2026 7:11 pm
AI knowledge discovery exposes a governance problem before it exposes a UX problem. The article’s real issue is not information scarcity but access fragmentation across repositories that already contain the answer. That makes this a knowledge governance and discoverability problem, not a content creation problem. For practitioners, the control question is whether verified knowledge can be reached consistently enough to replace repetitive tickets.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: Should teams prioritise document governance or AI retrieval first?
A: Document governance comes first. Retrieval can reduce friction, but it cannot compensate for unclear ownership, stale policies or scattered repositories. If the source material is not authoritative, the AI layer simply scales inconsistency and makes poor content easier to consume.
👉 Read our full editorial: AI knowledge discovery exposes the limits of fragmented access