Data Governance Committees, Forums and Working Groups

Data Governance Committee Forum Working Group

At some point in your Data Governance initiative you are going to need to think about setting up a Data Governance Committee. So in this blog I wanted to look at what a Data Governance Committee is and what it should do.

Before I start to look at this in detail I want to remind you that you may not call yours a Committee and that is f fine.  As I mentioned in this blog the titles of roles can be emotive and we need to be pragmatic about their use.  The same is true for your Data Governance Committee. You may have a Data Governance Forum, Data Steering Group, or something similar.  Whatever you call it is not important, it’s who sits on it and what it does that is important.

What is Data Governance Committee?

A Data Governance Committee is simply the forum where you get all of your Data Owners together. Now of course, that is an oversimplification; but it’s a good starting place. I’ve worked with some excellent Data Owners over the years, but it would be naïve to think that they could’ve run the Committee on their own. They are going to need some expert advice and guidance to help them make the right decisions about your company’s data.

These “experts” will include the following types of roles: your Enterprise Data Architect, the Head of Internal Compliance, and the Head of Operational Risk. In more than one client, the CIO has been an attendee. Deciding who you will invite as your experts will, of course, depend on the remit of your Data Governance Committee, which we will look at a little bit later. Before I move off the topic of expert advisors, I want to consider culturally how you will sell the concept of attending these meetings to the experts.

After all, by the time you set up your Data Governance Committee, you should have spent a considerable amount of time and effort identifying and engaging your Data Owners. You have succeeded in getting the agreement of senior roles within your organisation to be accountable for the data quality of a number of data sets. Then you tell them that they can’t make decisions upon their data alone…

Depending on the culture of your company, this may not go down too well! In many organisations, this isn’t really an issue. However, with some of my past clients, to avoid any unnecessary tensions, the terms of the committee have made it clear that the Data Owners are the “members” of the committee, and are the only people who can make decisions. The “experts” are “attendees”; there to provide advice and guidance to help the Data Owners make their decisions. (Notice that I don’t say “the right decisions,” that phrase could also open up a myriad of tensions and issues!)

There are three more people who are key to the success of your Data Governance Committee:

Firstly, a strong chair person. I have seen it work successfully with this role undertaken by one of the Data Owners, but it is better if the Chair of the Committee is not a Data Owner themselves so that they can remain neutral if any heated debates ensue. Ideally this person will be the executive sponsor of your Data Governance initiative, that way they have a vested interest in making it work and they are in the right position to escalate issues to the Executive Committee if that is needed at any point.

Secondly, you should be there! I am of course assuming that you are the Data Governance Manager or the person leading the Data Governance implementation (whatever your title happens to be); if so, you need to be an attendee. You are key to reconciling the agenda with the Chair Person, and in the early days you will be presenting many proposals for activities you want to start or include in your Data Governance initiative to get approval from the Data Owners.

Finally, you are going to need some type of secretariat support for the Committee. Arranging the meetings, booking meeting rooms, circulating papers in advance, and taking minutes are all crucial to the smooth and successful running of this Committee. If your organisation is very small, then you may have to do this yourself, but you may have a fellow Data Governance Team member that can help you, or perhaps the Chair Person’s personal assistant could provide some support.

So, hopefully that has given you an idea of who to invite, but you can’t invite them without being able to explain to them what it is they will have to do.

What does a Data Governance Committee do?

As with all things Data Governance, what the committee is responsible for will depend very much on your organisation and the Data Governance Framework you have designed or are designing. It will also depend on when you set it up. At the very least, the committee will be responsible for the oversight of the Data Governance Framework and for monitoring material data quality issues. The committee could also be responsible for ensuring compliance with relevant data related regulation as well as steering other data projects such as master data management, or the implementation of a Data Warehouse.

Depending on when the Committee is set up, its role in the development and implementation of your Data Governance Framework may also be dictated. Over the years, I have seen such forums set up at various times: before the Data Governance initiative has really begun; as it starts; and once the Data Governance initiative has started. My preference would be for the latter, but let’s look at each in turn:

Data Governance Committee First

This usually happens when a senior stakeholder recognises the need “to do something” about their data, and invites like-minded peers to a forum to discuss and agree what it is they can do. Sometimes this can be a useful step in identifying the need for and starting a Data Governance Initiative. At other times they can be a talking shop where attendees share their issues and everyone agrees that it is a problem, but not what will be done to resolve them.

