Ask a room of executives whether their company has a knowledge management strategy, and a surprising number will point to the intranet. It’s the natural answer. There’s a homepage, a document library, a directory of teams and people. It looks like where knowledge lives. But an intranet solving a communication problem and a knowledge management system solving a knowledge problem are answering two different questions, and organizations that treat them as the same thing usually end up with neither working well.
What each one is actually built to do
An intranet is, at its core, a communication and access platform. It’s where news gets posted, policies get published, and employees find each other. Its job is distribution: getting information from wherever it’s created to wherever it needs to be seen. That’s a genuinely valuable function, and a well-built intranet does it efficiently.
A knowledge management system is built around a different problem entirely: capturing, structuring, and making retrievable the knowledge that lives in people’s heads and experience, not just the documents that already exist in finished form. The distinction goes back to a foundational idea in KM theory, developed from philosopher Michael Polanyi’s work: information is what can be articulated and written down, while a meaningful share of what people actually know in their work is tacit, uncodified, and doesn’t transfer just by being posted somewhere.
An intranet is very good at distributing the first kind. It’s structurally unequipped to handle the second, because publishing a document and capturing someone’s judgment are not the same act, even when they happen on the same platform.
Where the confusion actually costs you
The gap between “we have a place to put information” and “we can find the right information when we need it” shows up as time, and the numbers are not small. Research from the McKinsey Global Institute found that knowledge workers spend roughly 20 percent of their workweek, close to a full day, searching for and gathering information rather than using it. Other industry estimates put the figure even higher once scattered tools and duplicate systems are factored in. Every one of these studies points to the same root cause: information exists somewhere in the organization, but the system it lives in wasn’t built to make it findable by the person who needs it, when they need it.
An intranet without a real information architecture behind it makes this worse, not better, because it becomes one more place content gets posted and then buried. Nielsen Norman Group’s research into intranet navigation, based on a study of over 120 corporate intranets, found that navigation and findability problems are the norm rather than the exception: most intranets accumulate content faster than anyone maintains the structure around it, and the resulting sprawl is what makes them feel, to employees, like the last place they’d look for something specific and reliable.
The overlap is real, which is exactly why the confusion persists
The two aren’t unrelated. Jakob Nielsen’s long-running analysis of top-performing intranets found that the best ones do incorporate real knowledge-sharing functions: connecting employees to the specific people who hold expertise, not just to documents, and building in ways for tacit insight to surface through discussion and comment rather than static pages alone. When an intranet is designed with this in mind, it can function as the front door to an organization’s knowledge, even if it isn’t the knowledge management system itself.
That’s the healthiest version of the relationship: the intranet as interface, and a more deliberate knowledge management layer, whether that’s a structured knowledge base, a taxonomy-driven repository, or a set of communities of practice, doing the actual work of capturing and organizing what the organization knows. Many effective organizations run exactly this way, with the intranet as the front-end and a purpose-built knowledge system underneath it.
The practical question to ask before buying either
Most organizations don’t fail because they chose the wrong platform. They fail because they never separated the two problems in the first place, and bought a single system expecting it to solve both. Before investing in either, it’s worth asking which problem is actually unsolved:
- If employees can’t find company news, policies, or basic operational information, that’s a communication and access problem. An intranet, well-structured, addresses it directly.
- If employees can find documents but still can’t get a straight answer about why something was decided a certain way, or what an expert would do in a specific situation, that’s a knowledge problem. No amount of intranet redesign fixes it, because the knowledge in question was never explicit to begin with.
- If both problems exist at once, which is common, the fix is not one platform doing double duty. It’s a clear architecture where the intranet handles distribution and a separate, deliberate knowledge management effort handles capture, structure, and tacit knowledge transfer.
The takeaway
An intranet answers “where do I find this.” A knowledge management system answers “how do I know what someone else already learned.” Both are legitimate, valuable investments. The mistake isn’t building an intranet. It’s assuming that building one means the knowledge problem has already been solved.
Subscribe to receive notifications for free webinars on Knowledge Management.