Skip to main content

Data Governance - Critical Success Factors

I recently read Marino's paper (2004) which addressed the critical success factors for data governance by addressing the the 10 corporate oversights, I summarize & explain some of the important points that I found useful:

  • Accountability & Strategic Accountability: The executive leadership has a clear mandate to drive data governance process.  This means roles and responsibilities for various people in the organization that are involved in the data governance process be accurately defined. 
  • Standards: Data standards needs to be established. Corporate Data is a valuable asset that needs caring & defining which means it made for a purpose and that purpose determines and drives value.
  • Embracing Complexity: Data stakeholders are the producers and consumers of data hence the data stakeholder management is a complex process as data itself. Processes need to be implemented taht collects, churns and distributes this data to the right stakeholders.
  • Choosing Strategic points of control: Controls need to be put in place to determine where and when the quality of data is to be assessed and addressed. 
  • Compliance monitoring: Data management policies and procedures need to be assessed periodically in order to ensure that the policies and procedures are being followed.
  • Metrics: Definition of outcome specific data quality metrics is important for measuring data governance success.
  • Cross Divisional Issue: The data governance structure must be designed so that it includes participation from all levels of the organization to reconcile priorities, expedite conflict resolution, and encourage the support of data quality
  • Senior Management follows suit: Leadership should not be excluded and should follow the rules of engagement laid out by the data governance model/framework or DG team
  • Training & Awareness: Data stakeholders need to be aware of the value of data governance. The importance of data quality, its benefits, values need to be communicated regularly. 
I added the last two in the list because from the political and perception standpoint these points are considered lightly and eventually become primary reasons for the failure of implementation of Data Governance in organizations. From personal experience I have seen small as well as big organizations becoming comfortable on the last two points during the implementation of a data governance framework.

Thoughts @ night,

Sam Kurien

Marinos, G 2004. We're Not Doing What? The Top 10 Corporate Oversights in Data Governance, DM Review, September, viewed 12 August 2010

Comments

Popular posts from this blog

IT as a Innovation Partner in Business

Usually in Business organizations and especially in organizations where R&D is a separate department itself a tension persists on keeping the IT department away from any decision when it comes to innovation or process improvement. In short the IT department is generally seen as less of a help and more of a hindrance to innovation efforts. One of the main reasons is traditionally information systems are designed to impose structure on process, achieve pre-defined goals, produce metrics and minimize need for human interaction (in some case over maximize human interaction leading to nothing but "meetings").

While Innovation activities are highly unstructured and emergent, IT cannot be ignored or kept in isolation because IT can help in visualization tools, data mining efforts, uncover hidden relationships between data and create tools of knowledge management/information repository that so desperately is needed cross functionally but especially by the innovators within a org…

Analysis of SAP’s Platform Strategy

The software industry has been through high and lows up with the constant advent of new technological innovations and rapid changes in the global economic landscapes. SAP is the leading enterprise application software giant started by Hasso Plattner. The rise of Enterprise application industries started in early eighty’s with organizations needing one single software program that was capable of serving the multiple needs and functions of various departments. One single enterprise-wide application software means integrating applications that fused together for the smooth exchange and extraction of information. For example when customer services sold a product and got stock updated in the inventory by the warehouse people and the same data could be pulled by the Finance department. Enterprise Application software’s were designed exactly to do the latter mentioned processes seamlessly. SAP started by break away engineer’s Plattner and group build the company on strong engineering fort…

How Dashboards can mislead

Read an interesting article from John Shapiro professor at Northwestern Kellog on how dashboards can mislead executives and I cannot agree more. To be honest, I love visualization of data and have pushed my data architects and report writers to give me snapshots of various measures but how often the rich data didn't mean anything as it did not align with organizational goals. Even more, what information is important to me is not necessarily relevant to other executives in the organization.  Data analytics visualized on dashboards typically describe existing measures on past phenomena, some better ones predict future events and past data and the best one prescribe a course of corrective or strategic actions.

Shapiro talks about three types of traps executives can fall for:

1. The Context Trap:  We equate empirical data to the objective. I have blatantly used the cliche "numbers don't lie." But this belief can be dangerous because we can track wrong measures or metrics…