Knowledge

Management Life
Cycle
Difference b/w Conventional System &
KM System
System Analyst
 data & Information from the user
 User highly dependant on the analyst for
solution

Knowledge developer
 Captures knowledge from people with known
knowledge in the firm
 Developer dependant on people for solution
Difference b/w Conventional
System & KM System
Interface of System Analyst
 User knows the problem & not the solution


Interface of Knowledge Developer
 Knowledgeable person who knows the problem
& solution

Difference b/w Conventional
System & KM System

Development is sequential

Design is incremental and interactive
Difference b/w Conventional
System & KM System
Testing at the End of the System

Testing (verification & Validation) from the
beginning of the Cycle
Difference b/w Conventional
System & KM System

Process Driven & documentation oriented

Process Result oriented- Start slow & grow
Difference b/w Conventional
System & KM System
Does not support rapid prototyping
Supports rapid prototyping – incorporate
changes on the spot refining the system

Structure the Problem

Reform the Problem Repeated Cycles

Rapid Prototyping Structure a Task

Repeated Cycles
Make Modifications

Build a Task
User v/s Knowledge Worker
 E va lu a tin g E xistin g In fra stru ctu re

Fo rm th e K M Te a m

K n o w le d g e C a p tu re

D e sig n K M B lu e p rin t

V e rify & V a lid a te th e K M S yste m

Im p le m e n t th e K M S yste m

M a n a g e th e C h a n g e & R e w a rd S tru ctu re

Po st S yste m E va lu a tio n

KM System Life Cycle

1.Evaluating Existing
Infrastructure

System Justification

Scope of Evaluation

Determine Feasibility
System Justification
 Knowledge lost due to knowledge worker
retirement, departure
 Need at several locations
 Are experts available and willing to help
 Does it require years of experience & cognitive
reasoning
 During knowledge capture does the expert know
how to solve the problem
 How critical is the knowledge captured
 Are the task non algorithmic
 Is there somebody who believes in the benefits of
a KM system

Scope Factor
Limiting the breadth and depth of the project
within the financial, HR and operational
constraints
Readiness of the companies current technology
Identify the gap areas between the current
technology and the requirement of the KM
system
Understanding of benefits and limitations
Feasibility
Is it doable - Can it be completed within a
reasonable time
Is it affordable – Does the system benefits
justify the cost
Is it appropriate – What is expected to get out
of it
Is it practical - How often will it be constructed
and at what cost
User Support
Are the users aware of the KM system in the
designing

What training is required for the user

What operation support is needed

2.Formation of the KM Team
Identify the key units, departments, divisions as
the stakeholders in the prospective KM System
Balance the team size and competency
organizationally, strategically & technically
 Caliber of team members in terms of
Personality
Communication skills
Experience
 Team size (4 to 20)
 Complexity of project
 Leadership & Team Motivation
 Promising more than can be delivered
3. Knowledge Capture
 Apply appropriate tools to capture Expert’s
Knowledge
 Explicit knowledge – documents, files other medias
 Tactic Knowledge – company experts, Data mining


 Collecting, analyzing & interpreting knowledge

used by experts in solving problems by the team
 Interviews with knowledge experts
 Interview the users

 Knowledge developer
 identify the problem domain
 Capture the knowledge
 Writes & tests the heuristics
 Coordinates the entire project from beginning to
the end

4.Design a KM Blueprint
 Inter operability & scalability with the existing IT
infrastructure
 Finalize the scope of proposed KM system with net
benefits in mind
 Required system components – user interface,
knowledge directories, mining tools
 Develop key layers
 User factor
 Authentication / password
 Collaborative agents & filters
 Application layer
 Transport internet layer
 Physical layer
 Storage devices holding the Information

5.Test the KM System
Verification
 Programs do what they are designed to do
 Right knowledge is available when needed in
the format needed
 Evaluate technical performance
Validation
 Meets user expectation
 User friendly
 Usable and scalable on demand
 Reliability of the KM System
6. Implement the KM System
Converting the KM System into actual
operation
Quality assurance
 Reasoning errors
Firm has never had a layoff so it will never have
a layoff
 Ambiguity
Sell the bad stocks
 False representation
User Training
 Manage Change & Reward
Structure

Experts – anxiety about sharing of information
User – Resent lack of recognition (helped in
building KM)
Troublemaker – obstruct installation, cause delay
Narrow minded Superstars
Post System Evaluation
Change in the accuracy and timeliness of
decision making
Constructive organizational change
Attitude of the end user
Change in the cost of operation
Change in relationship between the end users
Cost justification
