Chapter 2: Core Concepts and Knowledge Types

Learning Objectives

After completing this chapter, you will be able to:

• Explain the DIKW hierarchy and its significance in knowledge management
• Differentiate between tacit, explicit, implicit, and embedded knowledge
• Understand knowledge characteristics and their management implications
• Recognize the challenges of different knowledge types
• Apply knowledge classification systems to organizational contexts
• Define knowledge workers and their productivity factors
• Understand organizational memory and intellectual capital concepts

---

The DIKW Hierarchy

The Data-Information-Knowledge-Wisdom (DIKW) hierarchy is a foundational model for understanding how raw data transforms into actionable wisdom. This framework is essential for Knowledge Management practitioners to understand the value chain of information processing and knowledge creation.

The Four Levels

Level	Definition	Characteristics	Example
Data	Raw facts, figures, and observations	No context, unorganized, objective	Server CPU: 95%
Information	Data with context and meaning	Organized, answers “who, what, when, where”	Server CPU spiked to 95% during nightly backup at 2 AM
Knowledge	Information combined with experience	Actionable, answers “how”	Backup jobs on this server type cause CPU spikes; schedule during low-usage periods
Wisdom	Knowledge applied with judgment	Strategic, answers “why” and enables foresight	Design infrastructure to isolate backup workloads; implement resource governance

Transformation Process

Data → (Context) → Information → (Experience) → Knowledge → (Judgment) → Wisdom

Transformation	Process	Activities
Data → Information	Contextualization	Categorize, calculate, condense, contextualize
Information → Knowledge	Application	Compare, connect, converse, consider consequences
Knowledge → Wisdom	Integration	Reflect, evaluate, anticipate, exercise judgment

DIKW in Practice

Service Desk Example:

Level	Content
Data	Error code: 0x80070005
Information	User received error 0x80070005 when trying to access shared folder at 9:15 AM
Knowledge	Error 0x80070005 is an access denied error; check user permissions on folder, verify group membership, reset permissions if needed
Wisdom	Implement proactive permission auditing and automated group membership reviews to prevent access issues

---

Deep Dive: The DIKW Hierarchy in IT Service Management

Understanding each level of the DIKW hierarchy is critical for effective Knowledge Management. Let’s explore each level in detail with practical IT service scenarios.

Data: The Foundation Layer

Data represents raw, unprocessed facts without context or interpretation. Data alone has limited value until it is organized and given meaning.

Table 2.1: DIKW Hierarchy - Detailed IT Service Examples

Scenario	Data	Information	Knowledge	Wisdom
Incident Resolution	“Incident #45823 resolved in 15 minutes”	“Five similar printer incidents resolved today averaging 15 minutes”	“Printer driver v2.3 causes frequent connectivity issues; reinstalling driver resolves 90% of cases within 15 minutes”	“Standardize printer driver versions across fleet; implement automated driver update policy to prevent recurring incidents”
Performance Monitoring	“Network latency: 250ms”	“Network latency increased from 50ms to 250ms between 2-3 PM affecting 45 users”	“Video conferencing traffic during afternoon meetings saturates network bandwidth; QoS policies need adjustment for real-time applications”	“Implement SD-WAN with dynamic bandwidth allocation; establish network capacity planning aligned with collaboration tool adoption”
Change Management	“Change #7788 failed”	“Database upgrade change failed at validation stage with dependency conflict; 3 services affected for 45 minutes”	“Pre-production testing failed to catch dependency on legacy reporting module; validation checklist needs enhancement for database changes”	“Establish comprehensive dependency mapping in CMDB; mandate impact analysis workshops for all infrastructure changes”
Knowledge Base Usage	“KB article A-567 viewed”	“KB article A-567 viewed 340 times this month with 78% resolution success rate”	“Article A-567 on VPN setup is most-accessed article; high success rate indicates quality content; similar articles should follow this format”	“Develop article templates based on high-performing content; invest in visual documentation for network-related procedures”

Information: Adding Context

Information emerges when data is organized, structured, and given context. Information answers questions about who, what, when, and where.

Contextualization Activities:

• Categorization: Grouping similar data points
• Calculation: Performing mathematical operations
• Condensation: Summarizing large data sets
• Correction: Removing errors and anomalies
• Chronological ordering: Arranging by time sequence

Example - Ticket Queue Data:

• Data: “Ticket 1001, Ticket 1002, Ticket 1003…”
• Information: “25 password reset tickets in queue, average wait time 12 minutes, peak volume between 8-9 AM Monday mornings”

Knowledge: Applying Experience

Knowledge is information combined with experience, interpretation, and context. Knowledge enables action and answers “how” questions.

Knowledge Creation Process:

