Knowledge Management Is NOT About Delivering the Right Information to the Right People at the Right Time. Moving beyond classic KM thinking

Knowledge Management is still widely framed as delivering the right information to the right people at the right time. That framing reduces knowledge to content and turns a human practice into a technical delivery problem. A more useful view treats knowledge as something that emerges through interpretation, conversation, judgement, and action.

A familiar definition surprisingly still circulates in organisations and Knowledge Management literature:

Knowledge Management is about getting the right knowledge to the right people at the right time.

Or alternatively:

Knowledge Management is retrieving the right information, for the right people, at the right time.

It sounds reasonable. It sounds efficient. And it is also deeply misleading.

At best, this is a description of Information Management. At worst, it distorts how knowledge actually works in human systems.

Knowledge is not something you deliver

This definition quietly treats knowledge as a thing. Something that can be stored, indexed, retrieved, and delivered on demand. In doing so, it conflates knowledge with information.

Information can be retrieved. Documents, data, and artefacts can be moved from one place to another. But knowledge does not reside in repositories. It lives in how people interpret information, how they connect it to experience, how they exercise judgement, and how they act in a situation.

Two people can be given the same document at the same time and walk away with very different understandings. In such cases, nothing meaningful has been “managed” simply because something was delivered.

Retrieval moves artefacts. Knowing emerges only when people engage with them. This does not mean retrieval is irrelevant. It means it is never sufficient on its own.

“Right” does far more work than it can sustain

The word “right” conveys an illusion of certainty that rarely holds in practice.

Who decides what information is right? Before people begin exploring a problem, they often do not yet know what they need. Needs emerge through inquiry, testing, conversation, and engagement with the situation itself. They are rarely clear in advance.

Who decides who the right people are? Knowledge does not flow neatly along organisational charts. Some of the most valuable insights arise when information reaches people who were not originally intended to receive it, people who bring different backgrounds, ask unfamiliar questions, or notice patterns that others overlook.

And the right time? In complex and uncertain work, the right time to understand something is often long before it becomes urgent. By the time information is formally requested, the opportunity for calm reflection may already have passed.

All three versions of “right” rest on the same assumption, that needs, roles, and timing can be predicted in advance. In practice, they often cannot.

A passive and reactive view of knowledge work

Retrieval is inherently reactive. It waits for a question and then supplies an answer.

But much of knowledge work is generative rather than reactive. New understanding forms when people combine ideas, test assumptions, notice tensions, and reflect together. Insight often comes from juxtaposition, from conversation, from seeing things side by side that were never designed to meet.

The most valuable knowledge is rarely fetched on demand. It is formed through engagement over time.

Systems designed primarily for retrieval tend to optimise for precision, control, and efficiency. They do far less to support exploration, curiosity, or the kind of productive wandering from which new understanding often emerges.

The human dimension cannot be added later

Framed this way, Knowledge Management becomes a technical problem. Get the systems right, and knowledge will flow.

But knowledge does not move independently of people. It is mediated by trust, shared context, motivation, and relationships. Much of what matters most is tacit, embodied, and situational. You cannot extract years of experience, intuition, or practical judgement from a document and make it fully searchable.

In practice, Knowledge Management is at least as much about connecting people as it is about connecting people to information. When this is treated as a secondary concern, the entire effort becomes brittle.

Timing, memory, and forgetting

The emphasis on just-in-time delivery also reverses how understanding actually develops.

Good knowledge work builds familiarity over time. It creates shared memory, background awareness, and a surplus of insight that people can draw on when conditions shift. Often, the right time to know something has already passed.

Equally important is forgetting. Organisations accumulate information far faster than they shed it. Outdated assumptions, obsolete practices, and irrelevant material create noise that obscures what matters. A serious approach to knowledge must include pruning, letting go, and deciding what no longer deserves attention.

Retrieval-centred definitions leave little room for this.

From artefacts to capability

Perhaps the deepest limitation of the retrieval definition lies in what it aims to optimise.

It focuses on moving information efficiently. But the real purpose of Knowledge Management is to build organisational capability. The capacity to learn, to think together, to adapt, and to make better judgements under uncertainty.

The more useful question is not “Can we find what we stored?” but “Are we becoming more capable in how we act?”

When knowledge is treated primarily as something to be delivered, organisations invest in repositories and search tools. When knowledge is understood as something that emerges through interaction, attention shifts to conversation, reflection, learning practices, and the conditions under which meaning can form.

That shift is not cosmetic. It changes what we design for, what we value, and what we pay attention to.

Seen in this light, the familiar definition does not describe Knowledge Management as such. It describes a narrow and incomplete view of information handling.

Knowledge is not retrieved. It takes shape in use. It is enacted in judgement, conversation, and action.

Why SharePoint is not a knowledge management system

Tools like SharePoint are often described as Knowledge Management systems, but they are better understood as Information Platforms. They store, organise, and distribute documents. They do not create understanding.

SharePoint can support knowledge work, but only indirectly. Knowledge emerges when people interpret what they find, talk it through with others, test it in practice, and apply judgement. No platform can do that on their behalf.

When Knowledge Management is reduced to delivery, tools like SharePoint are mistaken for the solution. They are part of the infrastructure, not the work itself.

SharePoint Is Not a Knowledge Management System

How software systems confuse information with knowledge

Many organizations rely on SharePoint to manage what they call knowledge. The problem is that storing documents and supporting communication and coordination is not the same as sharing understanding. Real knowledge work happens through people, relationships, and conversations, not within folders and files. Continue reading

If we continue to treat knowledge as something to be retrieved, we will continue to invest in systems that move information but leave understanding untouched. We can instead design for learning. This means paying attention to how we think together, how insight forms, and how knowledge manifests in everyday practice.