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

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

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