Are You Really Ready to Buy a Master Data Management Tool?

Loraine Lawson

Gartner analyst Andrew White recently posted a "tale of two MDM initiatives," from which he reaches two conclusions:


  1. It's very, very hard to succeed with master data management when you don't have a larger information management strategy.
  2. With MDM, governance, process and organization are more critical to success than technology.


Time and time again, I've read that MDM is not a technology. Recently, Contraste Europe consultant Tod McKenna used a term I really liked, describing MDM as a "capability." As White points out, MDM is more about the strategic elements-governance, the processes and organizational change-than a tool you buy in the box.


I can see where companies would look to technology for MDM. MDM products are impressive and powerful. But, as information management consultant David Loshin explains in a recent BeyeNetwork article, you'll cause more problems than you'll solve by buying technology before you've laid the MDM foundation:


"... acquiring an MDM system should be the culmination of preparatory steps taken once the organization is prepared to make the hard decisions regarding business process modifications, application retirement, application migration, and data governance. Purchasing decisions made prematurely ... may lead to roadblocks and stonewalling that will impact the success of the program."


Last month, Loshin began a series of checklists to help organizations get ready for MDM. The first checklist was designed to help you identify and communicate the business drivers for MDM.


In the second installment of the series, Loshin provides a checklist of questions designed to measure your organizational preparedness for MDM.


The list covers all the stuff you'll need to figure out before you buy an MDM solution and, believe me, these are not easy, multiple choice, true/false stuff. They're more like essay questions, designed to determine how deeply you've thought through the issues.


Here's a sample from his excellent list:


  • What business processes will need to change to accommodate a master data environment?
  • What business processes will be eliminated or overhauled as a result of the transition?
  • Is there an existing or planned enterprise architecture?
  • Will enterprise architects oversee changes needed to move to a master data environment?
  • Are there potential synchronization issues for real-time business application use of shared master data? If so, how will you address them?


Hard questions-but as you answer them, you'll be doing the type of work White says you need to do to succeed with MDM.


Until you can answer all the questions on this checklist, Loshin wisely warns, hold off on the vendor dog-and-pony show.

Subscribe to our Newsletters

Sign up now and get the best business technology insights direct to your inbox.


Add Comment      Leave a comment on this blog post
Jun 28, 2009 11:27 AM M Ellard M Ellard  says:

Thanks for the post and the link to David Loshin's blog on this topic. Never enough said on the importance of setting a foundation before diving into MDM. Saw a Pitney Bowes white paper on this topic - specifically re: data quality: http://www.pbinsight.com/files/resource-library/resource-files/DQinMDM_WP.pdf...

Jul 7, 2009 7:56 PM Marty Moseley Marty Moseley  says:

I agree w/ the recommendations, but want to provide what I believe is a needed balance for organizations where the political environment may preclude getting all their ducks in a row before proceeding w/ the technical portion of a MDM solution.  Having worked in my share of those highly-political organizations, I've seen a project like an MDM project "break the log-jams" due to indecision, disagreement, infighting, and other passive-aggressive behaviors.  That said, the basic counsel of this article and of David's writings hold true: 

- articulate the business value for MDM (MDM business case)

- define the short- and long-term technology environments within which this ecosystem will interoperate (enterprise architecture)

- gain commitments from stakeholders to craft shared data policies and rules,  modify business processes, systems, integration points, etc. for it to be successful (data governance)

- pick the right technical solutions

The journey of 1000 miles begins with the first step. Don't get caught in preparing for the journey so long that you never make progress towards actually solving the problems.

Jul 23, 2009 12:50 PM GIS Services GIS Services  says:

Quite informativeThanks for sharing nice post..


GIS data processing


Post a comment





(Maximum characters: 1200). You have 1200 characters left.




Subscribe Daily Edge Newsletters

Sign up now and get the best business technology insights direct to your inbox.

Subscribe Daily Edge Newsletters

Sign up now and get the best business technology insights direct to your inbox.