This content is part of the Essential Guide: GDPR, AI intensify privacy and data protection compliance demands
News Stay informed about the latest enterprise technology news and product updates.

Building a business glossary enhances data governance

Experts say data professionals are responsible for establishing a common vocabulary across the organization to help ensure data governance success and GDPR compliance.

BOSTON -- It's time for data professionals to start establishing a business glossary at their organizations.

That's according to panelists at the Enterprise Data World 2019 conference, who argued that -- while it's not easy -- establishing a common data vocabulary across the organization is one of data professionals' highest priorities and is key to successful data governance.

A business glossary is a metadata repository with clear and consistent definitions about important business and IT information such as contacts, tools, processes and who is considered a customer, supplier, business partner and employee, panelists said.

Not having a business glossary complicates communication and results in misunderstanding, rework and large unnecessary costs, said panelist Laura Sebastian-Coleman, data quality lead at health insurance company Aetna.

"If our own employees were unable to successfully communicate with each other about the organization's data, we would not be able to manage our data well," Sebastian-Coleman said. "And if we can't manage our data well, how can we manage our business since all of our business depends on data?"

Perhaps more important, failing to establish common vocabulary puts an organization's data at risk for breaches -- and at risk of violating the EU's General Data Protection Regulation.

"GDPR demands that organizations know what category of personal data they process, where [it's from] and what its purpose is," said panelist Katherine O'Keefe, chief ethicist and lead data governance and protection consultant at Castlebridge. "Organizations need to have appropriate controls to detect and respond to a breach. A common vocabulary makes it clear what data was exposed, whom to call and how best to contact them."

A session at Enterprise Data World addressed the importance of establishing a business glossary and common vocabulary to data governance.
The session at Enterprise Data World began with a mock trial, the defendant being a data architect who failed to establish a business glossary. From left to right: Len Silverston, Thomas Redman, Laura Sebastian-Coleman, Katherine O'Keefe and Danette McGilvray.

Getting started on common data vocabulary

The first thing for data architects and other data professionals charged with creating their organization's business glossary to remember is that it's not a one-person job, according to the panelists. It requires organizational commitment from the top down and help from data stewards.

O'Keefe outlined the process of creating a business glossary into three key steps: definition, consensus building and communication.

  1. The definition process is defining an element or process and capturing its attributes and its relationship with other elements or processes. It requires a "vocabulary lead" and one or two subject matter experts -- preferably one from the business side and one from IT side.
  2. Consensus building involves circulating the definition with people in the organization, identifying synonyms and homonyms and recording those translations.
  3. Communication is publishing and promoting the definitions, as well as curating them on an ongoing basis.

O'Keefe estimated that each organization could need to define up to 2,500 terms to provide the starting foundation of a business glossary, but urged data professionals to start small. Even having just a few key common vocabulary terms, such as definitions for customer and various types of contact information, would make a significant difference in efficiency and GDPR compliance.

Three steps to creating a business glossary

Writing skills needed

Since clarity and accessibility are basic to a business glossary, Sebastian-Coleman said it's critical to have people with good writing skills on the project.

If our own employees were unable to successfully communicate with each other about the organization's data, we would not be able to manage our data well. And if we can't manage our data well, how can we manage our business since all of our business depends on data?
Laura Sebastian-ColemanData quality lead, Aetna

"Not everybody's a writer," Sebastian-Coleman said. "Very smart people are often not very good writers on their own subjects, because they know [the subjects] too well. So it seems obvious to me that if you want something written, you would hire people that have talent in writing to help facilitate that process."

Jan Bednarczuk, a data governance specialist at Nationwide attending the conference, has been charged with building the business glossary at her company for the last several years. She said she knows firsthand the importance of enlisting people with good writing skills.

"There are a lot of people in the insurance and financial services industry who would rather stab themselves with a fork than write anything," Bednarczuk said after the session. "Those people cannot be in charge of writing definitions. Even if they're the greatest subject matter expert, they will try to get it off their desk as fast as possible and it will not have the detail that it needs to have. You've got to find the person who got A's in English."

Meanwhile, panelist Thomas Redman, president of Data Quality Solutions, a consulting firm, offered closing advice: "Don't start from a blank piece of paper. There are so many different resources that allow you to get a jumpstart on the definition." Those resources could include something as simple as the dictionary or a financial, law or sales handbook.

The conference was March 17 to 22 at the Sheraton Boston Hotel.

Dig Deeper on Data governance strategy

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

How far along are you in building your organization's business glossary?
Common terminology is extremely important! I’ve maintained for years that a company or project glossary was essential for success