If this is what you are facing, view this as your self-identified stakeholders, and work with them to get the initiative started. They will then be instrumental in all stages of designing and implementing your Framework. At some stage, you will have to review the attendees as it will become obvious that not all of them are Data Owners and that some new Data Owners will need to be invited.

Data Governance Committee as Initiative Starts

In my opinion, this is still a little early; things move slowly at the start and it can be challenging to keep all the attendees engaged if you don’t have much progress to report. You also have the issue of how to identify the attendees if you haven’t designed the Framework and identified the Data Owners.

In this situation, the sponsor has identified key stakeholders and invited them. This can lead to engagement issues – if they really aren’t interested – plus, you will have the same need, detailed above, to review and change the membership a few months in.

Data Governance Committee on Data Governance Has Started

My preference is to set up the committee after you have designed an initial high-level Data Governance Framework once you have identified and agreed upon who the Data Owners are, or as a step to agree them. At this stage, you will be starting with a clear purpose and the correct attendees so that they can focus on overseeing the detailed design and implementation of the Data Governance Framework.

Whichever of the above situations you are facing, you must be clear from the start that the terms of reference for this Committee will evolve and transition from oversight of development and implementation, to the ongoing oversight and governance of your Data Governance Framework.

I do hope that this has clarified what a Data Governance Committee is and what it should do. But please don’t rest on your laurels once your committee has been set up. It requires a lot of effort to make and keep such forums successful. You can read my top tips for how to go about that here.

Setting up a Data Governance Committee is just one of many things you need to do when implementing Data Governance. You can find out more of the tasks (and the order in which they need to be done) by downloading my free Data Governance Checklist.


Free Checklist To Support Successful Data Governance

Increasing numbers of organisations are becoming data driven and digital transformation is high on the agenda for many of my clients. These really are exciting times from a data point of view. The landscape in which we work is changing rapidly with machine learning and AI increasingly influencing our daily lives. If you are reading this blog, then hopefully I have no need to convince you of the importance of data governance to support digital transformation, AI and machine learning.  Right now is not only a good time, but a necessary time to be embracing Data Governance.

 So perhaps you are among the many people I speak to who say that 2019 is the year you are going to get Data Governance in place in your organisation? Regardless of the endeavour, it is common for people to renew their efforts at the beginning of the year. Most people have had a break and are feeling refreshed and energised, ready to face the challenges that implementing data governance inevitably brings.

But I want to urge caution, whilst energy and enthusiasm are vital ingredients, on their own they will not ensure your data governance initiative is successful. I used to think that was the case, but be assured you also need a structured approach and a clear plan. 

When I was planning for 2019, I decided to make it my mission to help as many people as possible to be successful in data governance. So I decided that this year there was something more I could do to help you be more successful.

Over the 16 years I have been doing data governance, I have created and refined a methodology that ensures all the necessary building blocks are addressed and in the right order. This ensures that a data governance framework can be designed and implemented successfully, regardless of the industry and culture of an organisation. It is this methodology that is the basis of my training course.

 Being a "Data Governance geek" I like templates and lists, so as part of this methodology I have a checklist. This checklist details everything I need to do or consider, plus the order in which I need to do it and it is this checklist that I use when helping my clients design and implement data governance frameworks.  To be honest, I have followed it so many times over the years that I don't need to look at it very often these days! This got me thinking, it was a shame that something I have found so valuable is just sitting neglected.

 So I have decided to share this checklist with a wider audience.  A high level version is now freely available on my website and the full version of my checklist will be given to everyone who does either my online or face-to-face training (and indeed I will be sending a copy to everyone who has ever completed my training to date). 

I do hope that you find this resource as helpful as I have over the years.


Can Software Help My Data Governance Initiative?

This is a question that never came up very often the first few years I was a Data Governance Consultant but these I am being asked it much more frequently.  I think that the increase is due to the fact that there are good data governance tools available now and that data governance is getting much more focus than previously.

In the last couple of years, I have seen a move away from companies implementing data governance because they are in an industry where their regulator requires it, to organizations starting data governance purely because of the benefits they can achieve. That also includes companies looking to extend what they had put in place to meet regulatory requirements across more of their organization.

Before I answer the question, I think it is important to emphasize that despite having the word “data” in the title, data governance is more about people than data.  Most of the work you will do when designing and implementing a Data Governance Framework is around organisational and cultural change.  It is about the roles and responsibilities around data and the processes that these roles will follow.

