MODULE1:

KNOWLEDGE
MANAGEMENT

KBL Srivastava
 Knowledge Management

• Introducing the concept of KM

• Why KM?
• KM system life cycle,
• Aligning KM and business strategy
What is Knowledge?

• Data – collection of unprocessed facts, a set of

discrete facts about events
• Information – organized or meaningful data
• Knowledge – information that is contextual,
relevant, and actionable
• Strong experiential and reflective elements
• Good leverage and increasing returns
• Dynamic
• Evolves over time with experience
• Knowledge is also known as Human Capital
• The primary difference between the terms
information and knowledge is in the level of
understanding of their underlying organizational
data
From Facts to Wisdom (Haeckel & Nolan)

Volume Value
Less is
Completeness More Structure
Objectivity Wisdom Subjectivity

Knowledge

Intelligence

Information
Facts
Information, Knowledge and Wisdom
 Types of Knowledge
• Shallow (readily recalled) and deep
(acquired through years of experience)
• Explicit (codified) and tacit (embedded in the
mind)
• Procedural (psychomotor skills) versus
episodical (chunked by episodes;
autobiographical)
• Chunking knowledge
• Shallow Procedural Knowledge
• Knowledge FROM PROCEDURAL TO EPISODIC KNOWLEDGE
• Knowledge of how to do a task that is essentially motor in
• nature; the same knowledge is used over and over again.
• _______________________________________________
• Declarative Knowledge
• Surface-type information that is available in short-term
• memory and easily verbalized; useful in early stages
• of knowledge capture but less so in later stages.
• _______________________________________________
• Semantic Knowledge
• Hierarchically organized knowledge of concepts, facts,
• and relationships among facts.
• _______________________________________________
• Episodic Knowledge
• Knowledge that is organized by temporal spatial means,
• not by concepts or relations; experiential information that
• is chunked by episodes. This knowledge is highly compiled
• Deep and autobiographical and is not easy to extract or capture.
• Knowledge
Source: Awad, E.M (2007). Knowledge Management
 0-8

Two major types of Knowledge

 Explicit knowledge
 Deals with objective, rational, and technical knowledge
 Examples: policies, goals, strategies, papers, reports
 Structured knowledge that is easy to codify
 Easily manipulated, shared, taught or learned

 Tacit knowledge
 Unstructured knowledge – in the domain of subjective,
cognitive, and experiential learning
 Highly personal, hard to formalize and document
 Cumulative store of the experiences, mental maps,
insights, expertise, know-how, trade secrets, skills set,
understanding, etc.
 Involves a lot of human interpretation
A few Foundation Principles and
Building Concepts
• Knowledge Influences Success
• Knowledge Resides in the Heads of People
• Two Types of Knowledge
• Codified (explicit)
• Personalized (tacit)
• Knowledge Sharing Requires a Conduit to Happen Systemically
• Technology is the conduit
• Knowledge Sharing Requires Trust
• KM embraces both the Knowledge Based organization and the
Learning Organization
• KM has planned architectural frameworks
Reservoirs of Knowledge

Knowledge Reservoirs

People Artifacts Organizational

Entities

Individuals Organizational Units

Practices Technologies Repositories Organizations

Inter-organizational
Groups
Networks

Source: Becerra-Fernandez, et al. (2004). Knowledge Management

 Knowledge Assets
Codified Knowledge Assets (Legally Owned)
Patents
Copyrights Tip of the
Trademarks
Documents
iceberg

• Working Solutions
• Web of Relationships
• Communities of Practice
• Experience
• Expertise and Theoretical Knowledge
• Database

Source: The Knowledge Evolution

Illustrations of the Different Types of Knowledge

Source: Becerra-Fernandez, et al. (2004). Knowledge Management

Conversion processes
(Source: The knowledge creating company, I. Nonaka and H. Takeuchi)

Tacit Socialization Externalization

From

Explicit Internalization Combination

Tacit Explicit
To
 Four Modes of Knowledge Conversion

• Socialization:
• A process of sharing experiences
• Apprenticeship through observation, imitation, and practice
• Externalization:
• A process of articulating tacit knowledge into explicit concepts
• A quintessential knowledge-creation process involving the creation of metaphors,
concepts, analogies, hypothesis, or models
• Created through dialogue or collective reflection
• Internalization:
• A process of embodying explicit knowledge into tacit knowledge
• Learning by doing
• Shared mental models or technical know-how
• Documents help individual internalize what they experience
• Combination:
• A process of systemizing concepts into a knowledge system
• Reconfiguration of existing information and knowledge
The knowledge creation process