• Comparison: How does this information relate to other situations?
• Consequences: What are the implications of this information?
• Connections: How does this connect to what we already know?
• Conversation: What insights emerge from discussing this with others?

Example - Incident Pattern Recognition:

• Information: “Network outages occurring every Tuesday at 3 AM”
• Knowledge: “Tuesday 3 AM is when automated backup replication runs; network traffic spikes correlate with WAN link saturation; implementing backup throttling prevents outages”

Wisdom: Strategic Judgment

Wisdom represents the highest level - applying knowledge with judgment, foresight, and strategic thinking. Wisdom answers “why” questions and enables prediction and optimization.

Wisdom Characteristics:

• Principled understanding: Knowing underlying causes and principles
• Predictive capability: Anticipating future scenarios
• Strategic perspective: Understanding long-term implications
• Ethical consideration: Weighing values and trade-offs

Example - Service Strategy:

• Knowledge: “Users prefer self-service portals for password resets; reduces ticket volume by 40%”
• Wisdom: “Invest in self-service capabilities as strategic initiative; align with digital transformation goals; reduces operational costs while improving user satisfaction; enables service desk to focus on complex problems requiring human judgment”

Practical Exercise: DIKW Application

Scenario: Your organization has monitoring data showing server CPU utilization across 500 servers.

Your Task: Transform this data through each DIKW level:

1. Data Level: Raw CPU readings (Server01: 45%, Server02: 78%, Server03: 92%…)
2. Information Level: What patterns emerge? What context makes this meaningful?
3. Knowledge Level: What does this mean for operations? What actions should be taken?
4. Wisdom Level: What strategic decisions should this inform?

The Value Chain: From Data Collection to Strategic Action

The DIKW hierarchy represents not just a classification system, but a value chain where each transformation multiplies the potential impact on organizational performance.

Value Multiplication:

• Data: Low value, high volume - requires storage and management
• Information: Medium value, reduced volume - requires analysis and interpretation
• Knowledge: High value, actionable - requires validation and application
• Wisdom: Very high value, strategic - requires judgment and foresight

Investment Strategy: Organizations should invest most heavily in moving up the DIKW hierarchy rather than simply collecting more data. A small amount of wisdom is worth far more than terabytes of unprocessed data.

DIKW and the SECI Model Connection

The DIKW hierarchy complements the SECI knowledge conversion model (covered in Chapter 3):

• Socialization (Tacit → Tacit): Transfers tacit knowledge and wisdom through shared experience
• Externalization (Tacit → Explicit): Converts knowledge and wisdom into documented information
• Combination (Explicit → Explicit): Organizes information and data into knowledge bases
• Internalization (Explicit → Tacit): Transforms information and knowledge back into personal understanding

Understanding both models together provides a comprehensive framework for Knowledge Management strategy.

Common Pitfalls in DIKW Application

Pitfall 1: Data Hoarding

• Problem: Collecting massive amounts of data without plans for transformation
• Solution: Define information needs first, then collect only relevant data

Pitfall 2: Information Overload

• Problem: Overwhelming users with too much context without synthesis
• Solution: Focus on knowledge creation through analysis and pattern recognition

Pitfall 3: Knowledge Without Wisdom

• Problem: Knowing “how” but not understanding “why”
• Solution: Encourage reflection, strategic thinking, and principled decision-making

Pitfall 4: Premature Codification

• Problem: Trying to document wisdom before it’s fully formed
• Solution: Allow time for knowledge to mature through application and refinement

---

Types of Knowledge

The Tacit-Explicit Spectrum

Knowledge exists on a spectrum from tacit (personal, hard to articulate) to explicit (documented, easily shared).

Tacit ←――――――――――――――――――――――→ Explicit
(Personal)    (Implicit)    (Documented)

Figure 2.1: Knowledge Type Spectrum

This figure illustrates the continuum from pure tacit knowledge (completely internalized and difficult to articulate) through implicit knowledge (articulable but undocumented) to explicit knowledge (fully codified and documented). Most organizational knowledge exists somewhere in the middle of this spectrum.

Understanding the Knowledge Conversion Challenge

The primary challenge in Knowledge Management is converting tacit knowledge (valuable but inaccessible) into explicit knowledge (shareable and scalable) without losing essential context and nuance. This conversion is neither automatic nor easy.

Why Tacit Knowledge is Valuable:

1. Expertise: Represents years of accumulated experience
2. Context-sensitivity: Adapts to specific situations
3. Judgment: Incorporates values and priorities
4. Pattern recognition: Identifies subtle signals
5. Innovation: Enables creative problem-solving

Why Explicit Knowledge is Necessary:

1. Scalability: Can be shared with many people simultaneously
2. Consistency: Ensures standardized approaches
3. Accessibility: Available when and where needed
4. Persistence: Survives personnel changes
5. Searchability: Can be indexed and discovered

