Chapter 1: Introduction to Knowledge Management (KM)

“Working Smarter, Not Harder”

1. Shift to the Knowledge Economy
In the traditional industrial economy, physical resources like land, labor, and machinery were the
primary sources of competitive advantage. However, globalization, digital transformation, and
rapid technological advances have changed the basis of competition. Modern organizations now
operate in a knowledge-based economy, where intellectual capital and expertise determine
success. Products and business models become obsolete quickly, so organizations must
constantly adapt, innovate, and improve to remain relevant.
Today, customers are more informed, markets change faster, and competitors can replicate
technology quickly. What cannot be easily replicated is unique organizational knowledge such
as:
 Deep customer understanding
 Efficient problem-solving processes
 Employee know-how and experience
 Unique methods, insights, and best practices
Key Insight:
Competitive advantage now lies not in what an organization does, but in what it knows and
how effectively and quickly it applies that knowledge.
Example:
Companies like Apple, Google, and Toyota outperform others not because they have more raw
materials, but because they have superior design knowledge, innovation culture, and process
expertise.
2. Meaning and Purpose of Knowledge Management
Knowledge Management (KM) refers to the structured and strategic process of identifying,
capturing, storing, sharing, and applying knowledge to improve organizational performance.
KM ensures that valuable experience, insights, and skills are not lost when employees leave,
retire, or transfer roles. It also ensures that employees do not waste time reinventing solutions
that the organization already knows.
KM involves:
 Recognizing knowledge as a core asset
  Converting individual knowledge into organizational knowledge
 Making the right knowledge available to the right people at the right time
 Encouraging collaboration and continuous learning
Why KM Matters:
Without KM, knowledge remains fragmented and isolated within individuals or departments,
leading to repeated mistakes, inefficiencies, and slow problem-solving.
Example:
A company that documents troubleshooting procedures allows new technicians to solve complex
problems faster instead of depending solely on senior staff.
3. Types of Knowledge
Explicit Knowledge
 Can be written, stored, and communicated easily
 Found in books, manuals, reports, SOPs, databases
 Structured and formal
 Can be digitized and transferred efficiently
Example:
A standard operating procedure (SOP) explaining how to calibrate a machine is explicit
knowledge.
Tacit Knowledge
 Personal, intuitive, experience-based knowledge
 Hard to express clearly in words or documents
 Developed through practice, observation, and judgment
 Often transferred through mentoring, coaching, or apprenticeship
Example:
A senior negotiator’s ability to read body language and adjust communication tone is tacit
knowledge.
Key Point:
Tacit knowledge is usually more valuable but also more difficult to transfer. Effective KM
focuses heavily on converting tacit knowledge into explicit knowledge without losing meaning.
4. The Knowledge Organization
A knowledge organization is one that treats learning and knowledge-sharing as an integral
part of daily work, not as an optional task. Knowledge organizations focus on building systems
that encourage collaboration, reduce redundancy, support ongoing learning, and integrate
knowledge into every business process.
Characteristics of a Knowledge Organization:
 Encourages questioning, experimentation, and improvement
 Promotes transparency, open communication, and trust
 Maintains efficient knowledge storage and search systems
 Motivates employees to share rather than hoard knowledge
 Uses knowledge to make faster and more accurate decisions
Example:
Toyota uses a learn-from-every-mistake approach called Kaizen, where workers continuously
document insights and process improvements, creating a constantly improving organizational
knowledge base.
5. The Knowledge Management Life Cycle
KM operates through several stages:
1. Knowledge Creation
New knowledge is generated through research, innovation, customer interactions,
experimentation, and lessons learned.
2. Knowledge Capture
Useful knowledge is recorded through documentation, interviews, observation, and
knowledge mapping. This prevents knowledge loss when employees leave.
3. Knowledge Organization
Information is arranged using taxonomies, indexing, databases, and structured categories
so that it becomes easy to search and retrieve.
4. Knowledge Sharing / Dissemination
Knowledge is communicated across the organization using intranets, training programs,
communities of practice, presentations, mentoring networks, and collaborative platforms.
5. Knowledge Application
The final and most important stage. Knowledge becomes valuable only when it
influences decisions, behavior, and action.
Key Point:
The lifecycle is continuous, meaning the organization keeps learning, refining, and updating
knowledge to stay relevant.
6. KM Is Not Just Technology
While technology plays an important role by providing repositories, collaboration tools,
intranets, and databases, KM is primarily about people, culture, and motivation. Without trust
and incentives, people hesitate to share knowledge due to fear of losing job security or status.
Human Barriers to KM:
 Fear of losing power
 Lack of trust between employees
 Lack of communication culture
 No reward for sharing knowledge
 “Knowledge hoarding” mentality
Overcoming These Barriers:
 Encourage teamwork and shared goals
 Recognize and reward knowledge contributors
 Promote open communication and trust-building
 Provide leadership support and role modeling of knowledge sharing
Example:
If promotions reward teamwork and collaboration instead of individual performance alone,
employees naturally share more knowledge.
7. Benefits of Knowledge Management
KM leads to significant strategic and operational benefits:

Benefit Explanation

Faster Problem Solving Employees access proven solutions instead of reinventing

them.

Reduced Operational Cost Prevents repeated mistakes; saves time and effort.

Improved Innovation Combining different knowledge sources sparks new ideas.

Better Decision-Making Employees make informed decisions using collective

 intelligence.

Improved Customer Knowledgeable employees respond faster and more effectively.

Service

Example:
McDonald’s standard recipes and process instructions ensure uniform quality and efficiency
across thousands of outlets worldwide.
8. Challenges in Implementing KM
Implementing KM is difficult because:
 Capturing tacit knowledge requires time and effort
 Employees may be unwilling to share expertise
 Large organizations struggle to organize massive data effectively
 KM systems need ongoing maintenance and updates
 Cultural change is slow and requires leadership commitment
Key Point:
The main challenge is cultural, not technical. A KM initiative fails if employees do not believe
in sharing knowledge.
9. Overall Conclusion
Chapter 1 establishes that knowledge is the most critical strategic resource in modern
organizations. KM helps organizations convert individual know-how into collective
organizational intelligence, enabling faster learning, innovation, and competitive advantage.
But KM only succeeds if supported by culture, leadership, incentives, and continuous
improvement, not technology alone.
Here are detailed notes on all key topics from Chapter 1 – “Working Smarter, Not Harder”
of your Knowledge Management (KM) text. Each section expands on major concepts, examples,
and implications for organizational practice.
🔹 1. In a Nutshell

Modern organizations operate in a knowledge society, where survival depends on adapting to

rapid technological and market changes.
 The shift from the information age to the knowledge age redefines success: competitive
advantage now rests on creating, managing, and using knowledge effectively.
 The focus is no longer on “doing more work” but on working smarter—using insight,
creativity, and shared expertise to innovate continuously.
  Core questions for every firm:
o Do we know what we know?

o How can we use our existing knowledge better?

o How can we turn information into action and opportunity?

Example:
Merck’s CEO emphasized that to manage knowledge effectively, a company must inventory its
people, decisions, and systems; define who holds expertise; and use technology to make
knowledge accessible and useful.
🔹 2. What Is Knowledge Management?

Knowledge Management (KM) is a multidisciplinary approach combining people, technology,

and processes to capture, organize, and leverage an organization’s collective expertise.
Key components of KM:
 Using knowledge from external sources
 Embedding knowledge in processes, products, and services
 Representing knowledge in documents and databases
 Promoting knowledge growth via culture and incentives
 Sharing and transferring knowledge
 Measuring and reassessing knowledge value
Explicit vs. Tacit Knowledge
 Explicit knowledge: written or stored—documents, manuals, databases.
 Tacit knowledge: personal, experience-based, often unrecorded—residing in people’s
minds.
Key idea: Up to 95% of organizational knowledge is tacit.
KM seeks to connect human experts and documented systems into an integrated process.

🔹 3. The Knowledge Organization

The knowledge organization is structured around the KM life cycle:

1. Creation
2. Collection/Capture
 3. Organization
4. Refinement
5. Dissemination
6. Maintenance (quality assurance)
The environment—technology, leadership, culture, competition—shapes how well KM is
implemented.
Sources of Knowledge:
 Customer knowledge (needs, buying power)
 Product knowledge (market trends, pricing)
 Financial knowledge (funding, capital sources)
 Personnel knowledge (expertise, service quality)
Example: U.S. Marine Corps KM system integrates global intelligence and tactical simulation to
develop and test strategies within hours.
🔹 4. What KM Is Not About

Common misconceptions include:

 ❌ It is not reengineering (which is a one-time structural overhaul). KM is continuous
learning and adaptation.
 ❌ It is not only technology—technology enables, but people create and share knowledge.

 ❌ It is not just data or information—knowledge adds value through action and context.

 ❌ It is not intellectual capital alone—IC is the result of knowledge application.

 ❌ It is not digital networking—human collaboration is central.

 ❌ It is not simply knowledge capture—culture and cooperation matter more.

Example: A British supermarket discovered diaper–beer purchase correlations through data

mining—turning information into actionable knowledge.

🔹 5. Why Knowledge Management?

KM creates strategic and operational advantages:

 Empowers employees to learn and innovate
  Reduces duplication of work
 Enhances decision speed and accuracy
 Builds stronger customer and partner relationships
Key Benefits
 Faster response to customers
 Creation of new products and markets
 Retention of expertise (prevents “brain drain”)
 Continuous learning and collaboration
Examples:
 Merrill Lynch: Knowledge-based systems shorten learning curves for 18,000 brokers
worldwide.
 Accenture (ANet): Connects consultants globally for problem-solving and best-practice
sharing.

🔹 6. The Drivers of KM

KM growth is fueled by five main drivers:

1. Technology Drivers – Digital communication, intranets, and networking make
knowledge exchange faster and borderless.
→ Technology equalizes access, but people create value.
2. Process Drivers – Avoid repetition of mistakes; share best practices; become “just-in-
time” knowledge organizations.
3. Personnel Drivers – Promote teamwork, minimize turnover, retain expertise, and
prevent “knowledge walkouts.”
4. Knowledge-Related Drivers – Make hidden expertise visible and available when
needed.
5. Financial Drivers – Knowledge assets appreciate with use; KM increases ROI through
better decisions and innovation.

🔹 7. How KM Came About

