Data Governance is unfortunately not an exciting title and in no way conveys the benefits that an organisation can achieve by implementing Data Governance. In this article Nicola Askham, The Data Governance Coach, explores whether it is possible to call your Data Governance initiative by a more appealing name.
One of the many challenges you will have to face when implementing Data Governance is agreeing the scope of the initial phase of your initiative. By this I don’t just mean which data domains or business functions are going to be in scope. Inevitably you will be asked to include activities that are not Data Governance in your scope – but should you agree?
There is a lot of confusion about the roles of Data Owners and Data Custodians. How the roles are different and who should be fulfilling them. This article looks to clarify and answer those questions.
It is often expected that once you have a Data Governance or Data Quality Team in place that they will fix all your data quality issues. But are they really responsible for resolving them?
A look at who is responsible for investigating and resolving data quality issues.
Over time, unenforced regulations simply get ignored and become useless. It is likely that things won’t change until the regulators make them change, and they will have to go sooner or later through a harder enforcement line.