The art of Knowledge Management lies in converting tacit to explicit knowledge while preserving value, and then helping people internalize explicit knowledge to rebuild tacit expertise. This cycle, described by the SECI model (Chapter 3), is continuous and iterative.

Tacit Knowledge

Definition: Personal knowledge rooted in individual experience, insights, intuition, and skills that is difficult to articulate or document.

Characteristic	Description
Personal	Resides in individuals’ minds
Context-dependent	Meaning tied to specific situations
Hard to articulate	“I know it when I see it”
Acquired through experience	Learning by doing
Difficult to transfer	Requires observation, mentoring

Examples of Tacit Knowledge:

• Experienced technician’s ability to diagnose problems by “feel”
• Manager’s intuition about team dynamics
• Expert’s ability to recognize patterns quickly
• Skilled negotiator’s sense of timing
• Craftsperson’s motor skills and techniques
• Senior engineer’s architectural judgment
• Support analyst’s ability to sense user frustration levels

Challenges with Tacit Knowledge:

Challenge	Impact	Mitigation
Difficult to capture	Knowledge loss when experts leave	Mentoring, shadowing programs
Hard to validate	Quality varies, inconsistent	Peer review, testing
Not searchable	Can’t find when needed	Expert directories, skill mapping
Context-sensitive	May not transfer to new situations	Scenario documentation
Slow to transfer	Requires time and proximity	Apprenticeship models
Expert dependence	Creates single points of failure	Redundancy, cross-training

Explicit Knowledge

Definition: Knowledge that has been articulated, codified, and documented in formats that can be easily shared and understood.

Characteristic	Description
Documented	Written, recorded, or coded
Shareable	Easily transmitted to others
Storable	Can be captured in repositories
Searchable	Can be indexed and found
Replicable	Can be copied and distributed

Examples of Explicit Knowledge:

• Standard operating procedures
• Knowledge base articles
• Technical documentation
• Policy manuals
• Training materials
• Process diagrams
• Configuration guides
• Troubleshooting flowcharts
• API documentation
• Architecture diagrams

Explicit Knowledge Formats:

Format	Use Case	Strengths	Weaknesses
Documents	Procedures, guides	Detailed, comprehensive	Can become outdated
Videos	Demonstrations, training	Visual, engaging	Hard to update, not searchable
Diagrams	Processes, architectures	Clear visualization	May oversimplify
Databases	Structured data	Searchable, relational	Requires structure
FAQs	Common questions	Quick reference	Limited depth
Wikis	Collaborative content	Easy updates, versioning	Quality varies
Code comments	Technical context	Lives with code	May drift from implementation
Runbooks	Operational procedures	Step-by-step guidance	Maintenance intensive

Implicit Knowledge

Definition: Knowledge that can be articulated but has not yet been documented. It exists between tacit and explicit.

Characteristic	Description
Articulable	Can be expressed if asked
Undocumented	Not yet captured
Accessible	Can be obtained through inquiry
Convertible	Can become explicit with effort

Examples:

• Unwritten team norms and practices
• Workarounds that “everyone knows”
• Informal processes not in procedure manuals
• Institutional memory of “how things really work”
• Tribal knowledge about system quirks
• Unspoken rules about escalation paths
• Common shortcuts and efficiency tips

Converting Implicit to Explicit:

Technique	Description	When to Use
Interviews	Structured conversations with knowledge holders	Capturing expert knowledge
Observation	Watching experts perform tasks	Understanding actual practices
Think-aloud protocols	Experts verbalize their thought process	Documenting decision-making
After-action reviews	Capturing lessons immediately after events	Learning from incidents/projects
Documentation sprints	Focused efforts to document specific areas	Addressing knowledge gaps
Story circles	Group storytelling sessions	Capturing organizational history
Process mapping workshops	Collaborative diagramming	Understanding workflows

The 70-20-10 Rule for Implicit Knowledge

Research suggests that implicit knowledge represents approximately 70% of what people know in organizations - far more than the 10% that’s explicit and the 20% that’s purely tacit. This makes implicit knowledge the largest untapped resource for most organizations.

Capture Strategy:

• Focus first on high-value implicit knowledge (critical processes, common problems)
• Use lightweight capture methods (quick videos, voice recordings, bullet points)
• Capture “just enough” - not everything needs full documentation
• Focus on “how” and especially “why” - the context that makes knowledge useful
• Link to related explicit knowledge for richer understanding

Common Implicit Knowledge in ITSM:

• Troubleshooting approaches that aren’t in runbooks
• Escalation criteria that “everyone knows”
• System quirks and workarounds
• Customer communication templates and tone
• Priority judgment calls
• Vendor relationship management tactics

Embedded Knowledge

Definition: Knowledge that is built into processes, systems, products, or organizational structures.