It is for this reason that when Data Governance tools first started emerging I have to admit that I was skeptical about whether they could really help.  In fact, if you search the internet hard, you may even be able to find some comments I’ve made in the past along those lines!  After all, in the early stages of a Data Governance initiative I seldom find myself sitting at a desk using any type of software (data governance or otherwise); I am meeting and engaging stakeholders.

However, over recent years, having seen these tools evolve, I have revised my opinion and will happily say that yes, they can help you do data governance, but when I say yes it does come with a caveat.  In order to add value to your Data Governance initiative, they must be used in the correct manner and at the correct time.

Data Governance Tools Can Only Facilitate

The tools out there can be fantastic enablers and facilitators but they cannot do your job for you.  On more than one occasion I have heard of companies who have purchased such a tool and thought that that was it – job done.  However, it soon became clear that the tool “was not working.” Upon investigation, it became obvious that the tool was not the problem.  The business believed that it would do everything for them, which clearly it cannot.

If your whole data governance initiative centres around a tool, it is unlikely that your business user will ever engage, because they will be under the mistaken belief that the tool will do all the work for them.

You will still need to get stakeholders engaged in the process because without their buy-in, the whole initiative is likely to fail. The tool won’t work unless the whole business is signed up to data governance in the first place. Tools do not relieve them of any responsibility. Instead, tools should be positioned as enablers that make it much easier for people to execute their data governance responsibilities.

Remember: it’s not the tool that causes a data governance initiative to hit the rocks. The initiative fails when too much attention is focused on the tool, and too little attention is focused on getting stakeholder buy-in and change management.

Do Not Deploy Too Soon

Another reason I’ve seen problems arise around the use of tools is when they are deployed too early in the Data Governance initiative and the organisation is not mature enough to know how it wants to use the tool.  Without fully understanding what Data Governance is, the scope of their initiative, or the functionality of the tool, it is naive to rush into using one.  A company can expend significant time and resources on setting up a Data Governance tool only to find that they have set it up in manner that does not facilitate their Data Governance initiative or meet their requirements!

So What do Data Governance Tools do?

So let’s be clear on what such tools can do. Primarily, they provide data glossary functionality; they can automatically create data lineage diagrams and have workflows that send proposed changes in data definitions or data standards to the data owner for approval.  They can also be used for logging and monitoring the resolution of data quality issues. So they really can facilitate and help embed Data Governance into your organization.

How to Use Data Governance Tools Successfully

I hate to recommend it, but I firmly believe that as you start to create and build a data glossary, your early version should be created on an excel spreadsheet.  The reason I say that is that they are easy to adapt and change as your organization matures and your business users work out what they want and need from a tool.  When you are reasonably clear what is wanted and how it should be structured, that is the time to introduce a tool into the mix.

Remember, you are trying to change how people behave in your organisation. This is not something that can be achieved by only thinking in terms of technology solutions. It is going to involve a lot of soft skills: communications, influencing, and even hand-holding as they start to embrace Data Governance.  And let’s face it: computers and software are not known for their people skills.

Tools can be very powerful facilitators, especially in larger organisations where perhaps you do not know or even know how to find out who a data owner is or what data is available; but they only facilitate and support the hard work that you need to do in person.  There really is no way to avoid it… You are going to have to go and talk to people!

Thinking that software tools are the answer is just one of the top data governance mistakes that I’ve seen organizations make.  If you want to find out what the others are (and how to avoid them), you can download a free report here.


What is the Difference Between Policies and Standards?

This question is one that I have been asked a lot over the years, and has led to some interesting debates! But before I dive into my thoughts on the matter, I think that there is another question that needs to be asked (and answered first):

Why the confusion?

Why do these two terms cause so much confusion? After all, they are commonly used business terms. It’s not as though they are specialist data management jargon. The Oxford English Dictionary defines these two terms as follows:

Policy: A course or principle of action adopted or proposed by an organization or individual (Wikipedia elaborates this further saying that: A policy is a deliberate system of principles to guide decisions and achieve rational outcomes. A policy is a statement of intent, and is implemented as a procedure or protocol.)

Standard: A required or agreed level of quality or attainment

The way I use these terms in the context of data governance pretty much follows the above standard definitions. However, confusion arises as many people use the term policies when I would use standards, so whereas I would say that in data governance terms an organisation will have one Data Policy and many Data Quality Standards, I know that a lot of practitioners say that an organisation will have many data quality policies. So to clarify, the definitions I use are:

Data Policy: a formal document that describes an organization’s approach to managing data quality i.e. what will be done

Data Quality Standard: The standard that a certain field or data set needs to achieve e.g. that a field must always be completed or the value sit within a defined range.


So which should you use? Well I believe that it is fine to use them how you wish (and whichever fits best with your organisation’s culture) as long as you define what you mean and communicate that definition with your audience. As with most things, confusion only arises when no explanation of what is meant is provided and those on the receiving end of your messages are left to make their own (varied) interpretations.

Not defining terms is a common mistake or omission that many organisations make, but although it causes frustration and confusion, it is not the biggest problem you will face and it is easily rectified.


Do We Have to Call Them Data Owners?


I spend a lot of time helping people become successful Data Governance practitioners, so it is not surprising that I get asked lots of questions about Data Governance. A very common one is about naming the Data Governance roles..  Many people worry about whether it is necessary to use standard or best practice role titles when implementing Data Governance.  By this I mean titles such as Data Owner or Data Steward.

Before I dive into my thoughts on this issue, I’d like to remind you of a quote from Juliet in William Shakespeare’s Romeo and Juliet:

“What’s in a name? That which we call a rose. By any other name would smell as sweet.”

You don’t have to have studied Romeo and Juliet or even seen the play to know the saying “a rose by any other name…” As with many Shakespearean quotes, this one gets used in our everyday lives, and this particular quote resonates with me whenever I get asked the question about role titles. I often find myself involved in such discussions when I start working with new clients.

If you are implementing a Data Governance Framework and have done any “Google” research, you probably have come across a numbers of role titles that you may want to include: Data Owners, Data Stewards, Data Custodians, Data Champions, Information Owners, Data Librarians, Data Producers, Data Consumers, and a host of others, I’m sure.

Personally, I favour a fairly straight-forward set up with Data Owners, Data Stewards, Data Consumers, and Data Producers as the primary roles. However, throughout the numerous Data Governance initiatives that I’ve been involved in, I’ve learned not to be precious about it.

Through my own personal experience and from watching others, I know how emotive job or role titles can be.  You don’t have to be egotistical to desire the “right” label; it’s human nature to desire recognition for the work we do.

Of course, when we are implementing Data Governance, we are not recruiting and appointing new staff into new roles.  We are identifying the correct existing people to take on some data governance responsibilities.  Remember, however, that even additional responsibilities which do not ostensibly change a job title need to have a descriptive name that fits with company culture. You might be the Finance Director, but you can also say that you are the Data Owner for Finance data.  It is then easy for other people to understand your additional responsibilities.

Role titles are neat things. They enable you to deliver a message about what you are responsible for, succinctly and quickly, so it is no wonder that people like and use them. But what happens if you have the wrong titles? Well, that depends on the culture of the organization, and the individuals concerned. At best, it could lead to confusion and make implementing and embedding your data governance framework more challenging.  At worst, I’ve seen it delay the implementation of the data governance initiative as people waste time in endless debates over what the roles should be called.

What I’ve learned through experience is quite simple: the name is important to a degree (don’t insist on one set of titles if they really aren’t going to work in your organization), but it is critical to define what that role is responsible for and what you need the role holders to be doing in order to make your data governance initiative a success.

My advice is to start with the list of things you need done and work out how best to group those responsibilities together in a way that fits your organizational structure. Try some of the “usual suspects” out and test their reactions. If they like Data Steward – go with it; if they don’t, try something else. It doesn’t matter if they aren’t called a Data Steward as long as they act like one.

As with all things Data Governance, pragmatism is vital: so in my view, “that which we call a Data Steward by any other name could work just as well…”

1 Comment

Data Governance Interview - Alex Leigh


Alex has worked with over fifty UK universities, most of the sector agencies including University and Colleges Admissions Service (UCAS), Higher Education Statistics Agency (HESA) and the Quality Assurance Agency for Higher Education (QAA) and a host of practitioners in the Higher Education (HE) sector. Alex designed and developed the HEDIIP data capability framework, led the team to create the HESA in-year collection model and designed both a sector level and a HESA instance of a best practice data governance approach; and is currently working with universities to develop and implement their Data Governance frameworks,

How long have you been working in Data Governance?

I was working in DG before anyone really called it DG! Around fifteen years via data architecture and running data management teams.

Some people view Data Governance as an unusual career choice, would you mind sharing how you got into this area of work?