KM emerged as a response to limitations of older management trends:

  1980s–1990s reengineering and downsizing improved efficiency but drained expertise.
 Globalization, networking, and the Internet enabled sharing knowledge internally and
externally.
 Firms realized that knowledge—not capital—is the new core asset.
Survey Insight:
KPMG (2000) found that most firms had KM strategies but struggled with cultural and human
integration, often viewing KM too narrowly as technology.

🔹 8. Key Challenges in KM

Implementing KM requires cultural and organizational change.

Major challenges include:
1. Defining KM and its value to employees and management
2. Evaluating and mapping knowledge assets across departments
3. Capturing and converting tacit knowledge effectively
4. Encouraging collaboration and knowledge sharing
5. Sustaining research and innovation
6. Aligning technology with human behavior
Examples of Challenges:
 Cultural clashes in mergers (Daimler–Chrysler case) show that trust and
communication are vital for KM success.
 Collaboration tools (intranets, videoconferencing) enable distributed teamwork but must
be backed by incentives.

🔹 9. Historical Overview

Knowledge transfer dates back to ancient apprenticeship models.

Key milestones:
 Peter Drucker (1960s): Introduced “knowledge worker” concept.
 1970s–80s: Expert systems, AI, and early knowledge capture tools emerged.
 1990s: The Internet revolutionized KM—enabling instant sharing and collaboration.
  Modern era: Focus shifted from automating processes to augmenting human thinking
and embedding KM into daily workflows.

🔹 10. KM Myths (Debunked)

1. KM is a fad – It’s a long-term strategic necessity.

2. KM = Data warehousing – Data storage ≠ knowledge use.
3. KM is new – Its roots go back decades; technology only enhanced it.
4. KM is purely technological – People and trust are central.
5. Technology distributes intelligence – Only humans interpret meaning.
6. KM = Reengineering – Reengineering is structural; KM is cultural and continuous.
7. Employees resist sharing – True only in low-trust cultures; incentives reverse this.
8. KM works only internally – External networks (suppliers, customers) enrich
knowledge.
9. Technology replaces face-to-face learning – Personal interaction remains irreplaceable.

🔹 11. Role of Trust in the KM Life Cycle

Trust is the foundation of successful KM:

 Encourages open sharing without fear of loss or criticism
 Builds collaboration across departments
 Supports consistent reinvestment of knowledge in databases or communities of practice
Without trust, even advanced KM systems fail.

🔹 12. Implications for Organizations

 Firms must treat knowledge as a renewable strategic asset, not a byproduct.

 KM success demands integration across HR, IT, and strategy.
 Reward structures must favor collaboration, not competition.
 Continuous learning and innovation are essential for sustainable advantage.
🔹 13. Summary of Chapter Insights

 Knowledge is now the core economic resource.

 KM aligns people, processes, and technology to transform knowledge into performance.
 Success lies in creating a culture of learning, sharing, and innovation, not in acquiring
tools.
 Working smarter—not harder—means leveraging collective intelligence to anticipate
change.

CHAPTER 2 — UNDERSTANDING KNOWLEDGE

Knowledge is the central foundation of Knowledge Management (KM). Many people hold the
mistaken belief that knowledge simply exists in books, manuals, or databases. However, this is
incorrect because documents do not contain knowledge; they contain representations of
information. Knowledge exists primarily in the human mind, built through understanding,
reasoning, and experience. Just like musical notes on a page are not music until performed,
information becomes knowledge only when interpreted by a human knower. Thus, an
organization’s true competitive advantage lies not in its technology or database systems, but in its
people, their experience, skills, and ability to apply knowledge to decisions and problem-
solving.
1. DEFINING KNOWLEDGE
Knowledge is defined as “understanding gained through experience or study.” It is know-
how, meaning the ability to perform tasks, make decisions, and interpret situations effectively.
Knowledge can be an accumulation of facts, procedural rules, or heuristics:
 A fact is a statement accepted as true within a domain (e.g., the sun rises in the east).
 A procedural rule provides steps for action (e.g., check rear-view mirrors before
changing lanes).
 A heuristic is a rule of thumb derived through long-term experience (e.g., if you drive
within 5 mph of the speed limit, you usually avoid tickets).
Knowledge has specificity, meaning it is usually tied to a particular domain. A surgeon’s
knowledge is not automatically useful to an auto mechanic, and vice versa. Deep knowledge is
often tacit, shaped through years of practice. Values, personal judgment, beliefs, and integrity
influence how people understand information and turn it into meaningful action.
2. INTELLIGENCE, EXPERIENCE, AND COMMON SENSE
Intelligence is the capacity to acquire knowledge and apply it effectively in reasoning and
decision-making. Intelligence includes language understanding, memory, learning ability, and the
capacity to adapt to new situations. An intelligent person can convert knowledge into action.
Example:
A chess master remembers patterns of board arrangements and decides moves rapidly. The
novice must analyze each possible move individually. The difference lies in stored experience
and mental models, not simply information.
Experience refers to knowledge gained by doing. It allows a person to refine judgment and
improves problem-solving skills through repeated performance. Experience also develops
intuition, which helps experts recognize solutions without deliberate analysis.
Common Sense is everyday practical knowledge developed naturally through life. It is
something computers do not possess. A child knows not to touch fire; a computer must be
explicitly told what fire does. Lack of common sense makes computer reasoning “brittle.”
3. DATA, INFORMATION, AND KNOWLEDGE
Understanding the DIK hierarchy is essential:

Level Meaning Example

Data Raw facts without interpretation “John is 6 feet tall.”

Informatio Data organized to convey meaning “John’s height makes him suitable
n for basketball.”

Knowledge Information combined with experience, “Given his height, agility, and past
context, and judgment for decision- performance, John should play
making forward.”

Data becomes information when structured or analyzed. Information becomes knowledge when
interpreted and used to make decisions. Knowledge is actionable information.
4. TYPES OF KNOWLEDGE
a. Shallow vs. Deep Knowledge
Shallow knowledge is surface-level and easy to recall but lacks depth. Deep knowledge is
extensive understanding built over years. A simple loan approval for a small amount may use
shallow rules, while evaluating a complex business loan requires deep financial judgment.
b. Knowledge as Know-How
Know-how is practical, hands-on expertise. It distinguishes experts from novices. It is often
expressed as heuristics (rules derived from experience). If documenting expert knowledge in a
knowledge base, these heuristics are typically expressed in IF–THEN form.
c. Procedural, Declarative, Semantic, and Episodic Knowledge
 Procedural Knowledge: Knowing how to perform actions (e.g., how to play piano or
repair an engine). Automatic through repetition.
 Declarative Knowledge: Knowing facts and descriptions (e.g., “France is in Europe”).
Easily verbalized.
 Semantic Knowledge: Organized knowledge of concepts and relationships stored in
long-term memory (e.g., understanding how a car electrical system works).
 Episodic Knowledge: Knowledge stored through personal experiences or scenarios (e.g.,
recalling how a particular patient responded to treatment).
d. Tacit vs. Explicit Knowledge
 Tacit Knowledge: Internal, deeply personal, hard to articulate; formed by experience,
intuition, and values (e.g., how a musician “feels” rhythm).
 Explicit Knowledge: Codified knowledge stored in documents, manuals, and databases
(e.g., standard operating procedures).
5. EXPERT KNOWLEDGE AND CHUNKING
Experts store knowledge in chunks — large units of connected meaning. Chunking allows fast
recall and quick reasoning, but makes it hard for experts to explain their knowledge, because
much of it has become automatic.
Example:
An experienced mechanic diagnoses engine noise instantly, while a novice must test each part
individually.
Experts reason differently from novices:
 Experts use knowledge-based reasoning (pattern-recognition).
 Novices use means-end analysis (step-by-step trial).
6. HUMAN LEARNING METHODS
Humans primarily learn in three ways:
 Experience (trial & refinement)
 Example (studying cases)
 Discovery (exploring without guidance — the hardest to explain or teach)
These learning types reinforce how knowledge is acquired and why tacit knowledge is so
valuable.
7. IMPLICATIONS FOR KNOWLEDGE MANAGEMENT
Organizations must identify, capture, preserve, and share knowledge, especially tacit
knowledge held by experts. Failing to do so results in knowledge loss, particularly when experts
retire or leave. KM initiatives must therefore:
 Encourage collaboration and sharing
 Build systems that support knowledge access
 Create a culture that values continuous learning
Technology alone cannot create knowledge; it only supports its flow.
CONCLUSION
Knowledge is a living, human-centered asset. It grows through experience, becomes refined
through reasoning, and becomes valuable only when shared and applied.

Chapter 3 Knowledge Management Systems Life

Cycle
1. Knowledge Management Systems (KMS) follow a life cycle:
 Think of it like a process or journey that starts with planning and ends with a working
system that meets the company’s needs.
 A knowledge team (representing the company’s thinking) and a knowledge developer
(who knows how to capture, design, and implement knowledge) are essential for success.
 Without planning and structure, the system can fail.
2. The most important step:
 Identify needs: short-term, medium-term, and long-term.
 Check existing knowledge: see what employees already know.
 Do a cost/benefit analysis: make sure the system is worth it.
 Plan tools and procedures: ensure everything works correctly and reliably.
3. Three core questions guide KMS development:
1. What problem are we solving?
o Is the problem important?
 o What clues show a system is needed?

o How will the company and users benefit?

2. How should we develop the system?

o Who will build it?

o What strategy will we use?

3. What process will we follow to build it?

 These questions are connected and often lead to more detailed questions during
development.
4. Key success factors:
 Top management support: get approval and resources early.
 Employee participation: involve them in capturing knowledge, which makes
development easier.
5. Life cycle analogy:
A life cycle is just a structured way to do something from start to finish. Examples:
 College → Admission → Classes → Graduation
 Writing a term paper → Introduction → Body → Conclusion → References
 Air flight → Boarding → Takeoff → Cruising → Landing → Exiting
Life cycles share important traits:
 Organized into clear phases.
 Well-documented for future updates.
 Coordinated to finish on time.
 Reviewed regularly.
Bottom line:
Just like chapters and paragraphs give order to a book, a structured life cycle gives order to
building a KM system. Without it, the system may exist, but it will be confusing and ineffective.

Challenges in Building Knowledge Management (KM) Systems

Building a KM system sounds exciting, but there are several challenges:
1. Culture:
o People naturally hold onto knowledge because it gives them power.
 o Getting employees to share what they know requires changing attitudes and