15
Source: The knowledge creating company, I. Nonaka and H. Takeuchi
Knowledge Requires Capture, Organization, Access
and Leverage
 OLD WAY  NEW WAY
 Capture form is written,  Capture from is digits in
auditory or graphical cyberspace
representations
 Organization via software
 Organization is via tables of programs designed upon
content, indexes, engineering principles,
classification systems used mathematical equations,
by publishers, libraries, etc word associations in
 Access when physical body cyberspace 24/7/365
goes to where the  Access wherever the
knowledge is located…a physical bodies link via
library, a company, a computers
research laboratory, a
school  Tacit knowledge tapped
using many different
 Tacit knowledge rarely technological tools
tapped
 Leverage is exponential,
 Leverage is a sum game multiples upon multiples
Knowledge Work Activities

Ac q u i r e
An a l yz e
O r g a n i ze
C o d i fy
Co m m u n i
c aUttei l i z e
Re sult
KM in Practice
• Knowledge Teams - multi-disciplinary, cross-
functional
• Knowledge (Data)bases - experts, best practice
• Knowledge Centres - hubs of knowledge
• Learning Organization - personal/team/org
development
• Communities of Practice - peers in execution of
work
• Technology Infrastructure - Intranets, Domino, doc
mgt
• Corporate Initiatives - CKOs, IAM, IC accounting
 Seven Levers of KM
• Customer Knowledge - the most vital knowledge
• Knowledge in Products - ‘smarts’ add value
• Knowledge in People - but people ‘walk’
• Knowledge in Processes - know-how when needed
• Organizational Memory - do we know what we know?
• Knowledge in Relationships - richness and depth
• Knowledge Assets - intellectual capital
Some Cases
• Create/discover - 3M, Glaxo Wellcome
• Codify - BHA, Standard Life, PwC
• Diffuse - H-P, Thos. Miller, Rover, BP
• Use - Buckman, Steelcase, PwC, Andersen etc.
• Process/culture - Cigna, Analog
• Conversion - Monsanto
• Measure/exploit - Skandia, Dow Chemicals
Knowledge to Knowledge Management
• Process of capturing and making use of a firm’s
collective expertise anywhere in the business
• Doing the right thing, NOT doing things right
• Viewing company processes as knowledge
processes
• Knowledge creation, dissemination, upgrade, and
application toward organizational survival
• Part science, part art, part luck
Defining KM
• Knowledge management (KM) is managing the
organization’s knowledge (both explicit and tacit) through
the process of creating, structuring, disseminating and
applying knowledge to enhance organizational
performance and create value
• KM requires a major transformation in organizational
culture to create a desire to share
• Structuring enables problem-solving, dynamic learning,
strategic planning, decision-making
• Leverage value of intellectual capital through reuse
Roots of Knowledge Managment
Business
Transformation
Learning (BPR, TQM, culture)
Organization Innovation

Knowledge
Management

Intellectual Information
Assets/Capital Management
Knowledge-based
Systems
Need for Knowledge Management
• Knowledge has become the key resource, for a
nation’s military strength as well as for its economic
strength.
• It is fundamentally different from the traditional key
resources of the economist – land, labor, and even
capital
• The performance capacity, if not the survival, of any
organization in the knowledge society will come
increasingly to depend on those two factors
(Drucker,1994).
 Forces Driving Knowledge Management
• Increasing Domain Complexity: Intricacy of internal
and external processes, the rapid advancement of
technology.
• Accelerating Market Volatility: The pace of change, or
volatility, within each market domain has increased
rapidly in the past decade.
• Intensified Speed of Responsiveness: The time
required to take action based upon subtle changes
within and across domains is decreasing.
• Diminishing Individual Experience: High employee
turnover rates have resulted in individuals with decision-
making authority having less tenure within their
organizations than ever before.
Benefits of KM
• People don’t have to spend as much time looking for
answers
• People can move quickly on their problem-solving
anywhere and anytime
• People can work more effectively and more efficiently
• Share best practices
• Competitive advantage
• Expertise can be leveraged
• Better decision-making
• Reduced costs, therefore increased profits
• Retain key talent and expertise
• Improve customer retention and/or satisfaction
THE KNOWLEDGE ORGANIZATION
Indicators of knowledge: thinking actively and ahead, not passively and
behind Using technology to facilitate knowledge sharing and innovation

