Data Management Strategies for the CIOWhat have you found to be the most common master data management (MDM) project pitfalls that companies get victimized by?
Requires Free Membership to View
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
You, dear reader, have just unwittingly asked me to write my master’s thesis. Talk to you in two years -- bye!!!
Seriously, the answers to this question are many and long. But here’s a “few and short” list of the major culprits that can hold back an MDM project:
- Organizational politics and ownership debates.
- Lack of sanctioned decision-making processes.
- Sketchy understanding of the data in operational systems.
- Organizational politics and ownership debates.
- Inability to convince management to adequately fund MDM.
- Applying existing development methodologies to (new) MDM functionality.
- Organizational politics and ownership debates.
- Choosing an incumbent vendor’s MDM tool irrespective of its ability to meet requirements.
- Not sufficiently qualifying members of the MDM development team.
- Organizational politics and ownership debates.
- Lack of data governance processes to support business-developed data definitions and data policies.
Oh, and did I mention organizational politics? I did? OK, good.
This was first published in November 2010