Can I fast track the creation of the Data Glossary by using standard definitions?

In this video I look at whether using standard definitions is a good way to create your Data Glossary quicker.

[@enwezornzegwu2494]

Very useful perspective. We're just set-up a Data Glossary Core Team at my organisation as a subset of the Data Stewards group. The Core Team is focussing on definitions that have cross-organisation relevance while accepting data steward submissions as a starting point for the glossary. Useful to hear that there are no shortcuts!

[@TheDataGovernanceCoach]

It sounds like you have a good approach - I hope it goes well!

[@mormekull]

Great example, Nicola, thanks. It seems to me that this organisation missed a trick - not only did they end up with a dodgy glossary, but they wasted the early enthusiasm of their new hire who had experience in the same industry. If they'd proceeded differently, they could have involved this person as a pair of fresh eyes and to stress-test their developing glossary against comparable organisations. That might have unlocked some useful learning!

[@TheDataGovernanceCoach]

Very true Chris!

[@rmuller]

In general i agree. But it does need some nuance. Many data elements are standardized in various industries in the context of supply chain integration. Those data elements have very well defined semantics, agreed by the industry peers. So in these cases you can fast track.

[@TheDataGovernanceCoach]

That is a good point Ronald - there are circumstances where standardised elements can help fast track completing a Data Glossary - but I would always encourage my clients to check that they really are using the terms as per the standard.