My route in was via developing and implementing Enterprise Architecture frameworks while I was working in Deloitte UK consulting practice. There was a lot of maturity around the business, infrastructure and application architecture but data felt very fragmented between the technology of building warehouses and databases and the link to the business objectives.

So I focused my efforts on creating frameworks and approaches to pragmatically align how data was managed to how it was used. That was fifteen years ago and I’m still trying to change the perception around data.

What characteristics do you have that make you successful at Data Governance and why?

Passion for the right outcomes, resilience when I can’t achieve them and an ethos for openness, transparency and showing everyone why doing things differently isn’t just about the organisation, it’s about helping them.

Are there any particular books or resources that you would recommend as useful support for those starting out in Data Governance?

I’m a big fan of John Ladely and use his books as my primary source of reference. Bob Seiner has some great ideas about implementing DG and I’m an avid reader of TDAN. I also carry around the latest DMBOK which is a big improvement on the original in terms of applicability.

There’s so much good stuff online now. I’d encourage any new practitioners to read and research lots of different ideas, as no one size fits all.

What is the biggest challenge you have ever faced in a Data Governance implementation?

Believing everyone was as passionate, sold and committed as I was to doing things differently. So losing support once the initial enthusiasm had lapsed. Both from those working with data every day and those who had the budget, resource and will to help change the way data was governed.  Now I am very careful to make sure everyone is starting in the same place, and make far less assumptions around priorities.

Is there a company or industry you would particularly like to help implement Data Governance for and why?

I love working in Higher Education (HE). It’s collaborative, desperately in need of the professionalization of its data assets, and – finally – ready to make some of these changes. I’ve worked in 7 industry sectors, but I’ll never move out of HE. If I can help make a difference to this sector, it feels a really important thing to do. Having kids about to enter the HE environment makes this personal as well as important.

What single piece of advice would you give someone just starting out in Data Governance?

Don’t try to fix everything at once. At the heart of good DG is changing behaviours of many people. This is not a simple thing. Talking about frameworks or technology and the like early in a DG initiative is not helpful. Find some people who share your passion for data, look for quick wins where doing things differently makes a measurable change and communicate way more than you think you need to.

Finally, I wondered if you could share a memorable data governance experience (either humorous or challenging)?

I once asked an attendee at a workshop why she looked so glum. Her reply was "This is how I feel about data. I work in planning and I know at the top of the ‘data mountain’ it is sunny and lovely and all the data is perfect.  The data gets to me in this dark valley at the bottom of the mountain via a stream that all the sheep has wee’d in. That’s why I look so sad"

It was an amusing anecdote but made me realise that you really have to show people how things can be better, before actually asking them to do something about it. 


Data Governance Interview - Dr. Irina Steenbeek


Irina is a dedicated Senior Data Management, Financial and IT Professional with 15+ years of extensive experience in data management, software implementation, financial and business control, and project management. During the past year, she has also immersed herself in data science. She sees that big data and data science have a huge potential for business development. These areas are crucial for the development of data management, including data governance.

How long have you been working in Data Governance?

It has been over 7 years now, since I first started working in data management. During this time, I have also engaged a lot in Data Governance, mostly through hands-on experience in SMEs and large international organizations.

Some people view Data Governance as an unusual career choice, would you mind sharing how you got into this area of work?

For me, this career path started quite organically as a result of several challenges in related areas. The first challenge was to create an automated solution for management accounting reporting within an organization. During the development of an organization-wide reporting system, I came across various issues, such as massive numbers of non-reconcilable Excel reports and the presence of three separate reporting platforms. This lead to the implementation of a data warehouse in this company. This implementation also highlighted data quality issues. This was not all, but it started a long journey towards the management of the data.

What characteristics do you have that make you successful at Data Governance and why?

I think that well-developed communication skills always come in handy. Establishing a common business language between your colleagues and partners, as well as clear communication with the stakeholders helps a lot if you want to set up a good data management structure. A data management function connects various departments of a company, and it is great if you can get practical support of top management, or work in an environment and culture that can enable you to execute your function in the most effective way possible.

A while ago I have written a blog on this topic: ‘Am I a successful Data Manager’ Feel free to consult it for more tips that I have to share.

Are there any particular books or resources that you would recommend as useful support for those starting out in Data Governance?

Recently I came across The Practitioner’s Guide to Data Quality Improvement by David Loshin, published by Morgan Kaufmann in 2010. I think this book is quite useful for DQ professionals.

