What’s the best way to conduct an MDM implementation?

Do you find it better for companies adopting master data management to go with an enterprise-wide MDM implementation or deploy it departmentally? Or does it not really matter?

    Requires Free Membership to View

    Login

    When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on the hottest data and information management trends today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchDataManagement.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchDataManagement.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

I have two answers to that question.

First answer: I find it better to implement MDM enterprise-wide. That’s where companies get the biggest bang for their buck. Reconcile product data across diverse product catalogs and all of your suppliers? Golden!

Second answer: No one does that. Or at least, no one starts out that way. MDM projects typically start one system and one business problem at a time, and then branch out. Unlike business intelligence (BI) projects, where you’re usually developing successive BI applications, with MDM you’re progressively bringing on board new systems that need access to master data. So, truth be told, we’re slouching toward master data management one system at a time.

In both cases, the sooner you start, the faster you’ll succeed. Profound, huh?

This was first published in November 2010

Back to top