Imagine starting a new job and having a question about how to do something. You ask a coworker. They send you a PDF. You ask another coworker the same question a week later. They send you a different PDF — a slightly older version with different steps. You check the shared drive and find three more documents on the same topic, all saved in different folders, all with different dates. None of them are labeled as the “official” version.
Sound familiar?
If this scenario makes you cringe, you’re not alone. And if it doesn’t, I’d argue you just haven’t noticed the problem yet.
I’ve worked for companies of all sizes — large enterprises, mid-size organizations, and small operations. Different industries, different cultures, different challenges. But there is one thing that has been remarkably consistent across every single one of them: knowledge management is a struggle. It doesn’t matter how sophisticated the tech stack is or how talented the people are. When there is no system for organizing, maintaining, and distributing institutional knowledge, the same problems show up everywhere.
The Problem Is More Common Than You Think
Knowledge management breakdowns rarely happen because people aren’t creating information. In fact, the opposite is usually true. People are creating too much, in too many places, with no coordination.
Departments build their own resources in silos. One team has a SharePoint site. Another uses a shared drive. A third keeps everything in email threads. Individual employees — often the most dedicated and well-intentioned ones — create their own job aids, cheat sheets, and quick-reference guides. Sometimes they share these with a few peers. Sometimes they share a different version the next time someone asks. And almost never do those resources make it into a centralized location where the entire organization can benefit from them.
The result? You end up with an organization that technically has a lot of documentation but functionally has no idea what’s accurate, what’s current, or what even exists. People spend more time searching for information than actually using it. New hires piece together processes from fragmented sources. And when someone who “just knows how things work” leaves the company, they take all of that institutional knowledge with them.
This isn’t just an inconvenience. It’s a real cost — in onboarding time, in errors, in duplicated work, and in the slow erosion of trust when employees can’t find reliable answers to do their jobs well.
Why I’ve Always Gravitated Toward This Work
For as long as I’ve been in L&D, I’ve been building knowledge management solutions. Not because anyone asked me to — but because I kept seeing the same gap and couldn’t ignore it.
At one organization, I developed standard operating procedures for hundreds of locations covering food safety and cleaning protocols. The challenge wasn’t just writing the procedures — it was making sure that every location had access to the same version of the truth, and that when regulations changed, every single document could be updated in one place and reflected everywhere immediately. But the impact went beyond just having documents on a shelf. Those SOPs became the foundation for how we trained new employees. Instead of relying on institutional knowledge passed down informally from one team member to the next — with all the inconsistencies that come with that — we had a single, authoritative set of guidelines that every location used to onboard and train their staff. It improved compliance across the board because everyone was learning and performing from the same playbook. And in an industry that runs around the clock, those resources were available at 2 a.m. on a Saturday night when there was no manager to call. The knowledge base didn’t clock out.
At another, I standardized document formatting and workflow procedures. People were doing the same work in completely different ways, not because one way was better, but because no one had ever documented and shared a consistent approach. Once we did, it didn’t just improve efficiency — it gave people confidence that they were doing things the right way. New hires could follow a clear, documented process from day one instead of spending their first few weeks piecing together how things worked from five different coworkers. Existing employees got faster because they stopped second-guessing themselves or reinventing steps that had already been figured out. The standardized resources became the training materials and the on-the-job reference all in one.
In another role, I created a centralized resource hub for field employees driving trucks. These were people out on the road every day, often working early mornings, late nights, and weekends, who needed quick, reliable access to procedures and guidelines without having to call someone at the home office or dig through a cluttered folder on their phone. Having a single, organized location for that information changed the way they worked. It meant that whether a driver was on their first week or their tenth year, they had the same access to the same accurate information — at any hour, from anywhere. It supported 24/7 operations in a way that no amount of classroom training alone ever could, because the resources were always there at the moment of need.
In every one of these situations, I came into the role, saw the need, and built the solution. No one posted a job description that said “create a knowledge management system.” But when you see people struggling to find the information they need to do their jobs — when you watch the same questions get asked and answered differently every time — the need becomes obvious. And once you build it, the ripple effects are hard to miss: onboarding gets faster, training gets more consistent, compliance improves, and employees become more efficient because they spend less time searching and more time doing.
Think of It as Google for Your Employees
Here’s how I think about knowledge management: it should be Google for your employees.
Think about how you use Google in your personal life. You have a question, you search for it, and you get an answer. You don’t have to know which website the information lives on. You don’t need to call someone and wait for a response. You don’t need to remember where you saw that article three months ago. You just search, find, and go.
Now think about how your employees find information at work. They probably have to know which folder to look in, which version of a document is current, or which coworker to ask. That’s the gap. A well-built knowledge management system closes it. Employees should be able to go to one place, search for what they need, and trust that what they find is accurate and up to date.
This matters for more than just convenience. When employees can quickly and confidently access the information they need, it fundamentally changes how they learn and perform on the job. Knowledge management is not separate from training and development — it’s an essential part of it. A solid knowledge base becomes the backbone of your curriculum development strategy. It’s where your standard operating procedures live, where your job aids are housed, where your onboarding resources are organized, and where your ongoing learning materials connect back to real-world application.
Without that foundation, training becomes disconnected from practice. You can deliver a great onboarding program, but if employees can’t find the resources they need once they’re on the job, the training doesn’t stick.
Knowledge management is the bridge between learning something in a classroom or course and actually applying it day to day. It’s where formal training meets on-the-job performance support — and that intersection is where real capability gets built.
When “It’s All in One Place” Isn’t Enough
I once walked into an organization where the files were largely in one area. So that’s knowledge management, right?
Not so fast.
Yes, the documents were on a shared drive. But they were spread across dozens of folders with little to no consistent organization. Files dated back years — some from 2019, some from last month — all sitting side by side with no clear indication of which was current. Different people used different naming conventions. Different teams used different templates. Some documents had been updated multiple times with no version tracking. Others hadn’t been touched in years but were still being referenced as if they were current.
The real problem became clear when I started asking people for specific processes. I’d ask one person and get a document. I’d ask someone else the same question and get a completely different document — sometimes even from the same person who had sent me something different previously. No one was being careless. The system itself just made it nearly impossible to know what was accurate.
Having everything in one drive isn’t knowledge management. That’s just storage. Knowledge management is about structure, ownership, accuracy, and accessibility. It’s the difference between a filing cabinet stuffed with papers and a well-organized library with a catalog system.
Getting Buy-In: How to Have the Conversation
So if the problem is this widespread, why doesn’t every organization just fix it? Because getting leadership to prioritize knowledge management is often the hardest part. Not because leaders don’t care, but because they don’t always see it as a priority when there are more visible fires to put out. So how do you make the case?
Start with the pain they already feel. Every organization has symptoms of poor knowledge management even if they don’t call it that. Onboarding takes too long. Employees keep asking the same questions. Different teams follow different processes for the same task. Compliance gaps keep surfacing. Customer-facing teams give inconsistent answers. These aren’t separate problems — they’re all symptoms of the same root cause, and framing it that way helps leadership see the scope of what a knowledge management system actually solves.
Then bring the numbers, because they’re hard to argue with. According to McKinsey, the average employee spends 1.8 hours every day just searching for and gathering information. That’s roughly 20% of a full work week spent not doing their actual job. Employees spend an average of 21% of their work time searching for knowledge and another 14% recreating information they couldn’t find. Think about that — over a third of your workforce’s time is going toward finding or rebuilding things that should already be accessible. IDC estimates that an enterprise with 1,000 knowledge workers wastes $2.5 to $3.5 million per year searching for information that doesn’t exist, failing to find information that does, or recreating information that can’t be located. On the flip side, McKinsey’s Global Institute Report found that a well-implemented knowledge management system can reduce information search time by up to 35% and boost organization-wide productivity by 20–25%.
You don’t need to walk into a meeting with a full business case on day one. Sometimes the most effective approach is simply connecting the dots for people. Pull up a few of those conflicting documents you’ve found. Show the inconsistency. Ask the team, “Which one of these is the current version?” and watch the silence in the room. That moment of realization is often more persuasive than any slide deck. From there, you can propose a small pilot — one department, one process area — and let the results speak for themselves. Once people see the difference a structured system makes in one area, the conversation shifts from “why should we do this?” to “how fast can we expand it?”
How I Built the System
So I got to work. I didn’t start by reorganizing folders or moving files around. I started by defining what a knowledge management system actually needed to look like for this organization.
The first step was establishing a framework for every document in the system. Each resource needed clearly defined attributes: a document owner who was responsible for its accuracy and maintenance, a defined audience so people knew who the resource was intended for, a review cycle with specific dates so nothing could silently go stale, a version history so we could track what changed and when, a clear categorization so resources could be found intuitively rather than by memorizing folder paths, and — critically — a defined approval chain. The person who owns a document isn’t always the person who approves it. In some organizations, the subject matter expert drafts and maintains the content, but a director, a VP, or even the CEO needs to sign off before it goes live. That approval structure varies from company to company and sometimes even from document to document, and learning how it works within your organization is one of the first things you need to figure out. If you don’t build that into the review and approval process from the start, you end up with content that’s either bottlenecked waiting for sign-off nobody knew was required, or published without the oversight it needed.
Once the framework was in place, I worked through the existing content — auditing what we had, identifying what was outdated or redundant, consolidating duplicate resources, and filling in gaps where critical processes had never been formally documented. This part takes time and it takes collaboration. You need subject matter experts to validate content. You need stakeholders to agree on ownership. And you need leadership to support the idea that this is worth investing in.
The result was a centralized knowledge base where every resource had a single source of truth. When I need to share a procedure with a location or a team, I link to the document in the knowledge base. I don’t send a copy. I don’t attach a file. I link to it. That means when I update that document — whether it’s a minor revision or a major overhaul — every person who has ever been given that link is now looking at the current version. There’s no chasing down old copies. There’s no wondering if someone is working off a version from six months ago. One update, reflected everywhere, instantly.
This also changed how we think about accountability. With assigned document owners and scheduled review dates, resources don’t just sit there collecting dust. There’s a system in place that prompts reviews, flags content that’s approaching its review date, and ensures that the knowledge base stays living and current rather than becoming another digital graveyard of outdated files.
The Best Part? Most People Don’t Even Notice the Difference
And honestly, that’s how you know it’s working.
Most of our employees don’t think about the knowledge management system as a “system.” They just know that when they need a procedure, they go to one place and find it. They don’t have to wonder if it’s the right version. They don’t have to email someone and wait for a response. They don’t have to dig through a cluttered shared drive hoping they find the right folder. And they’re not overwhelmed by content that has nothing to do with their role.
That last point matters more than people realize. A well-structured knowledge management system doesn’t just organize information — it controls what each person sees. A field technician doesn’t need access to corporate accounting procedures. A new hire in customer service doesn’t need to sift through engineering documentation to find their call scripts. When you can scope the experience so that employees only see the resources relevant to their role, their location, or their department, you eliminate the noise. They’re not searching through hundreds of documents trying to figure out which ones apply to them. They see what they need, and nothing else.
They just go, find what they need, and get back to work.
That seamlessness is the goal. The best knowledge management systems are invisible to the end user. They feel like Google — simple, reliable, and always there when you need them. The complexity is behind the scenes — in the framework, the governance, the review cycles, the ownership structure, and the audience scoping that makes sure each person’s experience is clean and relevant. But the experience for the employee is effortless.
That’s the return on investment that’s hard to put on a spreadsheet but impossible to ignore once you’ve seen it in action. Fewer support tickets. Faster onboarding. More consistent performance across locations and teams. Less time wasted searching and more time spent doing.
The Future: Knowledge Management Meets AI
Here’s where it gets exciting.
Everything I’ve described so far — the centralized system, the single source of truth, the structured and maintained content — is valuable on its own. But it’s also the foundation for something much bigger.
We’re entering an era where AI can sit on top of your knowledge base and become the interface between your employees and your institutional knowledge. Imagine an employee doesn’t just search for a document — they ask a question in plain language: “What’s the process for handling a customer return at my location?” And an AI-powered tool, trained on your centralized knowledge base, gives them the exact answer, pulled from the most current version of the right procedure, tailored to their role and location.
That’s not a hypothetical. That technology exists today. But here’s the thing: it only works if your knowledge base is worth connecting to. If your content is scattered, outdated, contradictory, and unstructured, plugging AI into it won’t solve the problem — it will amplify it. You’ll get confident-sounding answers based on bad information, which is arguably worse than having no system at all.
Think of it this way: the knowledge base is the library, and AI is the world’s best librarian. But even the best librarian can’t help you if the library is full of mislabeled, outdated books shelved in random order.
A well-built knowledge management system isn’t just useful right now. It’s the prerequisite for everything that comes next. It’s the data layer that AI needs to actually be helpful.
This is why I say that knowledge management is crucial to the future and scalability of any organization. The companies that invest in organizing, structuring, and maintaining their institutional knowledge today are the ones that will be able to deploy AI-powered tools tomorrow — tools that can answer employee questions instantly, write out processes on demand, surface relevant training materials at the moment of need, and turn your knowledge base into what it was always meant to be: the new Google for your organization.
So Where Do You Start?
If you’re reading this and recognizing your own organization in these descriptions, here’s my honest advice: don’t wait for someone to ask you to build a knowledge management system. Start now. Start small if you have to, but start.
Audit what you have. Where does information currently live? Who creates it? Who maintains it? How do employees find it today? Understanding the current state — even if it’s messy — is the first step toward building something better.
Define your framework. Every document needs an owner, an audience, an approval chain, a review cycle, and a home. You don’t need a fancy platform on day one. You need a structure and the discipline to follow it.
Consolidate. Eliminate duplicate resources. Retire outdated content. Establish a single source of truth for every process, procedure, and policy. This is the hardest part because it requires collaboration and sometimes difficult conversations about who owns what. But it’s also the most important part.
Think ahead. Build your knowledge base with the understanding that it’s not just for today. It’s the foundation for AI integration, for scalable training, for consistent performance, and for an organization that can grow without losing the knowledge that makes it run.
The organizations that will lead in the next five years aren’t just the ones with the best technology — they’re the ones with the best-organized knowledge. Start building that foundation today.
If this resonates with you or your organization is facing these challenges, I’d love to hear about it. Knowledge management is one of those topics that doesn’t get enough attention until the pain becomes too obvious to ignore. Let’s change that.
References
- Chui, M., Manyika, J., Bughin, J., Dobbs, R., Roxburgh, C., Sarrazin, H., Sands, G., & Westergren, M. (2012). The social economy: Unlocking value and productivity through social technologies. McKinsey Global Institute. https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-social-economy
- Panopto & YouGov. (2018). Workplace knowledge and productivity report. Panopto. https://www.panopto.com/resource/valuing-workplace-knowledge/
- Feldman, S., & Sherman, C. (2001). The high cost of not finding information [White paper]. International Data Corporation (IDC). https://www.idc.com