Characteristic	Description
Systemic	Part of how things work
Often invisible	Not recognized as knowledge
Institutional	Belongs to the organization
Persistent	Survives personnel changes

Examples:

• Business rules in software systems
• Workflow automations
• Templates with built-in best practices
• Organizational structures reflecting strategy
• Physical layouts optimizing workflow
• Configuration management databases (CMDBs)
• Automated monitoring and alerting rules
• Self-service portal decision trees
• Change approval workflows

Table 2.2: Knowledge Types Comparison Matrix

Attribute	Tacit	Implicit	Explicit	Embedded
Codifiability	Very Low	Medium	Very High	High
Transferability	Very Difficult	Moderate	Easy	Automatic
Risk of Loss	Very High	High	Low	Very Low
Capture Effort	Very High	Medium	Low	High (initial)
Validation	Difficult	Moderate	Easy	Systematic
Scalability	Low	Medium	High	Very High
Update Ease	N/A	Medium	Easy	Varies
Search/Discovery	Very Difficult	Difficult	Easy	Automatic

---

Knowledge Classification Systems

Effective Knowledge Management requires systematic classification of knowledge assets. Classification enables better organization, discovery, governance, and reuse.

Classification by Source

Source Type	Description	Examples	Trust Level
Internal Creation	Knowledge developed within organization	Internal procedures, lessons learned	High (if validated)
External Acquisition	Knowledge obtained from outside sources	Vendor documentation, industry standards	Varies by source
Collaborative Development	Co-created with partners or community	Co-developed solutions, community wikis	Medium (requires validation)
Customer/User Contributed	Knowledge from service consumers	User forums, feedback, workarounds	Varies (needs moderation)

Classification by Domain

Domain	Description	Examples
Technical	System, application, and infrastructure knowledge	Configuration guides, technical specifications
Process	How work gets done	ITSM procedures, workflow documentation
Product/Service	Service catalog and offering information	Service descriptions, SLAs, capabilities
Organizational	Company-specific context	Policies, organizational structure, history
Domain/Industry	Sector-specific knowledge	Regulatory requirements, industry practices

Classification by Accessibility

Access Level	Who Can Access	Examples	Governance
Public	Anyone, including external parties	Public-facing KB, customer portals	High scrutiny
Internal	All employees	General policies, company directory	Standard review
Restricted	Specific groups/roles	Department procedures, technical details	Role-based access
Confidential	Limited authorized personnel	Security procedures, proprietary information	Strict controls
Regulated	Compliance-controlled access	PII, financial data, healthcare information	Audit trails required

Classification by Format and Structure

Format Category	Types	Management Considerations
Structured	Databases, forms, templates	Searchable, queryable, reportable
Semi-structured	Wikis, tagged documents	Requires taxonomy management
Unstructured	Emails, free-form documents	Difficult to search, requires AI/NLP
Multimedia	Videos, audio, images	Storage intensive, harder to search
Interactive	Simulations, decision tools	High engagement, complex to maintain

Table 2.3: Knowledge Classification Scheme

Classification Dimension	Values	Purpose
Content Type	How-to, Troubleshooting, Reference, Conceptual, FAQ	Helps users find appropriate format
Lifecycle Stage	Draft, Review, Published, Archived, Retired	Indicates currency and approval status
Audience	End User, Support Staff, Technical, Management, External	Targets appropriate complexity level
Service Area	Network, Applications, Infrastructure, Security, etc.	Enables domain-specific navigation
Priority/Criticality	Critical, High, Medium, Low	Guides maintenance prioritization
Update Frequency	Static, Quarterly, Monthly, Weekly, Real-time	Sets review schedule expectations
Language/Locale	English, Spanish, French, etc. / US, EU, APAC	Supports global operations

Figure 2.2: Knowledge Type Spectrum

This figure visualizes knowledge types across multiple dimensions: tacit-to-explicit spectrum, individual-to-organizational ownership, and low-to-high codifiability. Understanding where specific knowledge assets fall within this multi-dimensional space guides appropriate management strategies.

---

The Knowledge Worker

Definition and Evolution

The term Knowledge Worker was coined by Peter Drucker in 1959 to describe workers whose primary contribution is knowledge rather than manual labor or physical output.

Knowledge Worker Definition: An employee whose primary capital is knowledge, who “thinks for a living,” and who creates value through the application of expertise, judgment, and specialized skills.

Types of Knowledge Workers

Type	Description	Examples	Primary Value
Knowledge Creators	Generate new knowledge and insights	Researchers, analysts, engineers	Innovation
Knowledge Distributors	Share and disseminate knowledge	Teachers, trainers, communicators	Transfer
Knowledge Appliers	Apply existing knowledge to solve problems	Consultants, technicians, clinicians	Problem-solving
Knowledge Managers	Organize and curate knowledge	Librarians, KM professionals, editors	Organization

