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

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 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 1. 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. ...

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

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...

Search