behaviors.
o The company must create incentives that make knowledge sharing rewarding for
both employees and the organization.
2. Knowledge Evaluation:
o To improve KM and reward employees, a company needs to know the value of
the knowledge being shared.
o Measuring the worth of knowledge is tricky, and reliable methods are not fully
developed yet.
3. Knowledge Processing:
o KM is not just about storing data—it’s about understanding how decisions are
made.
o Systems must capture, store, and share knowledge that isn’t easily written in
tables, like experience or insights.
4. Knowledge Implementation:
o Companies must commit to change, learning, and innovation.

o Technology allows knowledge sharing anytime and anywhere.

o Lessons learned should be stored so others can use them in the future, like
debriefing prisoners of war to improve survival strategies.
Bottom line: Successful KM requires changing culture, measuring and processing knowledge
properly, and applying it to improve decision-making and performance.

Conventional Systems vs. Knowledge Management (KM) Systems

Building a KM system is different from building a traditional information system. Here’s how:
1. Source of Information:
o Conventional systems rely on data from users who know the problem but not the
solution.
o KM systems rely on knowledge from experts who know both the problem and the
solution.
2. Interaction:
o Systems analysts work mainly with regular users.
 o Knowledge developers work mainly with experts in the company.

3. Development Process:
o Conventional systems follow a strict step-by-step process: analyze → design →
build → test.
o KM systems evolve incrementally. They use rapid prototyping, improving the
system as it develops.
4. Testing:
o Conventional systems are tested at the end.

o KM systems are tested continuously during development.

5. Maintenance:
o Conventional systems require strict ongoing maintenance.

o KM systems are maintained by knowledge editors who update and improve the
system.
6. Focus:
o Conventional systems are process-driven and documentation-heavy.

o KM systems are result-driven, growing and improving gradually.

7. Prototyping:
o Conventional systems rarely use rapid prototypes.

o KM systems use prototypes to capture, refine, and verify knowledge until the
system is ready.
Bottom line: KM systems are more flexible, interactive, and expert-driven than conventional
systems, emphasizing learning and adaptation rather than following rigid steps.
Here’s a detailed, simplified explanation of the key similarities between conventional system
development and Knowledge Management System Life Cycle (KMSLC):

Key Similarities Between Conventional Systems and KM Systems

Even though conventional information systems and KM systems have major differences, they
share several important similarities:
1. Problem-to-Solution Approach:
o Both start by identifying a problem and end by providing a solution.
 o The goal in both cases is to benefit the organization and the users. In conventional
systems, this might mean automating a process or improving data flow, while in
KM systems, it means providing accurate, useful knowledge to make better
decisions.
2. Early Phase – Gathering Information or Knowledge:
o In conventional systems, the early stage involves gathering information from
users to understand the problem fully and define requirements. This is critical for
building a system that works effectively.
o In KM systems, the early stage involves knowledge capture—collecting
expertise and insights from employees or experts. This captured knowledge forms
the foundation of the KM system’s knowledge base.
o In both cases, it is crucial to represent the information or knowledge properly
so the system can process it and provide valuable outputs. Without proper
representation, both systems will fail to deliver meaningful results.
3. Verification and Validation:
o Both types of systems require testing to ensure quality and reliability.

o Verification ensures the system is free from errors and functions correctly. In
conventional systems, this is like alpha testing or debugging programs. In KM
systems, verification ensures that the knowledge has been captured and structured
correctly.
o Validation checks whether the system meets the user’s needs. In conventional
systems, this corresponds to beta testing or user acceptance testing. In KM
systems, validation ensures that the knowledge system actually provides useful
insights and answers for employees and decision-makers.
4. Tool Selection:
o Both systems require careful selection of the appropriate tools for design,
development, and implementation.
o Conventional system developers choose programming languages, databases, and
software frameworks.
o Knowledge developers select tools for capturing, storing, processing, and
distributing knowledge, including collaboration platforms, databases, and
sometimes AI-based knowledge extraction tools. The right tools in both cases are
essential for creating an efficient and reliable system.
5. Structured Process and Planning:
 o Both life cycles benefit from clear planning, disciplined phases, and organized
documentation.
o Even though KM systems may be more incremental and flexible, like
conventional systems, they require a roadmap, defined steps, and a strategic plan
to ensure the system grows in a controlled and purposeful way.
6. User-Centered Focus:
o Both systems focus on the end-users and aim to solve real problems for them.

o In conventional systems, this might involve streamlining operations or providing

accurate reports.
o In KM systems, it involves ensuring employees can access the right knowledge
when they need it, which supports better decision-making, faster problem-solving,
and overall organizational learning.
Summary:
While conventional systems and KM systems differ in methodology and interaction with experts,
they share a common foundation: both begin with a problem, gather necessary information or
knowledge, undergo verification and validation, require proper tools, and are designed to provide
solutions that serve users and the organization. Understanding these similarities helps
organizations transition more smoothly from traditional systems to KM systems while
maintaining discipline, structure, and a user-centered approach.

Users and Knowledge Workers: Roles and Differences

When developing systems, it’s important to understand the distinction between users and
knowledge workers (experts), because they interact differently with the system and the
developers:
1. Cooperation and Contribution:
o Users cooperate with the systems analyst by providing information and
documents. They help the system builder understand the problem so the system
can meet their needs.
o Knowledge workers (experts) provide their specialized knowledge or expertise.
They “own” the knowledge, meaning they control it and share it selectively.
While they are usually cooperative, their participation is not guaranteed, so
developers must approach them carefully and respectfully.
2. Interest in the System:
o Users have a direct interest in the system because they will ultimately use it.
Their satisfaction is critical.
 o Experts often do not use the system themselves; their main role is to provide
accurate knowledge. They are less invested in the system’s success as users.
3. Tolerance for Ambiguity:
o Users generally prefer clear, structured processes and can struggle with
uncertainty.
o Experts are more comfortable with ambiguity because their knowledge is often
complex, nuanced, or context-specific.
4. Dependence on the System:
o Users depend heavily on the system to perform their tasks effectively.

o Experts have little to no dependence on the system since they are not the final
users.
5. Knowledge of the Problem:
o Users usually understand the problem well but not necessarily the solution.

o Experts have detailed knowledge of the solution but may not fully grasp all
aspects of the problem as experienced by users.
6. Availability:
o Users are usually easy to reach and consult during system development.

o Experts are often less available because their primary responsibilities may lie
elsewhere, making careful scheduling and engagement essential.

Summary Table (Simplified):

Attribute User Expert

Dependence on system High Low to none

Cooperation Usually cooperative Cooperation not required

Tolerance for Low High

ambiguity

Knowledge of problem High Average/low

Contribution to system Information Knowledge/expertise

System user Yes No

 Availability Readily available Not readily available

Bottom line:
Users provide the context and validate the system, while experts supply the knowledge and
expertise that make the system meaningful. Successful system development depends on
balancing input from both groups carefully and recognizing their different motivations and
roles.

Knowledge Management System Life Cycle (KMSLC)

The KMSLC provides a structured roadmap for developing knowledge management (KM)
systems. Unlike conventional system development, KM systems emphasize capturing,
organizing, and disseminating human knowledge, especially tacit knowledge, to enhance
organizational learning and productivity.
1. Evaluate Existing Infrastructure
Objective: Assess the current knowledge environment to identify gaps and justify the need for a
KM system.
Key Steps:
 System Justification: Determine if the system is necessary based on factors like
knowledge loss due to retirements, distributed expertise needs, complexity of problem-
solving, and availability of expert knowledge. Example: BANKOR needed a KM system
to maintain consistent auditing across multiple states.
 Scope Definition: Limit project breadth and depth to ensure timely and manageable
development. Consider technological readiness, gaps in current systems, and benefits of
KM tools.
 Feasibility Analysis: Address economic (cost/benefit), technical (IT infrastructure
compatibility), and behavioral (training and adoption) feasibility.
Strategic Insight: Early evaluation ensures top management buy-in and prevents wasted
resources. Projects without internal champions or proper scoping are prone to failure.

2. Form the KM Team

Objective: Build a cross-functional team to oversee KM system development.
Key Considerations:
 Identify key stakeholders and expert representatives from relevant units.
  Balance team size (4–20 members is optimal) and competencies (technical, strategic, and
organizational).
 Focus on leadership, team motivation, and clear delivery expectations.
Pitfall: Overpromising capabilities or including too many members can stall coordination
and productivity.
3. Knowledge Capture
Objective: Elicit, analyze, and codify tacit and explicit knowledge for the KM system.
Activities:
 Interview experts and users to extract heuristics and practical knowledge.
 Capture tacit knowledge via observation, data mining, and team tasks.
 Validate knowledge iteratively through rapid prototyping (small-scale system
refinement through repeated expert feedback).
Strategic Insight: Knowledge capture is continuous—verification and adaptation occur
throughout the life cycle. Single or multiple experts may be involved depending on the
complexity of the problem domain.
4. Design the KM Blueprint
Objective: Create the system’s architecture and IT infrastructure plan.
Key Layers of the KM System (see Figure 3.8 in source):
1. User Interface: Access point for knowledge users; critical for adoption.
2. Authentication/Security Layer: Ensures data integrity, access control, and compliance.
3. Collaborative Agents & Filtering: Intelligent agents customize knowledge delivery.
4. Application Layer: Supports workflows, e.g., email, document exchange, decision
support.
5. Transport/Internet Layer: Manages communication protocols (TCP/IP, SMTP).
6. Physical Layer: Hardware and network infrastructure.
7. Repositories: Storage of explicit and tacit knowledge, legacy data, and databases.
Strategic Insight: The KM blueprint ensures interoperability, scalability, and alignment
with organizational goals.
5. Test the KM System
Objective: Verify and validate system functionality and usability.
 Verification: Ensure rules and knowledge work correctly; test internal system logic.
  Validation: Confirm the system meets user expectations, solves problems reliably, and is
user-friendly.
Strategic Insight: Continuous monitoring is essential; validation is ongoing, not a one-
time check.
6. Implement the KM System
Objective: Deploy the system and integrate it into organizational operations.
 Conversion to operational use
 Post-implementation review and system maintenance
 User Training: Tailored by skill level and role (tutor, pupil, customer). Manuals and job
aids reinforce adoption.
Strategic Insight: Implementation is not only technical but behavioral—user
engagement and practical training determine success.

