Share this content

Gartner reveals the 10 myths of master data management

26th Jan 2011
Share this content

Despite the potential benefits of adopting master data management tools and techniques, achieving them often entails overcoming "formidable" technical, organisational and political hurdles, Gartner has warned.

The market research organisation defines MDM as a "technology-enabled discipline that ensures the uniformity, accuracy, stewardship and semantic consistency of an enterprise’s official, shared master data assets". As a result, it can enable organisations to introduce change more quickly, lower IT and business costs and improve business performance if dealt with effectively.

Andrew White, a research vice president at the firm, said: "MDM is the latest attempt to solve the old problem of inconsistent versions of important data at the centre of the organisation. As with any new initiative, there is a lot of hype and confusion, and with hype and confusion comes misunderstanding."

As a result, there were 10 key myths surrounding MDM, he added.

Myth 1: MDM is about implementing a technology
Reality: MDM is much less about technology and much more about understanding how business processes are supposed to work.
Myth 2: MDM is a project
Reality: MDM is implemented as a programme that forever changes the way the business creates and manages its master data. However, to adopt MDM will require numerous discrete projects.
Myth 3: We don't need MDM; we have an enterprise data warehouse
Reality: MDM should/will span the organisation across all business units and processes (including data stores, operational and analytical).
Myth 4: Implementing ERP means you don't need MDM
Reality: Enterprise resource planning (ERP) generally means a packaged business application strategy, most often centered on a single, large vendor. ERP implied, but rarely realised for the user organisation, a single process and data model across the organisation.
Myth 5: MDM is for large complex enterprises only
Reality: The principle of MDM is applied whenever two or more business processes must view or share (master) data. This means that most organisations have a need for the discipline of MDM even if they don't call it that, or if they implement a separate technology called MDM.
Myth 6: Metadata is ‘the’ key to MDM
Reality: Metadata is critical to MDM (and many efforts outside MDM), but how metadata is applied in the context of MDM differs by domain, industry, use case and implementation style.
Myth 7: MDM is an IT effort
Reality: MDM must be driven by the business, a business case, and supported/enabled by IT.
Myth 8: MDM is just too big to do
Reality: MDM can be and is most presently being adopted one domain or province at a time, and one use case at a time.
Myth 9: MDM is separate to data governance and data quality
Reality: MDM includes governance (of master data) and data quality (of master data) — MDM cannot be established without them.
Myth 10: It doesn't matter which MDM technology vendor you use — they all ‘do’ MDM
Reality: MDM is complex; rarely do two organisations' MDM programmes look alike. Vendor MDM capability has also focused on specialisation across data domain, industry, use case, organisation and implementation style. Consequently, vendor selection is critical if organisations are to find the right partner.

Replies (0)

Please login or register to join the discussion.

There are currently no replies, be the first to post a reply.