Could Rovo detect organizational knowledge gaps before people notice them?

[AGASTYA SHARMA]

Instead of answering questions, should Rovo proactively identify:

undocumented processes,

isolated teams,

missing documentation,

duplicated knowledge,

outdated ownership.

Could AI eventually become a knowledge architect instead of just a search assistant?

[Martin Runge · Accepted solution]

Hi @AGASTYA SHARMA

Great question, and it is closer to reality than it might sound.

Parts of this already exist today. In JSM, Rovo's knowledge base management skill (/manage-knowledge-base) clusters recent tickets and shows you knowledge gaps and high-impact topics along with actual ticket volumes, so it already flags missing documentation based on demand rather than waiting for someone to complain.

I am just starting to explore KCS, which is related to your question, and I have posted an article about it: Making Knowledge-Centered Service Real in Jira Service Management 

Cheers,
Martin

[Dr Valeri Colon _Connect Centric_]

@AGASTYA SHARMA Martin’s example is a good proof point. Rovo can already identify knowledge gaps in JSM based on request patterns. The broader vision—finding duplicate knowledge, stale ownership, isolated teams, or undocumented processes across the whole organization—isn’t a documented general capability yet, but Teamwork Graph gives Atlassian the data foundation to move in that direction.