7. Manage Change and Reward Structure

Objective: Facilitate knowledge sharing and adoption while mitigating resistance.
 Address concerns of experts and regular users.
 Create incentives for participation.
 Communicate benefits clearly to reduce anxiety and resistance.
Strategic Insight: Cultural alignment and reward structures are as critical as technology
in ensuring KM system adoption.

8. Evaluate and Refine

Objective: Measure system performance, capture new knowledge, and refine the system.
 Monitor ROI, user satisfaction, and knowledge integrity.
 Update repositories based on feedback and evolving organizational needs.
Strategic Insight: KM systems are dynamic—they must evolve with business
requirements and knowledge growth.

Supporting Roles
 Knowledge Developer: Central orchestrator—captures knowledge, develops heuristics,
manages the project, ensures quality, and liaises with experts and users.
  Champion: Senior leader advocating for KM adoption; secures resources and aligns
strategy.

Strategic Takeaways
 KM systems are iterative and human-centered; conventional SDLC methods are adapted
to emphasize knowledge elicitation and validation.
 Early management support, expert cooperation, and user engagement are critical success
factors.
 Rapid prototyping accelerates knowledge capture and system refinement, reducing risk.
 Cultural, technical, and economic feasibility must be assessed holistically.

Chapter 4 — Knowledge Creation & Knowledge

Architecture (Comprehensive Notes)s
1. Core Idea of the Chapter
This chapter addresses three foundational questions:
1. Where knowledge resides — in people or in systems?
2. How knowledge is created and transformed within organizations.
3. How to design a knowledge architecture that supports learning, sharing, and
innovation.
Key Thesis:
Knowledge does not reside in data or documents; it exists in people and is created when
individuals interpret information and apply it in context.
Implications:
 Databases store information.
 Knowledge emerges when humans interpret and contextualize information.
 Organizations must create systems, culture, and processes that allow knowledge to flow,
be applied, and continuously evolve.
Philosophical Roots:
Thinkers like Leibniz, Locke, and Kant, as interpreted by Churchman, stressed that knowledge
is user-driven. Boland (1987) and Gill (1995) emphasized that knowledge is human,
contextual, and dynamic, not a static asset.

2. Knowledge Creation in Organizations

Definition:
Knowledge creation is the process by which individuals or organizations develop new insights,
understandings, or solutions by interpreting information, reflecting on experiences, and applying
them in context to generate value.
Knowledge is dynamic, requiring constant renewal to remain relevant. Static knowledge decays
with market, technology, or competitor changes.
Example: A teacher repeating the same lesson for decades gains experience but does not expand
knowledge; updating approaches based on feedback is essential.
Organizational Knowledge Creation Cycle

Step Description

Experience Work is performed; individuals and teams engage in tasks.

Reflection Outcomes are analyzed against expectations; successes and failures evaluated.

Abstraction Lessons learned are distilled into principles or rules.

Application Insights are applied to new situations, generating improvement and innovation.

Key Insight: Knowledge creation is both personal and social. While individuals generate
insight, teams, processes, and culture determine whether knowledge is shared or lost.

3. Knowledge Creation Through Teams

Teams are the engine of organizational learning, combining diverse expertise and perspectives
to generate richer understanding.
Why Teams Matter:
 They bring diverse expertise and experiences.
 They allow comparative insight—contrasting views on similar problems.
 They create shared understanding and collective memory.
Characteristics of Effective Knowledge-Creating Teams:

Attribute Explanation

Psychological Trust Members feel safe to share uncertain or incomplete ideas.

Open Communication
Free flow of information without hierarchical blockages.
Channels

Reflection Rituals Regular debriefs, retrospectives, and after-action reviews.

Knowledge is collective; ownership is distributed across the

Shared Accountability
team.

Critical Point: Knowledge Management (KM) is primarily social, not just technological.
Technology facilitates, but culture and human dynamics drive creation.

4. Barriers to Knowledge Sharing

Knowledge sharing is influenced by psychology, culture, and organizational systems. Not
everyone contributes automatically.

Factor Effect Explanation

Personality Shapes willingness Some individuals naturally share; others hoard.

Attitude Affects openness Curious, positive employees share more readily.

Work Norms Social expectations Norms encouraging sharing increase participation.

Reinforcers Incentives Recognition, promotions, and rewards motivate sharing.

Observation: Without recognition and psychological safety, knowledge remains trapped within
individuals, limiting organizational learning.

5. Nonaka’s Knowledge Creation Model (SECI Model)

Ikujiro Nonaka (1995) introduced a dynamic knowledge creation model explaining the
interaction between tacit and explicit knowledge.
Two Forms of Knowledge

Type Nature Examples

Tacit Knowledge Personal, experience-based, hard to articulate Intuition, craft skills, insights
Type Nature Examples

Explicit Knowledge Codified, documented, easily shared Manuals, reports, procedures

The SECI Cycle

Mode Conversion Mechanism Example

Shared experience,
Socialization Tacit → Tacit Apprenticeship, shadowing
observation

Externalization Tacit → Explicit Dialogue, articulation Documenting best practices

Explicit → Integration and Creating manuals/training

Combination
Explicit reorganization guides

Internalization Explicit → Tacit Learning-by-doing Practice, simulations, training

Essential Insight: The SECI cycle thrives only when culture, structure, and technology
actively support the flow between tacit and explicit knowledge.
The SECI cycle is a foundational framework in knowledge management introduced by Ikujiro
Nonaka, explaining how knowledge is created, shared, and transformed within
organizations. SECI stands for Socialization, Externalization, Combination, and
Internalization, representing a continuous and dynamic cycle of interaction between tacit
knowledge (personal, experience-based, hard to articulate) and explicit knowledge (codified,
documented, easily shared). Understanding this cycle is essential because organizations rely not
just on storing information, but on converting knowledge into actionable insights that drive
innovation and learning.

1. Socialization (Tacit → Tacit)

Definition: Socialization is the process of transferring tacit knowledge from one individual to
another through shared experience and direct interaction, without formal documentation.
Mechanisms:
 Observation: Learning by watching experienced colleagues perform tasks.
 Mentorship and Apprenticeship: New employees gain knowledge by shadowing experts.
 Informal Discussions: Brainstorming sessions, coffee chats, and collaborative problem-
solving.
 Storytelling: Sharing experiences, lessons, and anecdotes to convey subtle insights.
Example: A junior engineer learning troubleshooting techniques by observing a senior engineer
handle machine failures. Over time, the junior engineer internalizes these skills and develops
their own intuition.
Key Insight: Socialization is highly context-dependent; knowledge is shared through
experience and immersion, not written documents. Organizational culture that encourages trust,
openness, and collaboration enhances this phase.

2. Externalization (Tacit → Explicit)

Definition: Externalization is the process of converting tacit knowledge into explicit
knowledge so it can be documented, shared, and applied more broadly across the organization.
Mechanisms:
 Dialogue and Reflection: Team discussions that articulate insights and ideas.
 Concept Mapping: Visualizing knowledge, relationships, and workflows.
 Writing Manuals, Reports, or Guidelines: Capturing personal know-how in formal
documentation.
 Brainstorming and Modeling: Expressing mental models and heuristics in a structured
form.
Example: An experienced sales manager documents their approach to closing difficult deals,
creating a best-practices guide that junior sales staff can study and apply.
Key Insight: Externalization requires language, metaphors, and models to translate personal,
intuitive knowledge into a form others can understand. Without effective externalization,
valuable tacit knowledge remains inaccessible.

3. Combination (Explicit → Explicit)

Definition: Combination is the process of merging, synthesizing, and reorganizing explicit
knowledge from multiple sources to create new, structured knowledge that is more
comprehensive.
Mechanisms:
 Integrating reports, databases, and manuals from different departments.
 Compiling lessons learned from multiple projects into a unified framework.
 Editing and reorganizing existing documents to improve clarity and applicability.
  Creating standard operating procedures or training guides.
Example: A project manager consolidates post-project reports from different teams into a single
organizational knowledge repository, identifying common challenges and successful
strategies.
Key Insight: Combination allows organizations to leverage collective knowledge
systematically. This step turns scattered explicit knowledge into coherent, actionable insights that
can be widely applied.

4. Internalization (Explicit → Tacit)

Definition: Internalization is the process through which individuals absorb explicit knowledge
and convert it into tacit knowledge through practice, experience, and reflection.
Mechanisms:
 Learning by doing: Applying documented procedures to real-life tasks.
 Simulations and role-playing: Experiencing hypothetical scenarios to internalize lessons.
 Training programs and workshops: Transforming formal guidelines into skills and
intuition.
 Reflection on outcomes: Understanding what worked, why, and how it can be improved.
Example: Employees study a newly created manual on customer service protocols and, through
practice and reflection, develop intuition and judgment for handling complex customer
interactions.
Key Insight: Internalization ensures that explicit knowledge becomes personal and actionable,
feeding back into the tacit knowledge base of the organization. This completes the cycle and
enables continuous learning.

5. The Continuous and Spiral Nature of SECI

The SECI cycle is not linear; it operates as a spiral, where knowledge evolves through repeated
iterations of the four modes:
1. Socialization creates tacit insights.
2. Externalization converts insights into explicit knowledge.
3. Combination integrates and expands explicit knowledge.
4. Internalization converts explicit knowledge back into tacit knowledge within individuals.
With each iteration, knowledge becomes more refined, shared, and actionable, spreading
across individuals, teams, and the organization.
Strategic Implications:
 Organizations must support all four modes through culture, leadership, and technology.
 Technology facilitates storage, access, and collaboration, but cannot replace human
reflection and social interaction.
 Effective SECI implementation drives innovation, competitive advantage, and
continuous organizational learning.
6. Knowledge Architecture
Knowledge architecture is a blueprint defining knowledge flow, roles, processes, and
technology in an organization. It ensures knowledge is accessible, actionable, and updated
continuously.
Three Core Components
1. People Core — the primary source and carriers of knowledge.
2. Content Core — what knowledge is stored and how it’s structured.
3. Technology Core — systems enabling sharing and access, without creating knowledge
independently.

7. People Core
Human capital is the engine of knowledge creation.
Steps to Build the People Core
1. Identify knowledge holders — map who creates, uses, or depends on what knowledge.
2. Establish communities of practice — cross-functional groups for knowledge sharing.
3. Profile roles — categorize employees based on knowledge creation, usage, and
communication.
Example: “Expert forums,” skill guilds, and mentorship networks help form interconnected
knowledge nodes.

8. Content Core
The content core organizes and maintains knowledge systematically.
  Knowledge Centers — broad domains (Marketing, Operations).
 Satellites — sub-domains within each center (Quality Control, Procurement).
Responsibilities:
 Assign content owners to maintain accuracy, updates, and accessibility.
 Prevent knowledge decay through systematic curation.
Example: In banking, Operations (teller transactions), Loans (commercial, personal), Customer
Service (complaints, accounts).

9. Technology Core
Technology enables knowledge flow, storage, and collaboration, but does not replace human
insight.
Design Principles:
 Support search, collaboration, personalization, and continuous updates.
 Avoid over-automation or rigid decision-making systems.
 Ensure user-friendly interfaces and incremental improvement of existing infrastructure.

10. Seven Technical Layers of KM Architecture

Layer Purpose Key Features

User Interface Interaction point Dashboards, visual navigation, personalization

Access Security & permissions Authentication, intranet/extranet control

Collaborative Filtering &

AI agents, search relevance, user profiles
Intelligence recommendations

Knowledge Expert systems, decision support, discussion

Value-adding tools
Applications databases

LAN/WAN, Internet connectivity, bandwidth

Transport Communication channels
management

Bridges legacy and modern systems, ensures

Middleware System integration
compatibility

Repositories Storage Data warehouses, archives, libraries; integrated

Layer Purpose Key Features

and updated

Observation: A KM system succeeds only when all seven layers function seamlessly and
interoperate.
Knowledge Architecture is the strategic blueprint that defines how knowledge is created,
stored, shared, and applied within an organization. It ensures that knowledge flows efficiently
between people, processes, and technology, enabling organizations to learn continuously,
innovate, and maintain a competitive edge. Unlike mere data systems, knowledge architecture
focuses on human understanding, interaction, and application, supported by technology but
not replaced by it.
The ultimate goal is to design a system where knowledge is accessible, actionable, and
constantly updated, transforming individual insights into organizational intelligence.

Three Core Components of Knowledge Architecture

Knowledge architecture is composed of three interdependent cores: People, Content, and
Technology. Each core plays a distinct role, but they must operate in harmony for the system to
function effectively.

1. People Core
Definition: The People Core represents the human element, the creators, carriers, and users of
knowledge. Knowledge resides in individuals; technology only facilitates its sharing and
application.
Key Functions:
 Identify Knowledge Holders: Map employees based on their expertise, tacit knowledge,
and experience.
 Facilitate Knowledge Sharing: Create communities of practice, skill guilds, mentorship
networks.
 Break Silos: Enable cross-functional collaboration to prevent knowledge hoarding.
 Assign Roles: Define who creates, uses, and communicates knowledge.
Example: In a consulting firm, senior consultants mentor juniors, share lessons learned, and
contribute insights to a centralized knowledge repository.
Strategic Insight: Without a strong People Core, even the best systems fail, as knowledge
creation and application depend on human understanding, trust, and collaboration.

2. Content (Knowledge) Core

Definition: The Content Core organizes what knowledge is stored and how it is structured. It
ensures that knowledge is accurate, accessible, and continuously updated.
Key Elements:
 Knowledge Centers: Broad domains (e.g., Marketing, Operations, Finance) where core
knowledge resides.
 Satellites: Sub-domains within each center (e.g., Marketing → Customer Analytics,
Brand Management).
 Content Ownership: Assign experts to maintain, update, and validate content.
 Structure & Accessibility: Ensure knowledge is easy to navigate and retrieve.
Example: A bank may have a Knowledge Center for Operations, with satellites for Teller
Procedures, Loan Processing, and Customer Service, each maintained by domain experts.
Strategic Insight: The Content Core ensures that organizational knowledge remains reliable,
structured, and usable, reducing errors and enhancing decision-making.

3. Technology Core
Definition: The Technology Core enables knowledge flow, storage, and collaboration, but it
does not create knowledge by itself.
Key Functions:
 Search & Retrieval: Fast, intelligent search systems for locating relevant knowledge.
 Collaboration Tools: Discussion forums, shared workspaces, and project platforms.
 Integration: Ensures interoperability with existing systems (CRM, ERP, document
management).
 Continuous Updating: Supports version control, backups, and knowledge validation.
Example: A KM system using cloud-based repositories, AI-powered search, and collaborative
platforms to allow employees to share insights across global offices.
Strategic Insight: Technology amplifies human knowledge, enabling faster access, sharing,
and application, but it cannot replace human insight or context.

Integration of the Three Cores

The effectiveness of knowledge architecture lies in how well these three cores interact:
1. People generate and interpret knowledge.
2. Content organizes and preserves knowledge.
3. Technology distributes and facilitates access to knowledge.
When aligned, this triad creates a continuous cycle of knowledge creation, sharing, and
application, driving organizational learning and innovation.

Summary: Knowledge Architecture is not just a system or a database—it is a holistic design

that integrates people, content, and technology to ensure knowledge flows seamlessly across
the organization, empowering employees to act, learn, and innovate effectively.

If you want, I can now create a visual diagram showing the three cores of knowledge
architecture with examples, making it presentation-ready and easy to memorize.
Do you want me to do that?

11. Build, Buy, or Outsource KM Systems

Decision criteria depend on:
 Budget, time, and skills
 Degree of customization required
 Strategic priorities

Approach Advantages Disadvantages Suitable For

In-house Fully tailored High cost, high risk Large firms with IT capability

Organizations lacking internal IT

Outsourcing Fast execution Less control
expertise

Off-the-shelf Low cost, quick Limited Small/medium enterprises

Approach Advantages Disadvantages Suitable For

setup customization

Evaluation Considerations: Reliability, scalability, usability, vendor dependency, and

performance.
When organizations implement a Knowledge Management (KM) system, they must decide
whether to build it in-house, buy off-the-shelf software, or outsource development. This
decision is strategic because it affects costs, customization, control, scalability, and alignment
with organizational needs. Each approach has distinct advantages, limitations, and suitable
contexts.

1. Build In-House (Custom Development)

Definition: Developing the KM system internally using the organization’s own IT and KM
teams.
Advantages:
 Fully tailored solution: Can meet the organization’s unique processes, culture, and
knowledge flows.
 High control: The organization can dictate system features, updates, and integration with
other tools.
 Scalable & Flexible: Can evolve gradually as organizational needs change.
Disadvantages:
 High cost: Requires significant investment in development, maintenance, and staff
training.
 Time-consuming: Design, development, and deployment take longer.
 High risk: Potential for delays, technical failures, or design flaws if expertise is
insufficient.
Suitable For: Large organizations with strong IT capacity, strategic KM initiatives, or complex
knowledge requirements.
Example: A multinational consulting firm designing a proprietary KM platform integrating
internal knowledge repositories, collaboration tools, and AI-driven search engines.

2. Buy Off-the-Shelf Tools

Definition: Purchasing commercially available KM software that provides ready-made features.
Advantages:
 Lower cost and faster deployment: Immediate access to standard KM functionalities.
 Proven technology: Vendor-tested systems reduce technical risk.
 Basic customization possible: Many solutions allow minor configuration.
Disadvantages:
 Limited customization: May not fully align with unique workflows or culture.
 Dependency on vendor: Updates, maintenance, and support rely on external parties.
 Potential integration issues: May not work seamlessly with legacy systems.
Suitable For: Small to medium organizations needing standard KM capabilities quickly, without
major customization.
Example: A mid-sized company purchasing a cloud-based KM tool for document management,
collaboration, and workflow tracking.
3. Outsourcing (Third-Party Development)
Definition: Hiring an external vendor or consultant to design and implement a custom KM
system.
Advantages:
 Faster development: Experts with experience can implement systems efficiently.
 Access to specialized skills: Useful for organizations lacking in-house IT or KM
expertise.
 Flexible contracts: Can be tailored for development, implementation, and maintenance
support.
Disadvantages:
 Less internal control: Organization relies on external vendors for key decisions.
 Knowledge transfer risks: Critical knowledge may reside with the vendor rather than
the organization.
 Ongoing dependency: Long-term reliance on the vendor for updates, bug fixes, and
support.
Suitable For: Organizations with budget flexibility and limited internal IT capacity, aiming for
a custom system without building it entirely in-house.
Example: A pharmaceutical company outsourcing the development of a KM platform
integrating R&D reports, regulatory documentation, and collaboration tools.
Evaluation Criteria for Choosing an Approach
When deciding, organizations should consider:
1. Budget & Resources: How much can the organization invest in development,
maintenance, and training?
2. Customization Needs: Does the organization need a unique system tailored to its
processes?
3. Time Pressure: Is rapid deployment essential?
4. Internal Expertise: Does the organization have skilled IT and KM personnel?
5. Integration & Scalability: How easily can the system integrate with existing tools and
scale with growth?
6. Reliability & Support: Are vendor guarantees, service-level agreements (SLAs), and
maintenance plans sufficient?
Strategic Insight
 In-house development is ideal for strategic, long-term KM goals where control,
customization, and flexibility are priorities.
 Off-the-shelf solutions are optimal for quick implementation with moderate
functionality, especially in smaller organizations.
 Outsourcing is a middle path, offering customization without full internal
development costs, but requires careful vendor management to mitigate dependency
risks.
Summary: Choosing between build, buy, or outsource depends on the organization’s strategic
priorities, budget, timeline, and internal capabilities. The decision must balance control, cost,
speed, and alignment with organizational knowledge goals to ensure the KM system supports
continuous learning, innovation, and competitive advantage
12. Strategic Implications for Knowledge Management
Effective KM requires:
 Technology as an enabler, not controller.
 Culture promoting trust, sharing, and reflection.
 Leadership modeling continuous learning.
  CKO-led governance ensuring accountability and integration.
Cultural and Strategic Takeaways:
 Knowledge is created socially, through interaction, reflection, and shared experience.
 Tacit and explicit knowledge constantly transform via SECI.
 Multi-layered architecture and human-centric design ensure sustainability and
efficiency.
 Human creativity remains the ultimate driver, with technology amplifying its reach.

13. Summary of Chapter Insights

 Knowledge creation occurs through experience and teamwork.
 Sharing depends on psychological, cultural, and organizational factors.
 Knowledge architecture integrates people, content, and technology.
 A multi-layered technical system supports capture, access, and collaboration.
 Building or buying KM solutions depends on strategic fit, resources, and flexibility.
 Human creativity remains the ultimate source of knowledge, with technology as its
