Introduction to KM

Knowledge management hinges on a simple but consequential shift: raw data becomes actionable knowledge only when it’s applied in a specific context. That distinction matters because organizations don’t just need information stored somewhere—they need the right understanding, tied to real decisions, to improve efficiency, productivity, and competitive advantage.

The lecture builds the idea from first principles. Data is unprocessed facts or events—like counting students in a class. When that data is organized into meaningful categories (for example, breaking the class into boys and girls), it becomes information. Knowledge arrives when information is contextual, relevant, and usable for action—such as using the fact that girls make up 20% of students to decide what to do next in that institute. A practical example follows: knowing programming-language syntax is information, but writing a program for a specific customer need creates knowledge because the coding is tied to a concrete purpose and outcome.

Knowledge is also described as having distinct characteristics. It carries an experiential and reflective element: people accumulate capability through experience, and they continually reassess how new information—like a new technology—might affect their organization. It provides leverage, enabling individuals, teams, or organizations to gain a competitive edge and better returns. Just as importantly, knowledge is dynamic. What counts as “current knowledge” changes over time as domains evolve and systems update—illustrated through how search engines like Google surface the latest information in a field.

The lecture further frames knowledge as human capital. Knowledge resides with people, groups, and organizations, and its value depends on how well it’s understood and applied. It contrasts information (organized data) with knowledge (the level of understanding used for decisions and action). A hierarchy is introduced as a pyramid: data and facts sit at the base, information adds meaning, and higher levels move toward intelligence and then wisdom—where wisdom reflects learned outcomes and “enlightenment” from experience.

To make the hierarchy vivid, a cartoon analogy distinguishes information from wisdom using a food-chain scenario: acting on knowledge without deeper insight can produce harmful second-order effects, while wisdom anticipates those consequences. The lecture then classifies knowledge in multiple ways: shallow versus deep (surface familiarity versus learning gained through experience), explicit versus tacit (documented, codified knowledge versus personal, hard-to-formalize know-how), and procedural versus episodic versus declarative versus semantic knowledge (ranging from “how to do tasks” to experience-based episodes and structured conceptual understanding).

Finally, the lecture lays out principles for building knowledge management systems. Knowledge influences success, but organizations must manage both explicit and tacit knowledge. The key challenge is transforming tacit, personalized knowledge into explicit, shareable forms. Sharing is presented as the mechanism—through face-to-face transfer for tacit exchange, and through technology for capturing processes and making them retrievable. Knowledge management is positioned as a structured plan and architecture that helps acquire, create, store, and disseminate knowledge. Knowledge reservoirs include people, artifacts, repositories, departments, and networks, and the lecture notes that codified assets can be protected through patents, copyrights, trademarks, and trade secrets. The goal is to convert relationship- and practice-based knowledge into more explicit systems that organizations can use at scale, especially in knowledge-intensive environments like IT and R&D labs.