But in general, from my practical experience of working closely with business stakeholders, I have reached one conclusion: people are not interested to know what they need to do. They are eager to know how to do what is expected from them.

At an early stage of my professional development I used DAMA DM-BOK as my main reference point. And of course, I have done a fair share of internet browsing and analyzed the materials I could find, originating from numerous sources. So far, I haven’t been able to find any practical guide that could help starting data management professionals.

This experience brought me to an idea to write my own ‘The Data Management Cookbook’, a brief summary book on Data Management, which is here. The extended ‘Do It Yourself’ Data Management guide will be available in June 2018.

What is the biggest challenge you have ever faced in a Data Governance implementation?

There were several, it is difficult to say which one was the biggest or most important. The first one is finding your own way to implementation of data management, and figuring out where to start. The second one is convincing data owners that they have to take on responsibility for their data. And the third one is more technical: the investigation of data quality issues caused by applications.

Is there a company or industry you would particularly like to help implement Data Governance for and why?

In my career, I have worked in all kinds of companies, large and small. All in all, I think I prefer small and medium businesses to large and famous multinationals.  Why? I know it doesn’t sound very ambitious. Smaller companies feel more like a ‘family’. And I appreciate this a lot, as this feeling creates a great work environment. You know everyone and you can get things done quickly and efficiently. It is easier to involve your colleagues in all the processes, which is crucial for successful data management. Even if the resources are limited, you can still deliver tangible results in a short period of time.

What single piece of advice would you give someone just starting out in Data Governance?

You do not set up data management just for fun. You do it because you have certain

needs, a certain goal will drive you to do it. GDPR or data quality are the best examples.  My advice is to first get a clear picture what your goal, your driver is. As soon as you know the direction you should be working in, it will be easier to figure out which components will need most of your attention and in which order you should proceed.

Finally, I wondered if you could share a memorable data governance experience (either humorous or challenging)?

When implementing data management, you have to ensure collaboration between various stakeholders. These are people with different interests, needs and tempers, and you are the one who has to combine them all into one effective working system. One of the most memorable moments in my career was a question of one of such stakeholders: ‘Where do you get so much patience to permanently stay calm, have good relationships with all of us and still keep going?’. I guess only a data manager would know. :-)


Data Governance Interview - Matt Becker


 Currently, Matt serves as the Managing Director of Sullexis’ Enterprise Data Strategy and Solutions practice. He has spent 18+ years creating and implementing strategies that drive client performance through technology adaptation in areas ranging from big data to enterprise data management to business intelligence and analytics.  He enjoys delivering the value gained by implementing solid information management principles, thereby reducing inefficiencies and gaining insight into overall operational performance.

How long have you been working in Data Governance?

I spent the early part of my career helping to design and implement various data warehouses and analytics for the Energy Trading & Risk Management industry.  Because of the regulations involved in ETRM projects, starting around 2005, I started incorporating data management procedures and reporting requirements to identify, verify, and track the adherence to the data regulations associated with those DW initiatives.   In fact, every data project that I now oversee, has had some sort of DG set of deliverables.

Some people view Data Governance as an unusual career choice, would you mind sharing how you got into this area of work?

It was a combination of by accident and necessity.  Because of the reporting and visualization work I was doing on various BI / Data Warehouse implementations for the Energy industry early in my career, I started seeing a pattern emerge.  The data quality after the go-live of the data warehouse was usually very high but quickly degraded.  Many times, this was a result of the tools being used and the people involved not following a standard approach or adhering to an agreed set of guidelines to maintain the availability, usability, integrity and security of the data.

So, I typically became the person that would build that data quality discipline into the project, usually in the form of a roles and an accountability matrix.  This matrix would define the data requirements and standards needed for ongoing support and maintenance.  Over time this evolved into working with a number of clients on specific DG initiatives helping to provide a framework and a playbook for the overall management of data to drive quality, consistency, and usable insights.  

What characteristics do you have that make you successful at Data Governance and why?

Good blend of having been a business analyst, developer, tester, architect, and project manager. Having done all of these roles throughout my career has given me valuable exposure to all aspects of a solution lifecycle (planning, design, architecture, code development, testing, implementation, and deployment).  Understanding of this framework for a typical project enables you to apply a similar framework and approach for Data Governance methodology (i.e. planning of roles needed, design of the roles and processes to be used, active communication and coordination across both IT and Business functions).

In addition, deep domain knowledge is an added plus in helping to shape the data governance priorities between the IT systems and the business operations.  For example, I have spent quite a few years in the Upstream Energy sector, where Well Data mastering is a significant challenge.  Too many times, companies focus on just throwing technology at the problem to try to solve their data availability and reliability issues.   However, the issue was that the data in system A did not match to system B because the data wasn’t properly defined (i.e. a Well Legal Name vs. Well Short Name, or Spud Date vs. Drill Date) resulting in more expense and time than what was really needed.  In these situations, the company in question has not prioritized their efforts to first develop a common Well language, using DG standards, to ensure a foundational understanding of the data.  Too often, when this step is done first, portions of the existing technology and solutions available in-house can typically be repurposed, saving on the overall expense and allocating those funds to more prescriptive technological solutions needed.

In fact, at Sullexis, we have a section of blogs on our website ( that talk about combining the right data practices with technology to improve such things as data migrations and on-going data quality through practical DG practices.  One of our most recent blogs focuses on creating a common data language to ensure there is a mutual understanding of core concepts central to the company’s operations.

Are there any particular books or resources that you would recommend as useful support for those starting out in Data Governance?

  • DAMA’s DMBOK v2 – A fundamental guide to data governance
  • Manager ( – you have to understand how to manage teams, individuals, projects, and processes in order to be effective in implementing data governance.
  • - your website has a lot of great articles and blogs that serve as a very good aggregator of data governance knowledge from a broad and varied set of sources.
  • Practical Data Migration (Johnny Morris) – great book for working data migration efforts, which is many times how Data Governance gets introduced into an organization.
  • Visualization and Reporting Tools:  Tableau, Spotfire, Business Objects, MS Power BI – understanding how reporting and analytic tools function, are implemented, and how end users utilize them to properly is important to know how to combine their use with DG methodology.

What is the biggest challenge you have ever faced in a Data Governance implementation?

The big challenge is the same one I face at almost every client I work with where Data Governance is a new concept…understanding.  There are many companies that don’t realize that one of their most valuable and key assets is their data.  If you think of data as a garden, one needs to take the time to remove the weeds (bad data), clean out the clutter and debris (duplication), till and care for the soil (managing your technology stack), and properly feed and water (define and execute your roles and procedures).  These on-going activities (data governance process) result in the garden yielding a good crop (high quality, reliable data).   I like to take the time to engage and educate the right levels in the organization to solidify their DG understanding and ultimately gain their support.

Is there a company or industry you would particularly like to help implement Data Governance for and why?

Oil and Gas/Upstream Energy – first this is where I have spent quite a bit of my career, but secondly, many of the newer technologies (Big Data, Cloud, IoT, etc.) are just now being implemented, and there is an explosion of data and the need to better govern its use.  Executives are realizing the need to treat data as an asset and with that you must have the right governance and coordination between people, process, and technology to keep your employees safe, your solutions effective, and your operations competitive.

What single piece of advice would you give someone just starting out in Data Governance?

One of the best bits of advice that I received from my very first project manager about a year after I graduated college was "I want you to be the 'Go-To team member'."

Be the one who is willing to do the task nobody else will. Dig in to the details of the data processes and the business users that use them on a daily basis.   

Be the one who may not know the answer but will go do the work to find out.  Get into the weeds of the data issues or challenge so that you understand the root cause.  This will help you identify the data governance approach to employ to accounts for those issues.

Be the one that others will look to for a good attitude, a positive outlook, and assurance the job will get done and get it done well.  You will be amazed how well people will respond to you if you are positive to them…and many times when dealing with data issues, you need to stay positive!

Finally, I wondered if you could share a memorable data governance experience (either humorous or challenging)?

I was at a recent data visualizations conference and many of the sessions were focused on technology improvements like better leveraging IoT technologies in daily operations, no-SQL solutions for data aggregation and consolidation, and new visual modeling techniques using R-based tools.  But the most heavily attended session was about a company’s data governance journey and how they changed their culture and their methodologies to focus on data as the cornerstone of their operations.  The questions that I heard after that session warmed my heart.  So many times, it takes a large undertaking just to get people to understand why data governance is so important, but now the conversations were focused on the how and not the why or the what.  Everyone wanted to know how they could go about implementing data governance in their organization.  I think that is representative of a movement in global corporate community…this increased focus on data.  I think this is just the beginning of a data governance revolution!