AI-Led Knowledge Management: Building Scalable Enterprise Knowledge Infrastructure
Key highlights
- Every organisation past a certain size runs into the same wall: knowledge is everywhere, and somehow it's nowhere at all.
- A recent engagement with a global philanthropic foundation shows what this actually looks like when the scope is right from the start.
- Those 21 use cases weren't a theoretical exercise dreamed up in a workshop.
The Knowledge Problem That Isn't Going Away
Every organisation past a certain size runs into the same wall: knowledge is everywhere, and somehow it's nowhere at all. Documents scatter across SharePoint sites, Teams channels, shared drives, someone's personal OneDrive, and notebooks only the original author could ever find again. Progress updates live buried in email threads. And the knowledge that actually matters most, the reasoning behind a decision, the lessons pulled from something that failed, tends to live in one person's head and vanish the day they leave.
Most knowledge management efforts treat the symptoms and leave the underlying structure untouched. Someone imposes a taxonomy. A SharePoint site gets reorganised. Teams get told to document things in some new format going forward. Six months later, the same chaos has crept right back in, because whatever incentives and workflows created the mess in the first place never actually changed.
What actually shifts the outcome isn't a new filing convention. It's a genuine structural change in how knowledge gets created, captured, and found again, paired with technology that keeps that change sustainable without demanding constant heroics from people who already have full-time jobs to do.
Done well, knowledge management isn't really a system you install. It's a managed capability that grows with the organisation and gets more valuable the longer it runs.
What an AI-Led Knowledge Management Engagement Actually Looks Like
A recent engagement with a global philanthropic foundation shows what this actually looks like when the scope is right from the start.
The starting point was familiar enough. Disaggregated knowledge assets, folder structures that didn't match from team to team, documents named differently depending on who created them, and progress reporting that existed in some corners of the organisation and simply didn't in others. Most organisations in this spot try to clean up what's already there. CMI's instinct went the other way, understand what should exist first, then build the infrastructure to actually sustain it.
Four pillars held the work together. AI-led knowledge transformation came first, using AI to audit existing knowledge assets, spot the gaps, standardise taxonomy and naming, and migrate content into something coherent, all at a scale and speed that would have been genuinely impractical by hand. Reporting integration turned out to matter more than expected. For this particular organisation, knowledge management and internal progress reporting were deeply tangled together, KPI tracking and program reporting weren't separate from the knowledge infrastructure, they were part of it. Bringing both into one unified approach expanded the scope of the engagement considerably and the value along with it.
Change management was the third pillar, and arguably the one that determines whether any of the rest sticks. No AI system changes how people actually work. Only people do that. CMI's domain experts led that process directly, working with teams on the ground, supporting adoption, and building the habits that keep a knowledge system running on its own rather than collapsing the moment attention moves elsewhere.
The fourth pillar was an agentic AI roadmap. Rather than dropping in a generic AI tool and hoping it fit, the team ran a full assessment of the organisation's knowledge management use cases, mapping 21 distinct scenarios across how the client's teams actually worked day to day, and built a prioritised roadmap for where agentic AI would create the most value and how to get there.
What 21 Use Cases Actually Revealed
Those 21 use cases weren't a theoretical exercise dreamed up in a workshop. Each one was grounded in something real: what knowledge a team actually needed, where they'd realistically go looking for it, what happened when they couldn't find it, and what that friction actually cost them in time and rework.
What came out of the assessment was a genuinely differentiated picture, some needs were already covered by existing tools like Microsoft Copilot, some could be handled with CMI accelerators already in place, and some needed purpose-built agentic solutions that didn't exist yet. The result wasn't a wish list. It was a sequenced plan, starting with quick wins and building steadily toward more sophisticated agentic infrastructure over time.
Two agents got prioritised as the first quick wins, chosen specifically because they addressed the highest-friction points in the workflow that nothing else, Copilot included, could actually handle.
The first was an inbox knowledge harvester, an agent that monitors and processes email threads to surface and pull out the knowledge buried inside everyday communication. It identifies relevant documents, decisions, and insights shared over email, structures them against the organisation's taxonomy, and routes them into the knowledge base automatically. The inbox turns out to be one of the largest stores of institutional knowledge in any organisation, and one of the most consistently ignored by conventional knowledge management approaches. Privacy was built into the design from day one here, the agent is scoped to defined mailboxes and content types, excludes personal and sensitive communication entirely, and operates strictly within the organisation's existing data governance policies.
The second was a nudging agent, built into existing workflows to prompt knowledge capture at the exact moment knowledge actually gets created, at the close of a meeting, when a milestone wraps up, once a key decision gets made. Instead of asking people to document things retrospectively once the context has already faded, this agent creates low-friction capture opportunities right in the flow of work, while the information is still fresh and actually worth writing down.
The two agents prioritised here go straight at the knowledge gaps that neither existing tools nor internal teams had the bandwidth or expertise to solve on their own. That's really where the value sits, not in rebuilding what already exists somewhere, but in extending what's actually possible.
From a Single Team to a Program
Treat knowledge management like a one-off project, a single clean-up of SharePoint, and the results don't last. Teams drift back to old habits. New knowledge piles up in new corners. The same problem resurfaces eventually, usually sooner than anyone expects.
Treat it instead as a managed service, with ongoing governance, a live roadmap of agentic AI improvements, and a partner actually responsible for sustaining and evolving the capability over time, and the results compound instead. Every new use case added builds on infrastructure that's already there. Every team that adopts the program extends its reach a little further. That's exactly what's playing out with this client right now, the initial engagement is already generating interest from three to four additional teams inside the same organisation.
For a large organisation juggling hundreds of programs and dozens of internal teams, that's the real difference between a knowledge initiative that fades out and a knowledge infrastructure that becomes a genuine organisational asset worth investing in further.
Why This Applies Well Beyond One Foundation
None of this is unique to philanthropic foundations. The same pattern, scattered assets, inconsistent structure, and critical knowledge trapped in exactly the wrong place, shows up in every enterprise across every industry, without much variation.
What makes the problem genuinely solvable now is the combination of AI agents that can work at real scale alongside domain expertise that actually knows what good looks like. Agents can process and organise content at a volume no team of human analysts could ever match, ingesting documents, applying taxonomy, routing knowledge assets, and triggering capture prompts across an entire organisation all at once. But an agent is only ever as good as how it's configured. Without someone who understands the domain, the organisational context, and the governance requirements underneath it, an agent optimised for the wrong thing just produces noise at scale rather than knowledge at scale, which is arguably worse than doing nothing at all.
That's exactly why the Human-in-the-Lead model isn't a constraint on what these agents can do. It's what actually makes them useful in the first place. CMI domain experts define what each agent is looking for, set the quality thresholds, manage the lifecycle as the organisation evolves, and step in personally whenever an edge case needs judgment. No agent should ever be left to make it alone.
That kind of work needs people who genuinely understand the domain, understand the organisation, and are committed to the outcome, not just to delivering something and moving on. That's the human-in-the-loop model applied to knowledge management specifically. And it's really what separates a knowledge management initiative that works for a year from a knowledge management capability that keeps working indefinitely.

Shraddha Wankhade
Lead ConsultantShraddha Wankhade is a Lead Consultant at Custom Market Insights, specializing in market research, business consulting, competitive intelligence, and strategic advisory. She delivers customized research and actionable insights that help organizations identify opportunities, make
View profile and reports