Introduction to KM (Contd.)

Knowledge management hinges on a practical insight: valuable decisions and performance depend on how well organizations move between tacit and explicit knowledge—and then turn that knowledge into action. Explicit knowledge sits in documented, declarative forms (like manuals or books), while tacit knowledge lives in experience and judgment. The transcript uses everyday examples—stock buying, troubleshooting a computer, and managing a team—to show that even when explicit information exists, the final call often relies on personal insight, context, and learned experience.

That context split matters because knowledge behaves differently across situations. Declarative explicit knowledge provides “what” information in general terms—such as the financial ratios to check before buying a stock. Tacit knowledge, by contrast, shapes “how to decide” in a specific moment, drawing on experience to weigh factors that may not be fully captured in text. Procedural knowledge adds “how to do” steps: explicit procedural knowledge might be a guide for configuring a computer or following a buying process, but tacit procedural knowledge becomes crucial when something goes wrong or when time and resources must be saved. In management settings, the same pattern appears: written guidance on employee motivation may not work uniformly, so managers rely on judgment to adapt actions to the particular team and project.

The transcript then lays out a conversion framework for knowledge movement. Tacit-to-tacit transfer happens through socialization and internalization—learning through interaction, observation, imitation, and practice. Tacit-to-explicit transfer happens through externalization, where experience is articulated into models, concepts, theories, or hypotheses. Internalization completes the loop by turning documents and guidance into lived capability through “learning by doing.” These processes can be combined to reconfigure knowledge into new or improved forms, including testing and refining theoretical models based on real-world experience.

A second major theme is how knowledge gets captured, organized, and accessed. Traditional systems stored explicit knowledge in physical, structured formats—libraries, classifications, and physical retrieval—while tacit knowledge often remained trapped in people. Newer digital approaches shift storage and access into cyber space, enabling 24/7 retrieval and broader leverage for procedural and technical knowledge. Still, the transcript stresses that digital access alone isn’t enough: organizations must ensure knowledge is actually utilized to meet goals for productivity, efficiency, and effectiveness.

To operationalize this, knowledge management activities follow a lifecycle: acquire/create knowledge (through people, labs, and R&D), analyze its viability, organize and codify it into usable forms, enable access and retrieval, and then measure utilization by comparing outcomes against objectives. The transcript also names common knowledge management structures—knowledge teams, knowledge bases, knowledge hubs (with Google as an example), communities of practice, and learning organizations—supported by technology and leadership initiatives such as appointing Chief Knowledge Officers. Finally, it frames where knowledge resides across an organization: in customers, in products, in people (often tacit), in processes (“know-how”), in organizational memory, and in relationships. All of this connects back to intellectual capital, defined as structural, relational, and human capital—assets that some companies (e.g., Skandia and others mentioned) attempt to measure using intellectual capital indices.