Knowledge management Study Guide

📖 Core Concepts Knowledge Management (KM): Coordinated processes that capture, share, and apply knowledge to meet organizational goals. Tacit vs. Explicit Knowledge: Tacit: Unconscious, personal know‑how; hard to articulate. Explicit: Conscious, codifiable information that can be documented and transferred. SECI Model: A spiraling conversion cycle – Socialisation (tacit → tacit), Externalisation (tacit → explicit), Combination (explicit → explicit), Internalisation (explicit → tacit). Push (Codification) vs. Pull (Personalisation) Strategies: Push: Encode knowledge into repositories for anyone to retrieve. Pull: Seek knowledge from experts on‑demand, emphasizing tacit exchange. Knowledge Creation vs. Exploitation: Creation = exploratory innovation; Exploitation = reusing existing knowledge. Knowledge Barriers: Missing knowledge, inadequate education, or perceptual limits that block sharing. --- 📌 Must Remember KM creates competitive advantage by turning knowledge into a strategic asset. Three core KM components (across perspectives): people & culture, processes & structure, technology. SECI spiral is continuous – every conversion round enriches the knowledge base. Codification works best for explicit knowledge; personalisation is essential for tacit knowledge. Knowledge audits identify strengths, gaps, and alignment with objectives. Formal protection (patents, copyrights, access controls) safeguards codified knowledge; informal protection (secrecy, complexity, lead‑time) guards tacit or hard‑to‑codify knowledge. --- 🔄 Key Processes Knowledge Capture (Push): Identify expert knowledge → document → store in a searchable repository. Knowledge Retrieval (Pull): User defines problem → locates expert or relevant document → applies knowledge. SECI Conversion Cycle: Socialisation → Externalisation → Combination → Internalisation → repeat. Knowledge Audit: Define audit scope → inventory explicit assets → map tacit expertise → assess gaps → recommend actions. Retention Planning (when employees exit): Conduct exit interviews → record key processes → create hand‑over guides → store in repository. --- 🔍 Key Comparisons Codification vs. Personalisation Codification: Document‑centric, scalable, suited for explicit knowledge. Personalisation: Human‑centric, relational, suited for tacit knowledge. Formal vs. Informal Protection Formal: Legal instruments, technical controls; effective for codified assets. Informal: Secrecy, cultural norms, complexity; effective for tacit or complex assets. Embedded vs. Embodied Knowledge Embedded: Resides in systems/software design. Embodied: Resides in a person’s physiological/neurological skills. --- ⚠️ Common Misunderstandings “All knowledge can be codified.” – Tacit knowledge often resists documentation; forcing codification loses nuance. “More technology = better KM.” – Without supportive culture and processes, tools become underused. “Protection always beats sharing.” – Over‑protection stifles innovation; balance is essential. --- 🧠 Mental Models / Intuition Spiral Model: Think of knowledge flowing up‑and‑down a spiral—each loop adds depth; never a straight line. Push‑Pull Analogy: Imagine a library (push) vs. a mentor network (pull). Choose the “library” for facts, the “mentor” for expertise. --- 🚩 Exceptions & Edge Cases Highly regulated industries: Formal protection (patents, licenses) may be mandatory despite a push‑centric culture. Rapidly changing environments: Over‑reliance on codified repositories can become obsolete; favour personalisation. Aging workforce: Knowledge may be deeply embodied; retention must include shadowing and apprenticeship, not just documents. --- 📍 When to Use Which Use Codification when knowledge is stable, repeatable, and can be expressed in documents (e.g., SOPs, policies). Use Personalisation for problem‑solving that requires judgment, experience, or nuanced insight (e.g., design reviews, crisis response). Apply Formal Protection for marketable, codifiable assets (software code, product designs). Apply Informal Protection for competitive processes, cultural know‑how, or proprietary methods that are hard to patent. --- 👀 Patterns to Recognize “Knowledge‑Loss” Red Flag: High turnover of subject‑matter experts + no documented hand‑overs → audit needed. “Repository Stagnation” Pattern: Lots of stored documents but low access metrics → shift toward personalisation or improve searchability. “Barrier Clustering”: Multiple barriers (e.g., siloed departments + inadequate ICT) often appear together; solving one may not help until others are addressed. --- 🗂️ Exam Traps Confusing Tacit with Embedded: Embedded knowledge lives in systems, not in a person’s mind. Mixing “Push” with “Personalisation”: Push ≠ personalisation; the former is codification‑focused, the latter is expert‑centric. Assuming All Protection Is Formal: Many organizations rely on informal secrecy; exam questions may test recognition of both. Over‑emphasizing Technology Alone: A question might list “collaborative software” as a KM tool but expect the answer to include cultural alignment as a prerequisite. ---