MDM, or Master Data Management, is one of those concepts that just makes sense without a lot of explanation. Thus, while I have to explain what it is, I almost never have to sell it.
This is a good thing, considering that the majority of work around MDM is really building the knowledge within people, and then the processes around the people to make MDM a reality. There is indeed a technology component, but it's actually the easiest problem to solve in the world of MDM.
So, let me get this straight, the concept is to manage data centrally thus eliminating redundancy and improving data quality. That's good, right? You would think.
Giving that MDM is largely a people issue I am finding that those in IT looking to implement MDM are having huge issues with selling the MDM concept internally. The core issue is that many promoting MDM are not "politically connected" and thus have a hard time implementing a MDM strategy, which is systemic to enterprise IT, and thus touches a bit of everything, including turfs.
What is obvious to those who read MDM blogs seems to get lost in translation to the rank and file IT guys, or those charged with running IT. Many see MDM as something that's going to remove control from those who are masters of databases and applications, and while no such thing is ever proposed, MDM strategy after MDM strategy is shot down out of the gate for political reasons.
I hate company politics such as this, since they are typically looking out for their own personal interest over the interest of the company. However, they are also the people that seem to survive and advance.
What's so bad about this is that many of you reading this blog are nodding your heads in agreement, and are experiencing the same issues within your enterprise. I'm not sure where MDM became so difficult to understand, and hard to implement, but it clearly is these days. You'll have to work around the meatheads.