6 Easy Steps to Win at Data Governance
-
About this course
6 Easy Steps to Win at Data Governance e-Book -
Who this course is designed to help
-
The basics of data in your organisationWhat is data and why care for it?7 Topics
-
Why data mattersWhat "data-driven" means and how to use it to excite stakeholders6 Topics|1 Quiz
-
Why your organisation struggles to become data-driven
-
What does bad data look like, and how do you find it?How to identify bad data and identify its risks and costs3 Topics|2 Quizzes
-
How to fix bad data with good governanceDefining what good data means
-
The importance of business process data touch points
-
What is governance anyway?
-
Where governance and data collide
-
Kicking off your data governance initiativeData Governance explained - 6 easy steps to win at data governance6 Topics|1 Quiz
-
What are the basic features of a Data Governance Framework?8 Topics|1 Quiz
-
Common Data Governance Misconceptions
-
Why are you kicking data governance off in your firm?
-
Data Governance vs Data Management
-
Choosing a Data Governance Framework - Cognopia vs DAMA vs DCAM
-
Establishing Data Governance is a lot like trying to win the World Cup
-
Data Governance vs Data Quality
-
What common errors should you avoid when setting up a Data Governance Framework?
-
Data Governance is NOT a project
-
Common Data Governance Misconceptions
-
Five critical data governance deliverables
-
How to Implement Data Governance in your firmLet's start Governing Data - the Cognopia Methodology14 Topics
-
Establish the Scope of Data Governance
-
Evaluate your environment
-
Choosing your Operating Model
-
Translate Data Governance Principles into Practice
-
Building the Data Governance Team - an overview
-
The Data Owner
-
The Business Data Steward
-
The Technical Data Steward
-
The Data Custodian
-
Organising the Data Governance Roles
-
Define your Data Governance Forums
-
Communicating the change
-
Understand end user's data struggles to create better communications
-
Sustain and Improve
-
Establish the Scope of Data Governance
-
Data Governance case studies - winning with data governance9 ways data leaders are winning with Data Governance1 Quiz
Participants 216
Reference data introduction
Why do we need reference data?
Reference data helps classify and categorise information. It is a type of Master Data, and it typically changes very slowly (if at all). Examples include:
- Iso codes
- Country codes
- Product codes
Reference data doesn’t change very often hence it’s important we get it right.
To that end, one of the main things you can do with reference data is force standardisation by having people choose from a predetermined list of values. You could think of this for something like a country code or a country telephone code. Imagine people having to type their own country code in a free form textbox. Some people might put 00 in front while others might put + instead, or simply leave it blank. Let’s use Singapore as an example.
(Singapore) 97503525
(0065) 97503525
(+65) 97503525
( ) 97503525
If we can provide a dropdown of reference data for people to select their country and it automatically populates the country code for them.

This standardised information can then be used by other business processes and other teams across the organisation. For example, it’ll make sure we’re not calling up our customers using an incorrect country code.
A healthcare use case
If we are prescribing drugs to patients, we have to be very careful. The wrong dosage might make someone sick. The wrong product might kill someone. And we must know what we have prescribed and to whom so we can re-stock our supplies and invoice patients for the products they’ve received.
Take Ibuprofen as a simple example. Many people take this to fight pain and inflammation. Some people take the brand name “Advil” others take a generic “Ibuprofen”. Both are the same medicine, and both will have the same benefit to our patients. If we can standardise the reference data so the uninitiated know that they can prescribe either Advil or a generic Ibuprofen safely and with the same effects, it allows us to stock multiple brands whilst still being able to search for “ibuprofen” and be returned a list of all types of this medicine that we can use.


If we actually standardise – have reference data for each different drug and each different quantity of drug that is administered, it becomes easier for the organisation to know exactly what was prescribed and delivered to whom. As a result, they’ll know how much to bill for each of these products.
Whereas if we use different terminologies, there is the chance misunderstanding might occur. For example, I’m looking at Advil being dispensed versus ibuprofen, and I’m unable to match that up as easily as I would be if we had a common identifier, some reference data that allows us to know that both of these products are indeed the same thing.
Stop struggling, start succeeding
learn the 6 easy steps to Data Governance Success
Quickly learn how to succeed with 3-5 minute long video lessons packed with practical advice you can use in your job today
Checkout now!