enabler.

Chapter 5: Capturing Tacit Knowledge.

CAPTURING TACIT KNOWLEDGE — DETAILED NOTES
1. In a Nutshell
 KM systems depend on the quality and completeness of knowledge they contain.
 The first step in developing a KM system is capturing tacit knowledge, which is:
o Personal

o Experience-based

o Difficult to articulate

o Stored in experts’ minds

  Knowledge developers must convert tacit “know-how” into explicit, machine-
readable “say-how.”
 Process is iterative and refinement-based (rapid prototyping).
 Challenges include:
o Time demands on experts

o Loss of expert motivation

o Interpersonal fit between expert & knowledge developer

o Selecting the right capture approach (single vs. multiple experts, interview type,
environment)

2. What is Knowledge Capture?

Knowledge Capture = Extracting the expert’s internal reasoning, patterns, and experiential
rules and translating them into structured form.
Key Elements:
1. Elicitation: Understanding how the expert thinks and works.
2. Interpretation: Identifying hidden heuristics and mental models.
3. Codification: Converting reasoning into rules, decision trees, cases, or structured logic.
Methods may involve:
 Interviews
 Case-based reasoning
 Observing expert performance
 Protocol analysis
 Documentation review

3. Evaluating the Expert

To capture useful knowledge, the expert must be:
 Respected by peers
 Consulted regularly for decisions
  Capable of introspection and explanation
 Honest about limits
 Focused and not prone to irrelevant information
 Clear communicators
Key Expert Qualities:

Quality Description

Uses judgment wisely Knows when to apply rules vs. exceptions

Sees the big picture Identifies relationships among variables

Communicates effectively Explains ideas clearly and adaptively

Tolerates stress Patient during interview cycles

Creative reasoning Can articulate why solutions work

Self-confidence Not threatened by being questioned

Shares willingly Doesn’t hoard knowledge

Thinks in chunks Understands domain at pattern-level

4. Levels of Expertise

Level Characteristics Communication Style

Highly Expert Deep pattern recognition Concise but omits steps

Moderately Expert Strong knowledge + clarity Most detailed and useful explanations

New Expert Shallow experience Fragmented explanations

👉 Moderately Expert individuals are often best sources for capture because they articulate the
middle layers of reasoning more clearly.

5. Single vs. Multiple Experts

Single Expert
Advantages:
 Faster progress
  Easier scheduling & coordination
 Simpler prototyping
 Clear and consistent reasoning path
 Less risk of leaks/confidentiality issues
Drawbacks:
 Risk of bias
 Single viewpoint, no validation from others
 May overlook domain complexity
 System quality tied to one person’s clarity and motivation
Multiple Experts
Advantages:
 Captures diverse perspectives
 Reduces bias
 Better for complex or distributed knowledge domains
 Encourages synthesis and cross-validation
Drawbacks:
 Scheduling challenges
 Higher probability of disagreements
 Risk of dominance by senior experts
 Requires more skilled facilitation

6. Developing Relationships with Experts

Creating the Right Impression
 Build trust early.
 Show respect for the expert’s experience.
 Demonstrate preparedness.
 Avoid acting superior or naïve.
Understanding Expert Style

Style Type Behavior Developer Strategy

Procedure-Oriented Logical, structured Keep them focused

Storyteller Shares anecdotes at length Use structured questioning

Godfather Dominates discussions Maintain boundaries tactfully

Salesperson Persuasive and evasive Redirect gently toward specifics

Session Preparation
 Learn terminology beforehand.
 Set clear objectives.
 Present purpose honestly and respectfully.
Location
 Preferably expert’s workspace (comfort, tools, familiarity)
 Ensure minimal interruptions.
Approaching Multiple Experts
 Individual sessions
 Primary + secondary expert hierarchy
 Small group sessions (limit size to avoid communication overload)

7. Fuzzy Reasoning and Language Challenges

Experts often use vague and imprecise descriptors, such as:
 “Most of the time”
 “Very likely”
 “Not worth doing”
 “Warm / cold / high / low / significant”
Knowledge developer must:
 Clarify meaning repeatedly
 Request examples
  Use case scenarios to anchor language

8. Interview as a Knowledge Capture Tool

Why Interviews?
 Flexible
 Allows observation of reasoning processes
 Reveals emotion, intuition, pattern recognition
Types of Interviews

Type Use Case Advantage Risk

Exploring unknown Can wander away from

Unstructured Encourages openness
domains core issues

May feel rigid, limits

Structured Need consistent comparison Clear, formal
nuance

Semi- Balanced exploration + Best for most KM

Requires interview skill
Structured consistency capture

Guide to Successful Interviews

1. Establish rapport (respect, confidentiality, purpose)
2. Phrase questions carefully
3. Avoid arguments or interruptions
4. Evaluate insights for clarity, reasoning, and completeness
Things to Avoid
 Challenging the expert aggressively
 Pretending you understand
 Using unnecessary technical jargon
 Letting expert derail focus
 Making unrealistic promises (e.g., timelines)
9. Rapid Prototyping in Interviews
 Build early and rough system versions
 Compare system reasoning vs. expert reasoning
 Iterate to refine accuracy
 Maintains expert engagement by showing progress
Benefits: Keeps momentum, reveals misunderstandings quickly
Drawbacks: Can lock in incorrect assumptions if done too soon or without review

10. Implications for KM

Effective tacit knowledge capture:
 Preserves core organizational expertise
 Enables training, automation, support, and decision consistency
 Reduces future dependency on specific individuals
 Enhances innovation by making knowledge reusable and shareable

Chapter 6: Other Knowledge Capture Techniques —

Detailed Exam-Ready Note
In a Nutshell

Knowledge developers use specialized tools to extract, capture, and structure expert knowledge.
The choice of tool depends on:

 Whether it involves a single expert or multiple experts

 The nature of the problem (simple, complex, uncertain, or cross-disciplinary)
 The goal — observation, idea generation, evaluation, or consensus.

Key Techniques Covered:

1. On-Site Observation
2. Brainstorming & Electronic Brainstorming
3. Protocol Analysis (Think-Aloud Method)
4. Consensus Decision Making
5. The Repertory Grid
6. Nominal Group Technique (NGT)
7. The Delphi Method
 8. Concept Mapping & Semantic Nets
9. Blackboard (Groupware) Technique

Each technique offers a different pathway to uncover expert insights, structure tacit knowledge,
and convert it into usable, explicit knowledge for Knowledge Management Systems (KMS).

Overview

 Complex problems often require multiple experts from diverse fields.

 Knowledge developers must be skilled facilitators, managing both technical and
interpersonal aspects of knowledge capture.
 Proper planning, fairness, and structured procedures ensure that the knowledge
captured is both accurate and representative of real expert reasoning.

1. On-Site Observation

Definition:

A direct observation technique where the knowledge developer watches an expert perform real
tasks in their natural environment. Also known as action protocol.

Purpose:

 Capture real-time behavior, problem-solving logic, and subtle procedural nuances that
might not emerge in interviews.
 Ideal for single-expert systems where the knowledge lies in practice rather than verbal
explanation.

Procedure:

1. Observe the expert in action (e.g., bank teller, technician, doctor).

2. Record behaviors, decisions, and explanations.
3. Ask clarifying questions only during natural pauses — not during critical tasks.
4. Verify findings later through brief follow-up interviews.

Example:

A knowledge developer observed a senior bank teller to build a teller KM system for check
authorization.

 Teller’s decision accuracy: 95%

 Average bank officer’s accuracy: 70%
Observation revealed real judgment cues not captured in procedural manuals.

Advantages:
  Provides live insights into tacit knowledge.
 Contextual understanding of work environment.
 Complements interview data.

Limitations:

 Some experts dislike being watched.

 Observation may alter behavior (Hawthorne effect).
 Time gap between observation and recording can reduce accuracy.
 Can trigger resistance or tension among coworkers.

2. Brainstorming

Definition:

An unstructured group technique designed to generate creative ideas and possible solutions
without immediate evaluation.

Purpose:

Encourages divergent thinking—focusing first on the quantity of ideas rather than their quality.

Procedure:

1. Introduce the session — explain objectives and rules.

2. Present a problem from the experts’ domain.
3. Generate ideas — experts freely share suggestions.
4. Converge — ideas are grouped, refined, and evaluated.
5. Vote or reach consensus on the final few options.

Ground Rules:

 No criticism or judgment during idea generation.

 All ideas are welcomed and recorded.
 Aim for broad participation and idea fluency.

Example:

Experts brainstormed potential MIS research topics, later narrowing them through structured
discussion and voting.

Advantages:

 Encourages creativity and group synergy.

 Builds shared understanding of a problem.
  Simple, low-cost, and adaptable.

Limitations:

 Dominant personalities can overshadow others.

 Lack of structure may cause topic drift.
 Difficult to document ideas properly in large groups.

3. Electronic Brainstorming

Definition:

A computer-aided version of brainstorming where experts share ideas electronically in real

time through networked PCs.

Purpose:

Overcomes social barriers, promotes anonymity, and accelerates convergence of ideas.

Process:

 Experts connect via computers in a U-shaped layout.

 Ideas are typed and instantly displayed (without showing names).
 System categorizes and prioritizes inputs automatically.
 Voting and ranking features help finalize outcomes.

Advantages:

 Anonymity encourages open participation.

 Reduces influence of hierarchy and personality.
 Enables simultaneous input, saving time.
 Produces a clear record of all ideas.

Example:

Professors used IBM’s Electronic Brainstormer to create a list of field research projects —
quickly filtering duplicates and prioritizing top ideas.

4. Protocol Analysis (Think-Aloud Method)

Definition:

Experts verbalize their thoughts while solving a real problem. The developer records their
spoken reasoning—known as the protocol.
Purpose:

To understand how experts think, not just what they decide.

Steps:

1. Expert performs a real or simulated task.

2. Verbalizes every thought during problem-solving.
3. Developer records without interrupting.
4. Later, developer analyzes the transcript to identify cognitive patterns.

Example:

In the Diabetic Foot KM System, a surgeon verbalized his reasoning while diagnosing a patient.
His step-by-step logic helped encode medical knowledge into system rules.