Culture
Competition
Collect
Create
Organize
Techno- Intelligence
logy Maintain Knowledge
Organization

Refine
Disseminate
Knowledge
Management
Leadership
Process
KM Drivers
The middle layer
addresses the KM A knowledge organization derives knowledge
life cycle from customer, product, and financial
knowledge. Also from financial practices
Source: Awad, E.M (2007). Knowledge Management
THE KM CYCLE AND THE
ORGANIZATION
Knowledge management cycle
• Creates knowledge through
new ways of doing things
• Identifies and captures new
knowledge
• Places knowledge into context
so it is usable
• Stores knowledge in
repository
• Reviews for accuracy and
relevance
• Makes knowledge available at
all times to anyone
WHAT KM IS NOT ABOUT
• Reengineering
• Discipline or philosophic calling
• Intellectual capital, per se
• Based on information or about data
• Information value chain or knowledge capture
• Limited to gathering information from the
company’s domain experts or retiring employees
and creating databases accessible by intranets
• Digital networks
 1-30

WHY KNOWLEDGE MANAGEMENT?

• Sharing knowledge, a company creates

exponential benefits from the knowledge as people
learn from it
• Building better sensitivity to “brain drain”
• Reacting instantly to new business opportunities
• Ensuring successful partnering and core
competencies with suppliers, vendors, customers,
and other constituents
• Shortens the learning curve
 1-31

KM System Justification
• Is current knowledge going to be lost?
• Is proposed system needed in several
locations?
• Are experts available/willing?
• Can experts articulate how problem will be
solved?
• Is there a champion in the house?
 Critical Success Factors
• Strong link to business imperative
• Compelling vision and architecture
• Knowledge leadership
• Knowledge creating and sharing culture
• Continuous Learning
• Well developed ICT infrastructure
• Systematic knowledge processes
Soft Infrastructure

• A culture of sharing - vs. information fiefdoms