Knowledge Worker Characteristics

Key Attributes:

• Autonomy: Require independence in how they work
• Continuous Learning: Must constantly update skills and knowledge
• Collaboration: Value knowledge sharing and teamwork
• Judgment: Make decisions based on analysis and experience
• Tools Dependency: Require appropriate technology to be productive
• Intrinsic Motivation: Driven by mastery, purpose, and meaning

Knowledge Worker Productivity Factors

Table 2.4: Knowledge Worker Productivity Factors

Factor	Description	Impact on Productivity	Enablers
Access to Information	Ability to find needed knowledge quickly	High - reduces time searching	KM systems, search tools
Collaboration Capability	Ease of connecting with colleagues	High - accelerates problem-solving	Collaboration platforms, CoPs
Tools and Technology	Appropriate, usable tools for the job	Very High - fundamental enabler	Modern tooling, training
Organizational Culture	Support for knowledge sharing	Medium - affects willingness to share	Recognition, incentives
Time for Reflection	Opportunity to think and learn	Medium - improves quality	Workload management
Clear Goals	Understanding of objectives and priorities	High - focuses effort	Communication, alignment
Reduced Interruptions	Ability to focus on deep work	High - improves concentration	Work design, norms
Learning Opportunities	Access to training and development	Medium - builds capability	L&D programs

Managing Knowledge Workers

Challenges:

• Difficult to measure productivity with traditional metrics
• Require different management approaches than manual workers
• High turnover risk due to portable skills
• Need for autonomy conflicts with standardization needs
• Knowledge hoarding behaviors

Effective Practices:

• Outcome-based performance metrics
• Providing autonomy with accountability
• Investing in learning and development
• Creating knowledge-sharing culture
• Recognizing and rewarding contributions
• Reducing administrative burden
• Providing appropriate technology

Knowledge Worker Productivity: Beyond Time Tracking

Traditional productivity metrics like hours worked or tasks completed poorly measure knowledge worker output. The value of knowledge work lies in quality, innovation, and impact rather than volume.

Inappropriate Metrics:

• Hours at desk or online
• Number of emails sent
• Number of documents created
• Lines of code written
• Tickets closed (without quality consideration)

Better Metrics:

• Problem resolution effectiveness
• Innovation and improvement contributions
• Knowledge sharing and mentoring activity
• Quality of deliverables
• Strategic impact of decisions
• Customer or stakeholder satisfaction
• Long-term value creation

Deep Work vs. Shallow Work: Knowledge workers require uninterrupted time for concentrated cognitive effort (“deep work”) to produce their highest value output. Organizations that fragment knowledge worker time with constant meetings and interruptions destroy productivity while appearing busy.

The Knowledge Worker’s Dilemma

Knowledge workers face a fundamental tension: their value comes from specialized expertise, but organizations need knowledge to be shared and accessible. This creates several dilemmas:

1. Sharing vs. Competitive Advantage: Sharing knowledge helps the organization but may reduce individual competitive advantage
2. Documentation vs. Doing: Time spent documenting is time not spent doing (short-term productivity hit for long-term gain)
3. Specialization vs. Redundancy: Deep expertise is valuable but creates single points of failure
4. Innovation vs. Standardization: Creativity requires freedom but organizations need consistency

Resolution Strategies:

• Create incentives that align individual and organizational interests
• Recognize documentation and knowledge sharing as core job responsibilities
• Build overlapping expertise through mentoring and rotation
• Balance standardization (for routine tasks) with freedom (for complex problems)

---

Knowledge Assets and Intellectual Capital

Understanding Intellectual Capital

Intellectual Capital represents the intangible assets that create organizational value. Unlike physical or financial capital, intellectual capital resides in people, relationships, processes, and information.

Figure 2.3: Intellectual Capital Framework

This figure illustrates the three components of intellectual capital—Human Capital (knowledge in people), Structural Capital (knowledge in systems), and Relational Capital (knowledge in relationships)—and how they interact to create organizational value and competitive advantage.

Components of Intellectual Capital

Table 2.5: Intellectual Capital Components

Component	Definition	Elements	Management Focus
Human Capital	Knowledge embedded in employees	Skills, experience, creativity, expertise	Talent development, retention
Structural Capital	Knowledge embedded in organization	Processes, systems, databases, IP	Documentation, systematization
Relational Capital	Knowledge embedded in relationships	Customer relationships, partnerships, reputation	Relationship management

Human Capital

Definition: The collective skills, knowledge, expertise, and capabilities of employees.

Key Elements:

• Individual competencies and skills
• Experience and expertise
• Innovation and creativity capability
• Problem-solving abilities
• Leadership and management capabilities

Management Approaches:

