Knowledge Management

Knowledge Management - the "what"

George Santayana, the Spanish American philosopher, wrote the famous saying, “Those who cannot remember the past are condemned to repeat it.”

This really is the underlying basis for the process of knowledge management. It plays a key role in CSI but data must be captured in each of the service lifecycle stages. This Data capture must then be processed into Information, synthesize the information into Knowledge and applied to the context of the environment we are supporting to create Wisdom. This is known as the Data-to-information-to-Knowledge-to-Wisdom structure. DIKW. Wisdom (not repeating the past) will allow us to make more informed & better decisions around improvements in our processes, functions and services. The purpose of knowledge management process is to quantify all of this D-I-K-W and then to share perspectives, ideas, experiences and information at the right time in the right place with the right people to enable informed decisions efficiently by not having to rediscover this valuable knowledge.

Let's review the four elements of DIKW:

Data: Is a set of discrete facts about the CIs that we have within our environments. This data is captured in highly structured databases such as “Service asset and Configuration management systems. These advanced systems allow us to create relationships between these CIs and the discrete facts are captured as attributes of these CIs. This allows us to identify the relevant data and accurately capture it. We can then analyze and synthesize this data into information.

Information: We create information by putting the data into some context as it relates to our environment. This information is typically stored in things like emails, records, documents and multimedia. We do this so that it can be easy to capture, query, find, re-use and learn from. I like to think of the information as somewhat static. It’s the state of a CI at a particular moment in time. We can then trend these different moments in time to garner knowledge about the lifecycle of a CI or group of CIs.

Knowledge: Knowledge is gained from the analysis of information. This is then combined with peoples own experiences, insights and expertise to create new knowledge. Knowledge is dynamic and context based.

Wisdom: Wisdom is the ability to make use of our combined knowledge to create value through correct and well informed decisions. (Back to that not repeating the past thing).

In our next blog, we will explore "why" Knowledge Management is critical to successful service management.

Comments

Bordeaux said…

The DIKW construct would make sense if, as with most things IT, we first removed all the humans.

December 13, 2011 at 4:21 PM

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

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group . As a service provider, we can’t stop there! We must know what the contracts of our service offering are and be able to put them into context as required by the customer. Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include: Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods. Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you. You the consumer own these and they are yours to take with you. Note: Goods may not always be provided for every Service Offe

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 the

Search