Lightweight Data Governance: A Starting Point

This expands on the previous article, Lightweight Data Governance. I’ll continue to add to the theory in upcoming posts. If there are any areas you would like me to focus on, please add a comment, or email me directly.

A few weeks back I met with Steve Sarsfield to discuss the upcoming MIT Information Quality Symposium (MITIQS). It will be my first time presenting to a Data Quality focused group, so I was excited when Steve offered to provide some background. My main concern was, “How can someone in the commercial space keep the interest of a combined business, government and research focused community?” We discussed my approach, and I think I’m on the right track. I’m going to describe how we initiated Data Governance at my company, kept it simple, and found early success.

So where did we start? Data Governance grew from an expressed need by the executive team for better data quality. Sounds simple right? Fix the data. It’s like the Kenan Thompson SNL character talking about the economy: Fix It. The company decided that Data Governance was needed, and that they would let me define the path to getting there. I set the scope to include any project where I have an opportunity to build credibility in data or reporting. I’ve formalized processes where necessary, but kept it “lightweight” in most areas. With the current state of the economy, I see no other way to get there.

I previously led the Marketing Analytics department, and we had responsibility for B2B and B2C Analytics. Most of our efforts were focused on the B2B side, since that’s where the most perceived opportunity existed. When I moved into the Director of Global Data Governance role, I built from my strength and worked on B2B issues first. I attacked the low-effort, high-value projects. I looked to expand on the local efforts that were working well. If teams or projects came up with creative solutions, I looked to expand their work globally. My thought was that it’s really hard to come up with the underlying process definition, but that an existing process was easy to expand. It doesn’t work for every existing process, but some are natural fits that resolve longstanding internal issues.

That became the basis for Lightweight Data Governance. Find the projects or efforts that are successful on a small scale, and expand them globally. That way you start with a base of knowledge, documentation, and executive support that’s very hard to build from scratch.

Grow Data Governance efforts organically

Start with existing processes. Find out which can be expanded, centralized or automated.

Focus on project level ROI

Don’t try to sell your management on a huge program to start. Build the business case at the project level. It’s easier for management to support small positive ROI projects.

Partner to be unobtrusive to ongoing work

Find projects that are already in flight. Would Data Governance add to their impact? If so, partner with their leadership to help craft the deliverables to create mutual benefit.

Build momentum from early successes

Get testimonials! If the project went well and the community benefited, you should be able to get the project sponsor to say so.

Measure initiatives on DQ impact

This step is further along the Data Governance continuum. Begin to show the impact on the organization when projects focus on data quality. This cultural shift will underscore the importance of future Data Governance work.

Follow with Formal Data Governance

Does it make sense for the enterprise? Does executive support exist? If not how do you build it? This is where the more traditional theory in most Data Governance efforts becomes relevant.