Information Advantage

Crushing the Data Governance Challenge

January 8, 2010 by Scott Busse and Bill Abbott

http://www.theinformationadvantage.com/wp-content/plugins/sociofluid/images/digg_32.png http://www.theinformationadvantage.com/wp-content/plugins/sociofluid/images/reddit_32.png http://www.theinformationadvantage.com/wp-content/plugins/sociofluid/images/stumbleupon_32.png http://www.theinformationadvantage.com/wp-content/plugins/sociofluid/images/delicious_32.png http://www.theinformationadvantage.com/wp-content/plugins/sociofluid/images/newsvine_32.png http://www.theinformationadvantage.com/wp-content/plugins/sociofluid/images/technorati_32.png http://www.theinformationadvantage.com/wp-content/plugins/sociofluid/images/google_32.png http://www.theinformationadvantage.com/wp-content/plugins/sociofluid/images/facebook_32.png http://www.theinformationadvantage.com/wp-content/plugins/sociofluid/images/twitter_32.png

Governance Committee

Data Governance often gets a bad rap and it’s easy to see why. The business looks at data governance as yet another layer of policies and procedures mandated by IT that make their job more difficult.  While it might be hard to clearly quantify the benefits of effective data governance, the consequences of poor data governance are more transparent.  Insufficient or non-existent data governance leads to serious technical and business problems such as overly complex and cumbersome information flows, lack of a single version of the truth, poor or misunderstood data quality, proliferation of tools and platforms, inconsistent data definitions and more.  We encountered one environment where our client had core revenue and cost information stored across four different systems (each with different, un-reconciled amounts), nine ETL tools, overlapping and redundant 3rd party data providers, seven different database management systems, and 14 analytical tools.  And these were just the ones we discovered!  These issues ultimately lead to excessive costs and misinformed decision making.

Getting a data governance initiative off the ground starts with clearly defining the scope and objectives of the data governance organization and getting buy-in from top executives.  Data governance can encompass  many things, ranging from data quality all the way to maintaining the integrity of the enterprise information architecture.  It entails aspects of project management, architecture, data stewardship and data management, making it essential that the data governance boundaries be clearly defined.  This ensures that all aspects of information management are covered and responsibilities are not overlapping with other functions or groups.  And with clearly defined objectives, the progress of the data governance initiative can be measured and communicated to stakeholders.

With a charter that clearly defines objectives and scope, it’s time to establish executive support.  Reframing data governance in the context of high priority opportunities is the key to getting the right executive support from business and IT.  A data governance directive can be framed as an opportunity to simplify the IT environment, reduce costs, and strengthen decision making or mitigate business related risks that stem from information gaps and inaccuracies.  Risks vary from making poor decisions due to inaccurate data to litigation over non-compliance.  In fact, this is more of a business opportunity than a technical opportunity, and we would suggest that the business own your data governance initiative.

Data Governance Overview

While there’s no silver bullet approach to implementing data governance, there are a few techniques that make these initiatives more likely to succeed:

  • A well defined charter that is linked to pressing and agreed upon business issues (or underlying technological issues that are hurting business performance)
  • Business ownership, or at a minimum, a high degree of business engagement
  • Clearly establishing metrics or milestones based on the charter and using a phased approach allows the project to show progress and gain momentum
  • Day to day leadership that drives pro-actively drives the governance agenda and takes accountability for the charter
  • Executive engagement as part of the governance structure, meeting at least once a quarter
  • Data stewards from the business and IT who are accountable for data quality and following governance procedures across all major data domains
  • Carrots and sticks in place to follow governance procedures (e.g. employees reviews should have a governance component)

No doubt about it, data governance is hard.  Following  practical  techniques will help ensure a successful data governance organization is established, and the costly pitfalls of non-governance are avoided.

{ 2 comments… read them below or add one }

Kevin Davis February 3, 2010 at 9:34 pm

Scott and Bill,
While I agree with all that you state, one additional item I have seen work is to make sure data governance is incorporated in the development lifecycle. For instance, in order to get data from one of the MDM domains, it has to be approved by the data governance council and specifically the business owner of the data in the domain in question. It is a good practice to have a single business unit own a domain, the data itself and what it does, means, etc. while IT owns the systems and processes to make sure the data is reliable and available. Quality is everyone’s job.
Just my two cents.
Thanks
Kevin

Bill Abbott February 4, 2010 at 11:39 am

Kevin: Thanks for the reply here. Your point is well taken and a useful addition to the discussion.

Leave a Comment

Previous post:

Next post: