Understanding the Distinction Between Data, Information, and Knowledge in Knowledge Management

Every organization today sits on a mountain of facts, figures, and records. Yet very few manage to turn that raw material into the kind of insight that drives smart decisions. The reason often comes down to a confusion many people share: treating data, information, and knowledge as if they were the same thing. They are not. In knowledge management, understanding how these three concepts differ, and how one transforms into the next, is the foundation for everything else. This post breaks down the distinctions, explains the human cognition that sits at the heart of the process, and explores how enterprises handle the different forms knowledge can take.

Defining data, information, and knowledge 🔗

The most widely used framework for separating these concepts is the DIKW hierarchy, which stands for Data, Information, Knowledge, and Wisdom. It is usually drawn as a pyramid, with data forming the broad base and each higher level adding meaning and value to the one below it. The model has been used widely within information science and knowledge management for decades, and it remains the standard starting point for anyone studying the subject.

Let us look at each level in turn.

Data: the raw material 🔗

Data refers to discrete, unprocessed facts about events. These are numbers, characters, and specific or relative values that an organization can gather. On its own, a single piece of data carries no context and no meaning. The number “37” is data. The word “Mumbai” is data. A reading of “98.6” is data. None of these tells you anything useful until something is done with them.

Think of a library issuing books. Each transaction generates raw entries: a member number, a book accession number, a date. These entries are data points. They exist, they are recorded, but they do not yet explain anything.

Information: data with context 🔗

Information emerges when data is organized, structured, and given context. A common shorthand definition is that information is data with a context. Once we connect the raw entries and add meaning, they begin to answer questions like who, what, where, and when.

Returning to the library example, when those transaction entries are processed into a statement such as “Member 1024 borrowed three books on Indian history during the first week of June,” the data has become information. The figures now have relevance and purpose. This stage is essentially about adding context to data while keeping its integrity intact.

Knowledge: information made actionable through experience 🔗

Knowledge is the synthesis of information with experience, expertise, interpretation, and judgment. While information answers what and when, knowledge answers the harder questions of how and why. Knowledge is derived from experience and involves the values and judgments of the people who hold it.

A librarian who notices the pattern of history borrowings, connects it to upcoming university examinations, and decides to reserve extra copies of high-demand titles is applying knowledge. The information about borrowing trends has been combined with professional experience to guide a useful decision. Crucially, this knowledge originates and is applied in the minds of individuals, even though organizations often embed it in routines, processes, and practices.

The role of cognition 🔗

What turns information into knowledge is not a mechanical step. It depends on human cognition. Cognition covers the mental processes that acquire, store, retrieve, transform, or apply information. When a person reads a report, their brain takes in the text, retrieves prior understanding to interpret it, links new ideas to existing ones, and forms beliefs or conclusions. That interpretive work is exactly what separates a stack of information from genuine knowledge.

This is also why the neat upward ladder of the DIKW pyramid is sometimes criticized. Critics argue it can be simplistic and linear, ignoring how much human experience and interpretation matter. Knowledge does not simply fall out of information automatically. It requires a knowing mind to construct it.

The knowee, knower, and knowing process 🔗

Because cognition is central, knowledge creation is best understood as a relationship between three elements rather than a single object you can store on a shelf. In every knowledge situation there are three factors: the knower, the known, and the act of knowing. Without the interplay between the knower and what is known, knowledge cannot arise at all.

The knowee: the subject being studied 🔗

The knowee is the subject matter or phenomenon about which knowledge is created. It can be a physical object, a concept, a process, or a situation. The knowee exists independently, but it only becomes “known” through the effort of someone studying it. In a manufacturing firm, the knowee might be a production line; in a hospital, it could be a patient’s recovery pattern; in a library, it might be the reading behaviour of members.

The knower: the one who interprets 🔗

The knower is the individual or collective entity that engages in creating knowledge. Knowers do not arrive empty-handed. They bring their existing knowledge, experiences, values, and cognitive frameworks to the task of interpreting information. As a result, the same body of information can yield different knowledge in the hands of different knowers.

Several factors shape what a knower produces. Their background knowledge and prior expertise set the limits of what they can interpret. Their cultural and organizational context influences how they read a situation. Their cognitive style affects how they process input. And their motivations and goals direct where their attention falls. In most organizations, knowledge creation involves many knowers collaborating, pooling their perspectives into a shared, collective understanding.

Knowing: the dynamic process 🔗

Knowing is the ongoing process through which a knower engages with information to generate knowledge. It involves observation, interpretation, experimentation, and reflection. This is an important distinction worth holding onto: knowledge is the content of a thought believed to be true, while knowing is the state of mind in which the individual holds that belief. One is the product; the other is the living activity that produces it.

This is why many scholars warn against treating knowledge as nothing more than stored data. There is often too much focus on defining knowledge as a separable object and too little attention to the social and organisational process through which knowledge combines and interacts. For knowledge management to work, the knowing process and the relationships between knowers matter as much as the documents in a repository.

Types of knowledge 🔗

Once we accept that knowledge lives in human minds and processes, a practical problem appears. Some knowledge is easy to write down and share, while a great deal of it is locked inside people’s heads. This leads to the most influential distinction in the field, drawn originally from the philosopher Michael Polanyi, who divided knowledge into tacit and explicit forms.

Explicit knowledge 🔗

Explicit knowledge is knowledge that has been articulated, codified, and recorded. It is systematic and can be expressed in words, numbers, formulas, manuals, databases, and reports. Because it is written down, explicit knowledge is relatively easy to store, copy, transmit, and teach. A library cataloguing manual, a standard operating procedure, or a published research paper are all examples of explicit knowledge. Information systems handle this type comfortably.

Tacit knowledge 🔗

Tacit knowledge is the harder and arguably more valuable kind. It exists in people’s minds and is rooted in personal experience, intuition, and discernment. It is often described as the knowledge that people possess without being fully aware that they possess it, which is why it is so difficult to articulate. A master craftsman’s feel for materials, an experienced manager’s instinct for a negotiation, or a reference librarian’s sense of where to look for an obscure source are all tacit. Polanyi argued that all knowledge has personal and tacit elements, such that it can never be made fully explicit.

Why the distinction matters for enterprises 🔗

For organizations, the central challenge is that the most useful knowledge is often tacit and therefore at risk of walking out the door when an employee leaves. The Japanese scholar Ikujiro Nonaka argued that organizations create and use knowledge through the continuous interaction of tacit and explicit knowledge, a process he called knowledge conversion.

Nonaka and Hirotaka Takeuchi captured this in the well-known SECI model, which describes four modes of conversion. In Socialization, tacit knowledge passes from one person to another through shared experience, observation, and practice, much like an apprentice learning from a master. In Externalization, tacit insight is articulated into explicit concepts through dialogue and documentation, a step often considered the key to knowledge sharing and creation. In Combination, existing explicit knowledge is gathered, sorted, and recombined into new systems such as a database or a strategy document. Finally, in Internalization, explicit knowledge is absorbed back into individuals through learning by doing, becoming part of their personal tacit understanding once more.

These four modes form a continuous spiral rather than a one-time sequence. As individuals share, articulate, combine, and absorb knowledge, the organization steadily expands its collective intelligence. This spiral has been shown to work across education, healthcare, and non-profit organizations because it captures both formal and informal exchanges of knowledge.

Designing knowledge management around the differences 🔗

Recognizing these distinctions has direct practical consequences. An enterprise that wants to manage its knowledge well cannot rely on technology alone. It needs systems for capturing data and information, but it also needs social practices that let tacit knowledge surface through interaction, an organizational culture that rewards sharing, and policies that support the whole effort. Storing files is the easy part. Encouraging people to externalize what they quietly know, and to internalize what others have recorded, is where the real work of knowledge management lies.

In short, data is the raw fact, information is that fact placed in context, and knowledge is information transformed by a human mind into something that guides action. Each level depends on the one below it, but the leap from information to knowledge always passes through a knower. Enterprises that understand this build their strategies around people and processes, not just databases.

What do you think? Looking at an organization you know well, how much of its most valuable knowledge is tacit and locked inside individuals rather than written down? And if a key person left tomorrow, what would it take to make sure their knowledge stayed behind?

References

1. https://en.wikipedia.org/wiki/DIKW_pyramid
2. https://www.manageengine.com/products/service-desk/itsm/dikw-model.html
3. https://damafinland.fi/en/uutiset/dama-finalnd-ry-n-uutiset-27/the-difference-between-dikw-hierarchy-and-data-centricity-3618
4. https://en.wikipedia.org/wiki/Cognition
5. https://medium.com/@paralloid/rescuing-dikw-towards-a-context-centered-model-of-knowledge-7808350c5065
6. https://www.wisdomlib.org/hinduism/essay/prasthanatrayi-swaminarayan-bhashyam-study/d/doc1150548.html
7. https://www.researchgate.net/publication/32018301_Knowledge_knowing_knower_What_is_to_be_managed_and_does_it_matter
8. https://file.scirp.org/Html/4-9900196_31874.htm
9. https://academic-publishing.org/index.php/ejkm/article/view/770
10. https://sites.google.com/view/km101/km-models/nonaka-and-takeuchis-seci-model
11. https://www.researchgate.net/publication/340165842_The_SECI_Model_in_Knowledge_Management_Practices