Advantages:

 Captures deep cognitive processes.

 Makes experts aware of their own reasoning.
 Useful for building diagnostic or advisory KM systems.

Limitations:

 Time-intensive to analyze verbal data.

 Experts may struggle to articulate implicit thinking.
 May not suit high-pressure or fast-paced tasks.

5. Consensus Decision Making

Definition:

A structured process to achieve collective agreement among multiple experts after

brainstorming.

Procedure:

1. Present all previously generated solutions.

2. Conduct voting rounds to narrow options:
o Round 1: 3 votes per expert
o Round 2: 2 votes
o Final round: 1 vote for final solution
3. Continue until consensus is reached on the best option.

Advantages:
  Encourages fairness and shared ownership.
 Builds unity and support for final decision.

Limitations:

 Can be long, repetitive, or frustrating.

 Each option gets equal weight—can be misleading.
 Risk of conflict or walkouts due to rigidity.

6. The Repertory Grid

Definition:

A structured technique that reveals how an expert classifies, compares, and evaluates different
cases or examples.

Key Components:

 Constructs: Bipolar qualities (e.g., Experienced–Inexperienced, Satisfactory–

Unsatisfactory)
 Elements: Examples or individuals being rated (e.g., employees, patients)
 Scale: Usually 1–5, showing degree of each construct.

Example:

An HR manager rates tellers based on experience, appearance, punctuality, and personality.

The grid reveals consistent internal logic in expert judgments.

Advantages:

 Makes subjective reasoning explicit.

 Helps identify expert’s classification model.
 Promotes reflective thinking in experts.

Limitations:

 Hard to manage with large, detailed grids.

 Data interpretation can be complex.

7. Nominal Group Technique (NGT)

Definition:

A structured group ideation and ranking method that balances brainstorming with individual
reflection.
Procedure:

1. Experts are briefed on the issue.

2. Each writes pros and cons silently.
3. All ideas are compiled and duplicates removed.
4. Experts rank ideas individually.
5. Discussion follows to justify rankings.
6. Group agrees on the best solution(s).

Advantages:

 Equal participation, less dominance.

 Combines both idea generation and prioritization.
 Useful in uncertain or politically sensitive topics.

Limitations:

 Time-consuming and tedious.

 Requires strong facilitation to stay focused.

8. The Delphi Method

Definition:

An iterative survey-based method used to reach consensus among geographically dispersed

experts.

Process:

1. Experts receive a questionnaire on a specific issue.

2. Responses are summarized and shared anonymously.
3. Experts revise their views in light of others’ feedback.
4. Process repeats until opinions converge.

Features:

 Anonymity eliminates bias.

 Controlled feedback encourages reconsideration.
 Statistical aggregation represents the group’s collective wisdom.

Advantages:

 Suitable for forecasting and strategic planning.

 Reduces peer pressure and status effects.
 Works even with dispersed experts.
Limitations:

 Poorly designed surveys yield weak results.

 Experts may not always have sufficient context.
 Process may take several rounds.

9. Concept Mapping & Semantic Nets

Definition:

A visual tool that represents relationships among concepts through nodes (concepts) and links
(relationships).

Purpose:

To structure and visualize how experts perceive and connect knowledge elements.

Steps:

1. Preparation – identify participants and focus area.

2. Idea Generation – collect key concepts.
3. Statement Structuring – organize related concepts into clusters.
4. Representation – display relationships using maps or cluster analysis.
5. Interpretation – refine meaning with experts.
6. Utilization – apply or display maps in KM systems.

Semantic Nets:

 Similar to concept maps but more formal.

 Used to represent descriptive (declarative) knowledge in systems.

Advantages:

 Converts complex ideas into visual, memorable form.

 Encourages shared understanding.
 Useful in system design and training.

10. Blackboard (Groupware) Technique

Definition:

A computer-based collaborative system where multiple experts share ideas and refine
solutions on a shared “blackboard.”

Structure:
  Knowledge Sources (KS): Independent experts contributing solutions.
 Blackboard: Central shared memory or workspace.
 Control Mechanism: Coordinates inputs and ensures order.

Characteristics:

1. Diverse approaches to problem-solving.

2. Common language for interaction.
3. Flexible representation (text, diagrams, data).
4. Organized participation — one expert acts at a time.
5. Iterative refinement — solution evolves step-by-step.

Advantages:

 Supports complex, multidisciplinary problems.

 Encourages equal contribution and transparency.
 Provides a structured memory for collaboration.

Limitations:

 Technically demanding and rare in practice.

 Limited commercial software availability.
 Requires experienced developers.

Implications for Knowledge Management

 Tool selection must match expert type, problem complexity, and organizational
resources.
 Knowledge developers must balance technical expertise with interpersonal skills and
management awareness.
 Managerial support, funding, and communication are critical for success.
 The choice of method determines the accuracy, completeness, and usability of the
captured knowledge.

Summary Table

Technique Type Key Purpose Strength Limitation

On-Site Single Expert Capture real Realistic & Observer bias
Observation behavior direct
Brainstorming Multiple Generate ideas Creative Unstructured
Experts synergy
Electronic Multiple Faster idea Anonymity & Tech
Brainstorming sharing speed dependency
Protocol Analysis Single Capture cognitive Deep insight Time-
process consuming
 Consensus Multiple Achieve Democratic Tedious
Decision agreement
Repertory Grid Single Reveal expert Structured Complex with
logic evaluation large grids
Nominal Group Multiple Rank ideas Equal Time-heavy
systematically participation
Delphi Multiple Forecast & Anonymous Slow process
(remote) converge consensus
Concept Single/Multiple Visualize Clarity of Needs
Mapping knowledge structure facilitation
Blackboard Multiple Integrate diverse Collaborative Technically
expertise memory complex

Key Takeaway

The art of knowledge capture lies in choosing the right mix of techniques to fit the context,
experts, and goals.
A successful knowledge developer is not just a recorder of information but a strategic facilitator
who converts tacit expertise into structured, shareable, and actionable organizational knowledge.

🧭 Chapter 7 Knowledge Codification

1. In a Nutshell
 Knowledge Codification is the process of organizing and representing knowledge so that
it can be easily accessed, shared, and applied by others in an organization.
 It follows knowledge capture and precedes knowledge transfer in the KM (Knowledge
Management) system life cycle.
 The purpose is to get the right knowledge to the right people at the right time for
better decisions and efficiency.
Goals:
 Transform tacit (personal, experiential) knowledge into explicit (documented) form.
 Link KM initiatives to business goals and value creation.
 Focus on intellectual capital and usability.
2. What Is Knowledge Codification?
 Codification = converting captured knowledge into a systematic, usable, explicit form.
 It makes corporate knowledge visible, accessible, and usable for decision-making.
Two perspectives:
 KM view: Converting tacit → explicit knowledge.
 IS view: Converting undocumented → documented knowledge.
Core idea:
Codified knowledge is structured information that supports decisions, training, and performance.
Examples:
 Tacit knowledge → expert directories, knowledge-sharing sessions.
 Explicit knowledge → databases, manuals, intranet repositories.
3. Why Codify Knowledge?
Codified knowledge supports:
1. Diagnosis: Identifying causes from symptoms (e.g., medical systems).
2. Instruction/Training: Teaching newcomers using experts’ knowledge.
3. Interpretation: Comparing data to standards (e.g., sensor-based systems).
4. Planning/Scheduling: Designing sequences of actions (e.g., military operations).
5. Prediction: Anticipating outcomes (e.g., weather forecasting).
Benefits:
 Reduces dependence on experts.
 Enables faster learning.
 Improves consistency and decision quality.
4. Things to Remember (Challenges)
Before codifying knowledge, consider potential bottlenecks:
 Recorded knowledge may be fragmented or hard to access.
 Slow diffusion of new knowledge.
 Knowledge is often hoarded, not shared.
 People may not know who knows what.
 Knowledge may be:
o Not in the right form
 o Not available at the right time

o Not present in the right place

o Incomplete in content

Implication:
→ Knowledge developers must plan codification carefully to overcome these barriers.
5. Modes of Knowledge Conversion (Nonaka’s SECI Model)

From To Mode Description

Tacit Tacit Socialization Sharing through experience, observation, practice.
Tacit Explicit Externalizatio Explaining tacit knowledge using analogies or models.
n
Explicit Tacit Internalization Learning by doing — applying explicit knowledge.
Explicit Explicit Combination Integrating and organizing different explicit knowledge
sources.
These conversions continuously transform and expand organizational knowledge.
6. How to Codify Knowledge
Key Questions:
1. What goals will codified knowledge serve?
2. What knowledge currently exists?
3. How useful is existing knowledge for codification?
4. Which tools or media are best for representing it?
Steps:
 Identify relevant, not just complete, knowledge.
 Choose methods suitable for the knowledge type (tacit vs explicit, rule-based, etc.).
 Always align codification with strategic objectives.
7. Codifying Tacit Knowledge
Nature:
 Tacit knowledge is deep, experience-based, intuitive — hard to express or formalize.
 Often considered more art than science.
Challenges:
 Difficult to transfer all nuances of expert experience.
  Requires trust, collaboration, and skilled communication between developer and
expert.
Process:
 Work with a willing expert.
 Understand the expert’s style (procedural, storytelling, parental, or persuasive).
 Use the right approach accordingly.
 Aim for “good enough” representation — codified knowledge matures over time.
8. Codification Tools and Procedures
There are multiple tools for encoding facts and relationships:
(a) Knowledge Maps
 Purpose: Visual directory pointing to knowledge sources (people, documents,
repositories).
 Not a repository — a guide to where knowledge resides.
 Helps identify strengths and gaps.
How they work:
1. Visualize business problems or processes.
2. Encourage collaborative discussions.
3. Use facts to build shared understanding.
4. Ensure open, trusting communication.
5. Review and follow up post-session.
Building a Knowledge Map:
 Identify where knowledge resides.
 Ensure content is accurate, easy to navigate.
 Integrate into intranets or HR systems.
Types:
 Process maps
 Strategic maps
 Skills/Competency maps
Example:
 HR skills planner — links required skills to training and job advancement.
 Strategy-knowledge map — matches business strategy with existing knowledge to find
gaps.
(b) Decision Tables
 Represent knowledge as conditions vs. actions (like a spreadsheet).
 Each column = a rule.
