As you know, Russia supplies Gas to many European countries.
Could you imagine Italy purchasing gas from Russia without checking what exactly was flowing through the pipe? I’m no expert on gas pipelines, but I know that before completing the agreement to purchase the gas, Italy and Russia would have agreed metrics such as:
- Volume of Gas
- Calorific value (Energy content)
So what? What else would one expect? Applied common sense… yes?
Why is it that such common sense is often lacking in Data Migration and Data Population projects? Why do some Enterprises continue to perform data population of, and ongoing data entry to, critical data repositories without fully understanding the data they are pumping into the repository?
A simple example involves Date of Birth. The business ask the IT function to populate Date of Birth in the new AML / BASEL II / CRM / other repository. Some time later, when data population is complete, the business begin to express concerns:
- “We never realised we had so many customers aged over 100 ???”
- “I thought we had more Student customers”
- “How come so many of our customers share the same birthday ?”
- “These are not the results we expected”
Performing data population on the basis of what the source data “should contain”, without analysing what exactly it does contain is known as ‘Load and Explode’ approach to Data Population. I cover this Enterprise Wide Data Issue in more detail here.
We in the “Data Governance”, “Data Quality” industry need to educate the business community on the “common sense” parts of data governance, and the need to engage “Data Governance Professionals” to ensure that “Data Quality Common Sense” is actually applied.
Feedback welcome – Ken