Skip to main content

Enterprise Glossary

As a Professor, I realized long ago how important words can be. Not just the words themselves but also the definitions and contexts in which those words should be properly used. When we think about the vocabulary of ITSM (and it is quite an extensive technical vocabulary) we must remember that it is vital that we are all using the terminology in the same way. To help us get on the same page for the language of ITSM, one thing an organization can do is to create an enterprise glossary. Such a collection of terms helps people to use terminology and vocabulary correctly and in its proper context. Common usage of terminology also leads to consistency of thinking and action.


A glossary is defined as:
A list of words relating to a specific topic with the definitions of the words provided.
An enterprise glossary is therefore a collection of words used throughout and across an organization or enterprise to help establish consistent definitions wherever the vocabulary might be used. A single documented source of vocabulary helps to build cultural norms and a common vision for an organization.


So how do we establish such a collection of words for specific topics with established definitions? We begin with the words themselves. Every word or term has a three part definition:
TERM: this is the word or term itself, with consistent spelling
DEFINITION: this is the most basic, dictionary derived explanation of the term
CONTEXT: this is the usage of the word or topic to which the term applies
Let’s look at an ITSM example:
TERM: Incident
DEFINITION: a single distinct event (Princeton University Wordnetweb)
CONTEXT: Incident Management—describing a single distinct event in which the delivery of service is currently or may be disrupted or impacted
This example shows that we cannot simply use the word “Incident” in a loose or haphazard way. We must determine the context or situation in which the definition applies. We can then find “real examples” that fit the definition and context. Not everything that happens in IT is an Incident, only those that disrupt or may disrupt service delivery. The various contexts or topics in which words or terms have been, are or could be used are the real heart of the enterprise glossary.


So we gather together all of the words relating to the implementation or use of ITSM within an organization or maybe even a broader context of IT. Once we collect the words in a documented form, we get agreement on the terms, definitions and contexts for each word from a variety of stakeholders and decision makers.

Finally we publish the enterprise glossary in a convenient, accessible location (perhaps the company intranet). Then we ensure that people know about the glossary through awareness and communications efforts. We also verify that people begin using the terminology according to the agreed-upon glossary entries. If people misuse the terms, we must gently but firmly correct them and explain to them the proper context and use of the terms. Point them to the enterprise glossary and explain to people the importance of common terminology.


An enterprise glossary can be a powerful tool to bring consistency, standardization, predictability and structure to you ITSM effort. So do not wait—work on that enterprise glossary today!

Comments

Popular posts from this blog

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...