Knowledge management system life cycle
- 1. Akash C.Mathapati Assistant Professor Kirloskar Institute of Advanced Management Studies (KIAMS) Knowledge Management System Life Cycle Akash C.Mathapati
- 2. Evaluating Existing Infrastructure Form the KM Team Knowledge Capture Design KM Blueprint Test the KM System Implement the KM System Manage Change & Reward Structure Post-System Evaluation Knowledge Management System Life Cycle Process Akash C.Mathapati
- 3. Design the KM Blueprint Beginning of designing the IT infrastructure & the knowledge management architecture KM team relies on such a blueprint to proceed with the actual design & deployment of KM system KM blueprint referred to as the KM system design, addresses several important issues Akash C.Mathapati
- 4. Test the KM system Testing involves two steps: Verification procedure Validation procedure The role of Quality Assurance Reasoning Error Ambiguity Incompleteness False Representation Akash C.Mathapati
- 5. Implement the KM system Major part of the execution phase is training company employees on the new KM system Users range from novice to experts Users are classified as tutor, pupil or customer Tutor user acquires a working knowledge of an existing knowledge base in order to keep the system current Pupil & customer fall within the actual use of the KM system Akash C.Mathapati
- 6. Manage Change & Reward Structure The resistors include the following: Experts Regular employees Troublemakers Narrow-minded “superstars” Akash C.Mathapati
- 7. Post System Evaluation Several Key Questions are asked in the post implementation stage: How has the KM system changed the correctness & appropriateness of decision making? Has the new system effected organizational change? How productive have those changes been ? How has the new KM sys affected the attitude of the end users? In what way? Was it worth it? How has the new system changed the cost of conducting the business? How significant is the saving or otherwise of it? In what way has the new system affected relationship between end users in the organization ? Akash C.Mathapati