Example:
If Customer = Bookstore and Order > 6 copies → Allow 25% discount.
Useful for verifying logic and defining consistent rules.
(c) Decision Trees
 Graphical, hierarchical representation of decisions.
 Easier to visualize relationships and verify logic.
 Used when limited actions result from complex conditions.
Difference from Decision Tables:
 Trees = visual + hierarchical.
 Tables = tabular + structured verification.
(d) Frames
 Knowledge structure with slots (attributes) and facets (values).
 Represent entities (e.g., employee, car, product).
 Support inheritance — child frames inherit properties from parent frames.
Example:
Frame for “Car” with slots like Manufacturer, Color, MPG, Owner.
(e) Production Rules
 Codify expert knowledge into IF–THEN statements.
Example:
IF income is average AND credit_history is good
THEN approve loan (Confidence = 0.8)
  Expresses heuristic or experiential knowledge.
 Easy to understand, but limited to fine-grained details.
 Requires validation to ensure reliability.
(f) Case-Based Reasoning (CBR)
 Solves new problems by recalling past similar cases.
 Works like human analogy-based thinking.
Examples:
 Doctors diagnosing patients using prior cases.
 Mechanics recalling past repair experiences.
Advantages:
 Saves time, less rule formulation.
 Useful when experts are unavailable.
Limitations:
 Needs large case libraries.
 May degrade with too many attributes or outdated cases.
(g) Knowledge-Based Agents
 Intelligent software programs that act autonomously.
 Learn from user behavior and assist in decision-making.
 Can filter, search, or recommend based on prior user actions.
9. The Knowledge Developer’s Skill Set
Knowledge Requirements:
1. Computer Technology: Hardware, software, system architecture.
2. Domain Knowledge: Understanding the business problem.
3. Repositories & Data Mining: Familiarity with KM tools.
4. Cognitive Psychology: Knowing how experts think and make decisions.
Skill Requirements:
 Strong interpersonal communication.
  Ability to articulate rationale and gain management support.
 Rapid prototyping and iterative development ability.
Personality Traits:
 Intelligence, creativity, patience, persistence.
 Logical and analytical reasoning.
 Humor, optimism, and tolerance for ambiguity.
Key Roles:
Change agent, planner, tester, communicator, motivator, and problem-solver.
10. Role of Planning in Codification
Planning ensures:
 System modularization.
 Logical linking of rules.
 Verification and validation.
 Effective user interface design.
 Continuous monitoring and revision.
Without planning, KM projects risk inefficiency and poor outcomes.
11. Inferencing and Reasoning
 Inferencing: Drawing conclusions from existing knowledge (the role of the inference
engine).
 Used in expert systems to apply rules and derive results.
 Critical for rule-based and case-based reasoning in KM.
12. Implications for Knowledge Management
 Codification is not just technical—it’s managerial and strategic.
 Requires planning, collaboration, and user participation.
 Success depends on user acceptance and integration into daily routines.
 The knowledge developer’s role is central to building organizational learning and
sustaining intellectual capital.
13. Summary (Key Takeaways)
 Codification bridges knowledge capture and knowledge transfer.
 It transforms human expertise into organizational assets.
 Tools include: Knowledge Maps, Decision Tables, Decision Trees, Frames, Rules,
CBR, and Agents.
 Codification requires strategy, structure, and skilled developers.
 Effective KM relies on balanced use of technology, people, and processes.
 Chapter 9: Knowledge Transfer and Knowledge Sharing
1. Overview
Knowledge Transfer (KT) and Knowledge Sharing (KS) are core processes in Knowledge
Management (KM).
Their goal: transform individual learning into organizational learning, turning knowledge into
action that improves performance, innovation, and profitability.
Knowledge must first be captured, codified, and deployed before it can be shared or reused.
2. Knowledge Transfer as a Step in the Process
Definition:
Knowledge transfer = transmission + absorption of knowledge between sources and recipients.
 Merely making knowledge available ≠ knowledge transfer.
 It involves using and applying the knowledge to create new value or behavior.
Purposes:
 Promote collaboration and networking
 Enable access to new insights and expertise
 Build an environment of excellence and continuous learning
Examples:
 Learning by doing
 Mentorship or apprenticeship
 Document exchange
 Asking colleagues for solutions (tacit exchange)
Herbert Simon’s Bounded Rationality:
People seek “good enough” information (satisficing) rather than the best possible solution —
often limited by convenience or access.
Three Factors in KT:
1. Source: Knowledge bases, experts, books, lessons learned, etc.
2. Medium: LAN, wireless transmission, encrypted channels.
3. Recipient: Individual, team, customer, or automated system.
Tacit knowledge limits full codification — it must often be shared person-to-person or through
direct experience.
3. The Knowing–Doing Gap
Many firms know what to do but don’t act accordingly.
Causes:
 Organizational culture that ignores learning.
 Leadership that undervalues front-line employees.
 Fear of change or failure.
Example:
In a seminar, a Miami bank refused to act on “employee-first” ideas despite understanding their
value, while another bank took immediate action — showing the difference between a
knowledge-hoarding and a learning organization.
Lesson:
Bridging the knowing-doing gap requires action-oriented culture and leadership support.
4. Prerequisites for Effective Knowledge Transfer
4.1 Instill Trust
 Trust is the foundation of KT and KS.
 People hoard knowledge if they fear exploitation or replacement.
 Organizations must ensure psychological safety for open exchange.
4.2 Fix the Culture
Culture influences how freely people share ideas.
Positive cultural traits:
 Leadership that promotes change.
 Clear mission and transparency.
 Cooperation, empowerment, and fairness.
Negative traits:
 Knowledge hoarding, “not my job” attitudes.
 Prioritizing money over people.
  Poor communication of company goals.
Example:
Firms with high layoffs or secrecy discourage sharing; “learning organizations” embed
cooperation into daily norms.
5. Key Guidelines for Knowledge Transfer
5.1 Push Reasoning Before Process
 Teach why before how.
 Example: Employees must understand why databases exist, not just how to use them.
5.2 Doing Is Better Than Talking
 Learning by doing (apprenticeship, projects, mentoring) transfers both explicit and tacit
knowledge.
 Example: A new car salesman with mechanic experience uses practical know-how to
build trust and improve sales.
5.3 Embrace Mistakes as Learning
 Trial and error fosters innovation.
 Example: IBM founder Watson’s $10 million “training mistake” story — mistakes are
investments in learning.
5.4 Encourage Cooperation over Competition
 Internal rivalry breeds hoarding.
 True progress comes from team-based cooperation toward shared goals.
5.5 Identify What Counts
 Focus on why things happen, not only outcomes.
 Prioritize actionable insights from reports, not just data.
5.6 Leadership’s Role
 Managers set the tone for learning and transfer.
 They must model and reward knowledge-sharing behaviors.
5.7 Job Satisfaction and Stability
 High satisfaction supports collaboration.
 Based on Maslow-style needs: recognition, security, responsibility, fairness, etc.
6. Transfer Methods
Process:
1. Capture experience from completed tasks.
2. Repackage as knowledge.
3. Reuse or distribute through repositories or teams.
Factors Influencing Method:
 Nature of the problem (routine vs nonroutine)
 Type of knowledge (explicit or tacit)
 Barriers (time, culture, communication)
7. Transfer Strategies
 Formalized approaches: documents, intranet, databases, meetings.
 Tacit absorption: achieved through job rotation, mentoring, and on-site training.
 Informal networks (e.g., “watercooler talks”) are powerful enablers of spontaneous
knowledge exchange.
Example:
Japanese firms create “talk rooms” and social gatherings to strengthen knowledge flow and trust.
8. Inhibitors of Knowledge Transfer
1. Lack of Trust: Without a shared language or mutual respect, people hesitate to share.
2. Lack of Time/Space: No dedicated spaces for discussion.
3. Status Barriers: Employees may ignore information from lower-ranked sources.
4. Quality and Speed Issues: Outdated or poorly communicated knowledge reduces
reliability.
9. How Knowledge Is Transferred
(1) Collective Sequential Transfer
 Knowledge moves within the same team performing tasks repeatedly.
 Example: A construction crew improving septic system installations job by job.
 Focus: team learning and process refinement.
Features:
  Frequent short meetings
 Equal participation, no hierarchy
 Confidentiality within team
 Focus on performance, not personality
(2) Explicit Inter team Transfer
 Sharing knowledge between different teams performing similar work.
 Example: One construction team discovers a method to protect tree roots; shares with
another team.
Challenges:
 Pride, time pressure, and reward systems may hinder open sharing.

(3) Tacit Knowledge Transfer

 Transfer of experience-based, intuitive knowledge.
 Example: Red Adair’s team transferring oil-well firefighting know-how in Kuwait.
Features:
 Requires contextual adaptation.
 Difficult to codify or document.
 Depends on direct interaction, observation, and trust.
10. Role of the Internet in Knowledge Transfer
Evolution:
 From mainframes to global, knowledge-sharing networks.
 Internet = medium + market for collaboration and learning.
Internet Service Providers (ISPs):
Provide access, hosting, and backbone connectivity.
Competition made access affordable and widespread.
Benefits:
 Speed: Instant knowledge exchange across time zones.
 Accessibility: Equal visibility for large and small businesses.
  Feedback loops: Real-time customer input via online surveys.
 Customer service: FAQs, chatbots, and automated replies streamline responses.
 Global collaboration: Managers and employees connect worldwide.
Examples:
 Dell sells $6M/day via website (knowledge-driven operations).
 Cisco uses web-based collaboration to drive innovation.
Limitations:
 Security & Privacy Risks: Cyberattacks, viruses, data theft.
 Quality Control: Online information may lack accuracy.
 Information Overload: Hard to filter valuable insights from noise.
11. Implications for Knowledge Management
1. Culture before technology: Trust and motivation precede infrastructure.
2. Technology as an enabler, not a driver: Internet and databases support—but don’t
replace—human connection.
3. Learning by doing: Continuous improvement and feedback loops sustain knowledge
flow.
4. Leadership accountability: Managers must lead by example and reward sharing.
5. Balanced incentives: Encourage contribution to knowledge systems (“give to get”
principle).
12. Summary
Knowledge transfer bridges the gap between knowing and doing.
It’s a cycle of capture → codify → transfer → apply → learn again.
The key enablers:
 Trust
 Supportive culture
 Leadership
 Technology
 Collaborative spirit
Without these, even the best KM systems fail to deliver organizational learning or competitive
advantage.