• Talent acquisition and retention strategies
• Learning and development programs
• Succession planning
• Mentoring and coaching
• Career development pathways
• Performance management

Risks:

• Loss when employees leave
• Difficult to control or own
• Varies widely in quality
• Can be poached by competitors

Structural Capital

Definition: Knowledge that remains in the organization when employees go home at night.

Key Elements:

• Documented processes and procedures
• Organizational routines and culture
• Information systems and databases
• Intellectual property (patents, copyrights)
• Organizational structure and governance

Management Approaches:

• Documentation and codification initiatives
• Process standardization
• Knowledge base development
• Systems implementation
• IP protection strategies

Advantages:

• Owned by organization
• Can be controlled and managed
• Scalable and replicable
• Persists through personnel changes

Relational Capital

Definition: Knowledge and value embedded in external relationships.

Key Elements:

• Customer relationships and loyalty
• Supplier and partner relationships
• Brand reputation and image
• Networks and alliances
• Stakeholder trust

Management Approaches:

• Customer relationship management (CRM)
• Partner collaboration programs
• Brand management
• Network development
• Stakeholder engagement

Value:

• Creates barriers to competition
• Reduces transaction costs
• Enables collaboration and co-creation
• Provides market intelligence

Knowledge Asset Valuation

While difficult to quantify, organizations can assess knowledge assets through:

Quantitative Approaches:

• Market capitalization minus book value (market-to-book ratio)
• Revenue per employee
• Tobin’s Q (market value / replacement cost)
• Calculated Intangible Value (CIV)

Qualitative Approaches:

• Knowledge audit and inventory
• Competency assessments
• Process maturity evaluations
• Relationship strength assessments

Practical Indicators:

• Employee expertise and certification levels
• Knowledge base size and quality metrics
• Patent and IP portfolio value
• Customer satisfaction and retention rates
• Partner collaboration effectiveness

---

Organizational Memory

Definition and Importance

Organizational Memory is the stored information from an organization’s history that can be brought to bear on present decisions. It represents the collective knowledge, experience, and learning accumulated over time.

Components of Organizational Memory:

Component	Description	Storage Mechanisms
Individual Memory	Knowledge held by employees	Personal notes, expertise, experience
Documented Memory	Recorded information and knowledge	Documents, databases, repositories
Procedural Memory	Embedded in processes and routines	SOPs, workflows, systems
Cultural Memory	Shared values, norms, and assumptions	Stories, rituals, unwritten rules
Physical Memory	Embodied in physical artifacts	Facilities, equipment layouts, designs

Organizational Amnesia

Organizational Amnesia occurs when institutions lose memory of past experiences, lessons learned, and accumulated knowledge.

Causes:

• Employee turnover and retirements
• Lack of documentation practices
• Poor knowledge transfer processes
• System migrations without data preservation
• Organizational restructuring
• Merger and acquisition disruptions
• Failure to archive historical information

Consequences:

• Repeating past mistakes
• Losing competitive advantages
• Reduced problem-solving capability
• Inefficient decision-making
• Loss of customer intelligence
• Weakened organizational identity

Preventing Organizational Amnesia

Retention Strategies:

Strategy	Description	Implementation
Documentation Programs	Systematic capture of knowledge	KM systems, documentation standards
Exit Knowledge Transfer	Structured handoffs when employees leave	Exit interviews, transition periods, mentoring
Succession Planning	Ensuring continuity of critical knowledge	Redundancy, cross-training, shadowing
After-Action Reviews	Capturing lessons from events	Post-incident reviews, retrospectives
Storytelling and Narrative	Preserving organizational history	Video interviews, written histories, case studies
Alumni Networks	Maintaining relationships with former employees	Alumni programs, consulting arrangements
Archival Management	Preserving historical records	Digital archives, retention policies

Organizational Learning and Memory

Organizational memory enables organizational learning by:

• Providing context for current decisions
• Preventing repetition of past failures
• Leveraging successful patterns and practices
• Building institutional wisdom
• Maintaining continuity through change

Learning from Memory:

• Single-loop learning: Correcting errors based on past experience (doing things right)
• Double-loop learning: Questioning and changing underlying assumptions (doing the right things)
• Deutero-learning: Learning how to learn and improve learning processes (learning to learn)

The Half-Life of Organizational Knowledge

Like radioactive isotopes, organizational knowledge has a “half-life” - the time it takes for half of the knowledge to become obsolete or lost. Different types of knowledge decay at different rates:

Short Half-Life (6-12 months):

• Technology-specific procedures (tools evolve rapidly)
• Competitive intelligence (market changes quickly)
• Tactical workarounds (systems and processes change)

Medium Half-Life (2-5 years):

• Process documentation (periodic updates needed)
• Best practices (improvement and refinement ongoing)
• Product knowledge (versions and features evolve)

