Skip to main content

Managing Knowledge

I recently had the opportunity to chat with a practitioner about the importance of knowledge management and had to smile when she declared that ‘knowledge management is back.’ The premise of the comment was that early attempts at knowledge management were unsuccessful as organizations seemed to think that the knowledge was going to ‘magically’ appear. Gartner speaks to the fact that organizations also often focused on collecting knowledge, rather than dispersing it.

It has taken the IT industry a while to understand that there needs to be a strategy for knowledge management that culminates in the right information being delivered to the right place or person at the right time. Doing that successfully requires a process, methods, policies, procedures, tools, and metrics.

Another consideration is the shifting of generations in the workforce. Think about it. How do young – or young at heart – people solve problems today? They Google or Tweet and draw upon the knowledge and expertise of others. And those ‘others’ are perfectly willing to share. The ‘social generation’ is not afraid to share their knowledge and expertise the way that generations have been in the past. Organizations just need to ensure they have the processes and technologies in place to capture that knowledge and publish it in the best and most usable form. To that point, a whopping 42 percent of organizations are planning to update or add knowledge management technology in the coming year according to HDI’s 2012 Support Center Practices and Salary Report. According to the same study, knowledge management is now one of the most widely adopted ITIL® processes, behind only incident and change management.

 There’s often a perception that ITIL only focuses on knowledge management in Service Transition. This conversation really brought home to me the importance of emphasizing the fact that knowledge management spans the service lifecycle.

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th

The ITIL Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem