I often get asked about the difference between Data Owners and Data Custodians.
If you've read my other blogs, you'll know that I'm not fixated on sticking rigidly to the standard role names, but for the purposes of this blog, I’ll to stick with what I consider “best practice” role names and consider both roles in turn:
A Data Owner is a senior business stakeholder who is accountable for the quality of one or more data sets. They are usually a senior business person who has the resources, budget and authority to be able to make changes to that data if necessary.
Data Custodians are very much an IT role. They are responsible for maintaining data on the IT infrastructure in accordance with business requirements. I think the confusion between the roles and who should be making decisions about data is rooted in a long term lack of Data Governance.
Before a company has Data Governance in place, it's common that the business has not been trained in articulating their data requirements and therefore it is often down to IT to interpret or make decisions in order to help the business. However, once you have a Data Governance framework in place, the business usually gets much better at articulating data requirements and IT’s job gets easier.
Another difference between the roles is that for Data Owners, I'm looking for named individuals who own one or more data sets. When it comes to Data Custodians. However, I use that more loosely as a collective term for all of the IT department who are supporting your infrastructure. That said, it's not impossible to have named custodians. I've worked with a number of clients where they have named their Data Custodians. These have usually been smaller organisations, where there is only one subject matter expert for each system and that person has been named as the Data Custodian.
Another frequent question is whether IT is ever a Data Owner? Now this is an interesting questions as generally, I would say, no. They might own meta data, or performance data around the systems, but nothing more than that. However, recently, I have come across circumstances where IT might own some data.
One such example is maybe your Data Security or Information Security Team who may be monitoring telephone calls or internet activity. This often isn't being done for any direct business purpose, but rather to protect the business as a whole. If this data isn't being collected to meet the requirements of a business Data Owner, then it could easily be argued that IT own that data.
I also often get asked if only IT can be Data Custodians? Generally, it is the case that Data Custodians sit within IT, but there are instances where business teams or functions may also act as Data Custodians. For instance, you may have a BI or Analytics Team sitting in the business reporting line, who perhaps manage and support your data warehouse. Because of the work they do it is quite common for such a team to be considered as the Data Owners for all data that's in the data warehouse. However, this is not a correct approach, because all that data has a Data Owner when it sits in the source system and that person still owns it even when it's on a data warehouse. Of course, in a data warehouse a lot of data is aggregated, combined and often new data is derived or calculated. It is common for the BI or Analytics Team to be involved in these activities, but it does not mean that they own the new or aggregated data. It is more appropriate to consider them as Data Custodians for the data, whilst it's being managed, manipulated and reported on by that team. After all they should be carrying out these activities to meet business requirements and the person who approved those requirements is the Data Owner.
I hope that this has clarified the difference between Data Owners and Data Custodians. Roles and responsibilities are only one of many things that you have to address as part of implementing Data Governance. If you are struggling to get your head around everything else you should be doing and the order in which to do it, please download my free checklist to help you plan your initiative.