• Directors of Knowledge (Intellectual Capital)
• Facilitating knowledge processes
• change teams, development workshops etc.
• Developing personal skills
• info management, ‘dialogue’, online techniques
• New measures of human capital, capabilities
KM System Development
Life Cycle
• Evaluate existing infrastructure
• Form the KM team
• Knowledge capture
• Design KM blueprint (master plan)
• Test the KM system
• Implement the KM system
• Manage change and reward structure
• Post-system evaluation
Evaluate Existing Infrastructure
System justification:
• Will current knowledge be lost through retirement,
transfer, or departure to other firms?
• Is the proposed KM system needed in several locations?
• Are experts available and willing to help in building a KM
system?
• Does the problem in question require years of experience
and cognitive reasoning to solve?
• When undergoing knowledge capture, can the expert
articulate how problem will be solved?
• How critical is the knowledge to be captured?
• Are the tasks non algorithmic?
• Is there a champion in the house?
The Scope Factor
• Consider breadth and depth of the project
within financial, human resource, and
operational constraints
• Project must be completed quickly enough
for users to foresee its benefits
• Check to see how current technology will
match technical requirements of the
proposed KM system
The Feasibility Question
A feasibility study addresses several questions:
• Is the project doable?
• Is it affordable?
• Is it appropriate?
• Is it practicable?
Areas of feasibility:
• Economic feasibility determines to what extent a new
system is cost-effective
• Technical feasibility is determined by evaluating hardware
and supportive software within company’s IT infrastructure
• Behavioral feasibility includes training management and
employees in the use of the KM system
The Feasibility Question (cont’d
Traditional approach to conducting a feasibility study:
• Form a KM team
• Prepare a master plan
• Evaluate cost/performance of proposed KM
• Quantify system criteria and costs
• Gain user support throughout the process
Role of Strategic Planning in KM System
Development
Risky to plunge with a new KM system without strategizing.
Consider the following:
• Vision — Foresee what the business is trying to achieve,
how it will be done, and how the new system will achieve
goals
• Resources — Check on the affordability of the business to
invest in a new KM system
• Culture — Is the company’s political and social
environment amenable to adopting a new KM system?
KM Team Formation
• Identify the key stakeholders in the prospective
KM system.
• Team success depends on:
• Caliber of team members
• Team size
• Complexity of the project
• Leadership and team motivation
• Promising more than can be realistically
delivered
KNOWLEDGE CAPTURE
• Explicit knowledge captured in repositories from
various media
• Tacit knowledge captured from company experts
using various tools and methodologies
• Knowledge developers capture knowledge from
experts in order to build the knowledge base
• Knowledge capture and transfer often carried out
through teams, not just individuals
Role of the Knowledge Developer
• The architect of the system
• Job requires excellent communication skills,
knowledge capture tools, conceptual thinking,
and a personality that motivates people
• Close contacts with the champion
• Rapport with top management for ongoing
support
Design of the KM Blueprint
The KM system design (blueprint) addresses several
issues:
• System interoperability and scalability with existing
company IT infrastructure
• Finalize scope of proposed KM system with realized net
benefits
• Decide on required system components
• Develop the key layers of the KM architecture to meet
company requirements. Key layers are:
• User interface
• Authentication/security layer
• Collaborative agents and filtering
• Application layer
• Transport Internet layer
• Physical layer
Testing the KM System
• Verification procedure: ensures that the system is right
• Validation procedure: ensures that the system is the right
system
• Validation of KM systems is not foolproof
Implementing the KM System
• Converting a new KM system into actual operation
• This phase includes conversion of data or files
• This phase also includes user training
• Quality assurance is paramount, which includes checking
for:
• Reasoning errors
• Ambiguity
• Incompleteness
• False representation (false positive and false negative)
Resisters of Change
• Experts
• Regular employees (users)
• Troublemakers
• Narrow-minded superstars
• Resistance via projection, avoidance, or
aggression
 Knowledge Management Strategies
and
Aligning KM Strategy with the Business
Knowledge Management Approaches
• Personalization strategy focuses on connecting
knowledge workers through networks and depends on
tacit knowledge and expertise
• It provides creative, rigorous and highly customized
customer services and products.
• Codification Strategy focuses on technology that enables
storage, indexing retrieval and reuse.
• It provides high quality fast, reliable and cost effective
service.
Knowledge Management Strategies
Knowledge maps to link knowledge to strategy
Systematically mapping, categorizing, benchmarking and
applying knowledge with the help of a KM system can not
make only such knowledge more accessible, but also
focusses and prioritizes KM.

Source: A Tiwana (2002). The Knowledge Management Toolkit

Creating a knowledge map to evaluate
corporate knowledge

Source: A Tiwana (2002). The Knowledge Management Toolkit

Aligning Business Strategy With KM Strategy

Source: A Tiwana (2002). The Knowledge Management Toolkit

Process of linking knowledge with business Strategy
(Tiwana,1999)

Source: A Tiwana (2002). The Knowledge Management Toolkit

Process of linking knowledge with business Strategy (Tiwana,
2002)

Source: A Tiwana (2002). The Knowledge Management Toolkit

Glaxo Wellcome
 A strategy led initiative - learning org. focus
 Workshops to convert rhetoric to action plans
 Using Intranets to share R&D, help approvals
 Library, document management support
 Reoreinted Technical Architecture
 Challenge is creating ‘sharing culture’
Bottom Line - better RoIC
 Glaxo Wellcome - Knowledge Net
Learning History
Process Improvements Team Skills
- Quality etc.

Knowledge New science

Communications Network competencies
Architecture

People Marketing products

- manager skills - customer dialogue
- ‘Yellow pages’ Strategy
- expertise
 Ernst & Young’s Framework for KM
Storage
• Input, Purge
• Archive, Abstract Deploy
• Index, Catalog • On-demand
Acquire • Coordinate
• Engagement • Repeatable
• Content • Event-based
based
• Non • Subscription
engagement • Commercialize
Add Value • Monitor usage
based
• Identify needs • Measure
• External
• Research satisfaction
• Develop
proprietary
• Package

Provide Infrastructure
Organization - Culture - Technology - Public Relations

Source: Ernst & Young, and “A Note on Knowledge Management,” Harvard Business School
9-398-031, 1997
Organizational Impacts of Knowledge Management