Effective knowledge management<\/em> improves mean-time-to-repair (MTTR) metrics, increases customer satisfaction, and generally makes life on the\u00a0typical IT service desk a whole lot easier.<\/p>\n Why then is knowledge management one of the most neglected processes in IT Service Management (ITSM)? Even when organizations put some effort into knowledge management, information is stored in silos that function as separate repositories for different IT teams. Maintaining this separation greatly degrades the value of the knowledge that is recorded.<\/p>\n A key factor that contributes to successful and timely problem solving is having the right people in the room, with the expert knowledge that you need. If information is scattered around the organization with different people having exclusive access to individual parts of the puzzle, then knowing who the right people are, and bringing them together, is made much more difficult.<\/p>\n To improve problem-solving capabilities within an organization, it is worthwhile to improve knowledge management practices at the same time. A well-organized, central knowledge repository will greatly enhance your problem solving abilities.<\/p>\n It feels great to get to the bottom of a problem and get people back to work. But the last thing you want is to come up against the same problem in the future and have someone redo the investigation. Without good knowledge management, this is likely to happen. Recording and sharing the results of your problem solving is a start, but there is more to knowledge management than this.<\/p>\n To make sure you do not go down the same road and rework problems time and time again, there are a few rules to follow:<\/p>\n 1. Record a good description of each problem, using non-technical language. This will allow you to match future occurrences with the descriptions.<\/p>\n 2. Include keywords in your documentation to make future searching easier.<\/p>\n 3. Link this knowledge to the related incident and problem records.<\/p>\n 4. Store all knowledge in one, central, searchable repository.<\/p>\n 5. Update the knowledge record with relevant new information every time a similar issue is reported.<\/p>\n Effective knowledge management needs to be recognized as a critical component of any IT Service Management (ITSM) organization \u2013 it is much more than a \u201cnice to have\u201d. Knowledge management, when done well, has positive impacts on all other areas of your IT organization, particularly in the areas of problem management and incident management. Accurate knowledge reporting, as a part of your problem management process, will have a positive impact on MTTR metrics and ultimately, on customer satisfaction and business results.<\/p>\n When Kepner-Tregoe (KT) problem solving tools are integrated into their ITSM capabilities, organizations credit the information as \u201cessential\u201d for future problem solving. The KT tools use logical questioning and analysis steps and record the results in a clear and logical format that provide robust and usable data for knowledge management and ongoing problem solving activity.<\/p>\n","protected":false},"excerpt":{"rendered":" Knowledge silos have a negative impact on customer service Effective knowledge management improves mean-time-to-repair (MTTR) metrics, increases customer satisfaction, and generally makes life on the\u00a0typical IT service desk a whole lot easier. Why then is knowledge management one of the most neglected processes in IT Service Management (ITSM)? Even when organizations put some effort into […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"ppma_author":[113],"class_list":["post-24852","post","type-post","status-publish","format-standard","hentry","category-other"],"acf":[],"yoast_head":"\nMaking problem solving harder<\/h4>\n
Knowledge management, when done well, has positive impacts on all other areas of your IT organization, particularly in the areas of problem management and incident management.<\/span><\/h3>\n
Don\u2019t solve problems twice<\/h4>\n
A key capability<\/h4>\n
The Kepner-Tregoe difference<\/h4>\n