Long Half-Life (5+ years):

• Fundamental principles and concepts
• Organizational culture and values
• Strategic lessons learned
• Customer relationship history

Implications for Knowledge Management:

• Short half-life knowledge requires continuous refresh cycles
• Medium half-life knowledge needs scheduled review processes
• Long half-life knowledge deserves archival and preservation
• All knowledge needs metadata indicating expected lifespan and review dates

Corporate Storytelling and Narrative Knowledge

Stories are powerful vehicles for organizational memory. Unlike formal documentation, stories:

• Provide rich context and emotional connection
• Are easier to remember and retell
• Convey culture and values alongside facts
• Preserve the “why” behind decisions
• Create organizational identity

Types of Organizational Stories:

1. Foundation Stories: How the organization began, early challenges overcome
2. Hero Stories: Individuals who exemplified organizational values
3. War Stories: Crisis situations and how they were resolved
4. Lesson Stories: Failures that led to important learning
5. Success Stories: Achievements and how they were accomplished
6. Customer Stories: Memorable client interactions and outcomes

Preserving Organizational Narratives:

• Video interviews with long-tenured employees
• Structured storytelling sessions
• Case study documentation
• Historical archives and timelines
• Anniversary celebrations that recount history
• Onboarding programs that teach organizational story

---

Knowledge Characteristics

Dimensions of Knowledge

Dimension	Spectrum	Implications
Codifiability	Tacit ↔ Explicit	Affects capture and transfer methods
Complexity	Simple ↔ Complex	Affects documentation and training needs
Specificity	General ↔ Specific	Affects reusability across contexts
Volatility	Stable ↔ Dynamic	Affects maintenance requirements
Criticality	Nice-to-have ↔ Essential	Affects prioritization and governance

Knowledge Life Cycle Stage

Stage	Description	KM Focus
Emerging	New knowledge being created	Capture, validation
Maturing	Knowledge being refined and validated	Quality, standardization
Stable	Established, proven knowledge	Maintenance, accessibility
Declining	Becoming outdated or obsolete	Review, archival, retirement

Knowledge Characteristics Assessment

Characteristic	Questions to Ask
Source	Who knows this? Where did it originate?
Validity	How accurate is it? When was it validated?
Applicability	In what contexts does it apply?
Completeness	Is it sufficient for the use case?
Accessibility	Who can access it? How easily?
Currency	How current is it? When does it expire?

---

Individual vs. Organizational Knowledge

Individual Knowledge

Knowledge held by individual employees:

Type	Examples	Risk
Skills	Technical abilities, soft skills	Lost when employee leaves
Experience	Lessons learned, pattern recognition	Hard to transfer
Networks	Relationships, contacts	Personal, not organizational
Context	History, background understanding	Often undocumented

Organizational Knowledge

Knowledge that belongs to the organization:

Type	Examples	Storage
Documented processes	SOPs, procedures, guidelines	Knowledge bases, wikis
Institutional memory	Historical decisions, rationale	Archives, case studies
Collective capabilities	Team skills, organizational competencies	Skill databases, assessments
Structural knowledge	How the organization works	Org charts, process maps

Converting Individual to Organizational Knowledge

Strategy	Description	Example
Documentation	Capture expertise in written form	Procedure guides, knowledge articles
Training	Transfer through education	Courses, workshops, certifications
Mentoring	One-on-one knowledge transfer	Pairing experts with newcomers
Communities	Group learning and sharing	CoPs, forums, special interest groups
Embedding	Build into systems and processes	Automation, templates, checklists

---

Knowledge Quality Dimensions

Quality Attributes

Attribute	Definition	Assessment Question
Accuracy	Free from errors	Is the information correct?
Completeness	Contains all necessary information	Is anything missing?
Currency	Up-to-date and timely	Is it current?
Relevance	Applicable to the use case	Does it address the need?
Clarity	Easy to understand	Is it clear and unambiguous?
Accessibility	Easy to find and retrieve	Can users get to it?
Credibility	Trustworthy source	Is the source reliable?
Consistency	Aligns with other knowledge	Does it contradict other sources?

Quality Assessment Matrix

Quality Level	Characteristics	Action Required
Gold	Accurate, complete, current, validated	Promote and reference
Silver	Generally accurate, may need minor updates	Schedule review
Bronze	Useful but needs improvement	Flag for enhancement
Needs Work	Incomplete, potentially inaccurate	Major revision required
Archive	Outdated but historically valuable	Move to archive
Retire	No longer valid or useful	Remove from active use

---

Knowledge in Context

Contextual Factors

Knowledge meaning and applicability depend on context:

