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?
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?
Dig Deeper on MDM best practices
Related Q&A from Jill Dyché
Do you need to gather business requirements for an MDM project? Find out and learn how functional requirements are the key difference between the MDM... Continue Reading
Learn about the most common master data management (MDM) project pitfalls that companies run into. Get a list of the major problems that can hold ... Continue Reading
Learn how to include data policies and data governance in a master data management (MDM) development process even if your company doesn’t want to ... Continue Reading