Leverage Your Data Modeling Tools and Team


If Data Governance is your program/project to manage, think of the Data Modeling Team and their tools as your foundation. A good Data Governance Program needs to be built atop a top-notch Data Model. Sure, you can have Data Governance without a good data model, it’ll just be a lot harder and a lot more time consuming. See this post on data governance failures for a recent study stating a high percentage of Data Governance programs fail – and my thoughts on that.


The scope of many Data Governance Programs is enterprise data, master data, or a particularly high-value line-of-business’ set of data. With a good Data Model, you’ll easily be able to go in and tag the domains that are in-scope for you as part of the Data Governance Program.

Additionally, you may want to have a comment field for discussions that took place around this data field (not part of the metadata description, but in a separate area) and you’ll definitely want to have a place where you can indicate where the field currently is on your data maturity model.

One thing that we didn’t do, which I now regret, is to have a ‘date last reviewed’ area for a data element. This would certainly help as I’d quickly know when this particular field last came before the council. Since I don’t have this, I have to rely on a combination of memory and a review of my meeting minutes, notes, and website to find that date.