Factor	Impact on Knowledge
Time	What was true may no longer be
Location	Practices vary by region/site
Role	Different needs for different roles
Situation	Emergency vs. routine scenarios
Technology	System-specific knowledge
Regulatory	Compliance requirements vary

Context Capture Requirements

Context Element	Examples	Why It Matters
When created	Date, version	Assess currency
Who created	Author, expert	Assess credibility
What problem	Use case, scenario	Assess relevance
Which system	Application, platform	Assess applicability
What conditions	Prerequisites, limitations	Assess validity

---

Connections to Other Chapters

Understanding core concepts is just the beginning. Throughout this handbook, you’ll see these concepts applied:

• Chapter 3 (Frameworks): The SECI model provides the process for converting between knowledge types
• Chapter 10 (Knowledge Conversion): Deep dive into techniques for tacit-to-explicit conversion
• Chapter 15 (Knowledge Retention): Strategies for preventing organizational amnesia
• Chapter 18 (Technology): Tools for managing different knowledge types
• Chapter 21 (Culture): Creating environments where knowledge workers thrive

The DIKW hierarchy and knowledge type taxonomy introduced here form the theoretical foundation for all practical Knowledge Management activities covered in subsequent chapters.

---

Review Questions

Test your understanding of the core concepts covered in this chapter:

1. DIKW Hierarchy Application
   • You receive a monitoring alert: “Database query response time: 3500ms.” How would you transform this through each level of the DIKW hierarchy?
   • What additional context would you need at the Information level?
   • What experience would be required to move from Information to Knowledge?
   • What strategic judgment would elevate this to the Wisdom level?
2. Knowledge Type Identification and Conversion
   • Your senior network engineer can diagnose complex routing issues by reviewing log files in ways that junior engineers cannot replicate, even with the same logs. What type of knowledge is this?
   • Is this tacit, implicit, explicit, or embedded knowledge?
   • What strategies would you use to capture this knowledge?
   • What methods would be most effective for transferring this knowledge to junior engineers?
3. Knowledge Classification Practice
   • You need to classify a document titled “Emergency Response Procedures for Data Center Power Failure.” What would be its content type classification?
   • What lifecycle stage should this document be in?
   • Who should be the target audience?
   • What priority/criticality level should be assigned?
   • How frequently should this document be reviewed?
4. Intellectual Capital Assessment
   • Your organization is considering an acquisition. What human capital indicators would you examine in the target company?
   • What structural capital assets would you assess?
   • What relational capital factors would be important to evaluate?
   • How would you measure the overall intellectual capital value?
5. Organizational Memory and Amnesia
   • Your IT department has experienced 40% turnover in the past year. What specific symptoms of organizational amnesia would you look for?
   • What critical knowledge is most at risk of being lost?
   • What immediate actions would you take to capture at-risk knowledge?
   • How would you design a three-month program to rebuild critical organizational memory?

---

Key Takeaways

• The DIKW hierarchy shows how data transforms into wisdom through contextualization, experience, and judgment - each transformation adds value
• Tacit knowledge (personal, experiential) is harder to capture but often more valuable than explicit knowledge; requires different management strategies
• Implicit knowledge represents a significant opportunity - it can be articulated and converted to explicit knowledge with intentional effort
• Embedded knowledge persists in organizational systems and processes, providing stability through personnel changes
• Knowledge classification systems enable better organization, discovery, governance, and reuse of knowledge assets
• Knowledge workers are the primary creators and consumers of knowledge; their productivity depends on access, tools, and culture
• Intellectual capital comprises human, structural, and relational components - all three must be actively managed
• Organizational memory preserves institutional wisdom and prevents repeating past mistakes
• Knowledge quality must be actively managed across accuracy, completeness, currency, and other dimensions
• Context is essential for knowledge to be meaningful and applicable; always capture contextual information
• Converting individual knowledge to organizational knowledge protects against knowledge loss and creates scalable capability

---

Summary

Understanding the different types and characteristics of knowledge is fundamental to effective Knowledge Management. The DIKW hierarchy provides a framework for understanding how raw data becomes actionable wisdom through progressive transformation. Recognizing the differences between tacit, explicit, implicit, and embedded knowledge helps organizations develop appropriate strategies for capture, sharing, and application.

Knowledge classification systems enable systematic organization and governance of knowledge assets. Understanding knowledge workers and their productivity factors guides effective management approaches. Intellectual capital frameworks help organizations recognize and manage the intangible assets that increasingly drive competitive advantage. Organizational memory preservation prevents institutional amnesia and enables continuous learning.

Quality dimensions ensure that knowledge remains accurate, current, and useful, while context ensures knowledge is applied appropriately. Together, these concepts form the theoretical foundation for practical Knowledge Management implementation.

---

Chapter Navigation

Previous	Up	Next
← Chapter 1: Introduction	Part I: Foundations	Chapter 3: Frameworks →