3 Essentials For Starting and Supporting Master Data Management
3 Essentials For Starting and Supporting Master Data Management
8 August 2022
3 Essentials for Starting and Supporting Master
Data Management
Published 8 August 2022 - ID G00764706 - 14 min read
By Analyst(s): Sally Parker, Simon Walker
Initiatives: Data and Analytics Programs and Practices; Build Trust and Mature D&A
Culture
Additional Perspectives
■ Organizations that fail to engage business stakeholders proactively from the outset
struggle to meet expectations of value. This subsequently impacts their ability to
establish a sustainable operational governance structure.
Recommendations
Data and analytics (D&A) leaders and peers exploring MDM in support of the
organization’s business goals should:
■ Clearly define and articulate the links between the MDM program and the business
outcomes it supports, taking a programmatic approach to MDM by leveraging
proven frameworks that map out the journey.
■ Lay a solid foundation for success by engaging business stakeholders early to agree
upon the prioritized business outcomes their MDM program will support, and to
secure support for a business-driven information governance team.
■ Adopt an MDM architecture most suited to fulfill their current and future goals by
learning the distinct characteristics of the different MDM implementation styles and
their impacts on existing business processes.
Many organizations in touch with Gartner’s MDM analysts are just starting (or sometimes
revisiting) their MDM strategy. From chief data and analytics officers (CDAOs) to CIOs,
marketing leaders and supply chain leaders, the interest in understanding the role of MDM
is high. This is evidenced by a 52% increase in Gartner client inquiries on the topic
between 2020 and 2021. This latent attention to MDM provides these leaders with an
opportunity to benefit from the lessons learned by their predecessors. So for those
considering or embarking upon their MDM journey, what are the key considerations — the
essential, must-know insights on pitfalls and best practices? This research arms D&A
leaders, and their peers with a vested interest, with the fundamentals of MDM across the
three vectors of people, process and technology, rather than technology alone. These three
vectors are shown in Figure 1.
Master data is the least number of consistent and uniform sets of identifiers and
extended attributes that uniquely describe the core entities of an enterprise and are used
across multiple business processes. This may include existing customers, prospective
customers, citizens, suppliers, sites, hierarchies and the chart of accounts.
Analysis
Process: Take a Programmatic Approach to MDM to Avoid Common
Pitfalls
Historically expensive, complex and monolithic, the barrier to entry for MDM has been
lowered recently with the introduction of subscription-based pricing, simpler entry-level
products that leverage graph technologies and cloud-based solutions that facilitate a
viable “start small and grow” approach. However, the pitfalls and lessons learned by
organizations about MDM have arguably been less about technology. Rather, they have
been more about failure to establish a solid foundation with business stakeholders, as
well as failure to agree upon the goals, the measures of success and a plan for
sustainable governance of the “mastered data.” For example, an outcome-based approach
to MDM in favor of a data-issues-based approach will naturally lead to a leaner, narrower-
scoped program.
1. Establish a maturity baseline leveraging Gartner’s MDM Maturity Model (see Create
a Master Data Roadmap With Gartner’s MDM Maturity Model).
The MDM Operating Model is one of several key planning domains within the Gartner
Data and Analytics Strategy and Operating Model (see How to Craft a Modern, Actionable
Data and Analytics Strategy That Delivers Business Outcomes). It comprises six steps
that are sometimes executed concurrently, to some extent. However, the first step, “scope,”
is fundamental, as it involves aligning the MDM initiative with the business outcome(s) it
supports, and clearly articulating the value it will provide.
The large majority of organizations leverage the services of a third party for assistance
with their MDM strategy and/or implementation. The benefits of engaging a services
provider with expertise in your specific industry often extend beyond supplemental skills,
to industry accelerators and data models to fast track time to value. However, the MDM
Operating Model serves as a blueprint to keep your MDM program focused, irrespective of
whether a third party is engaged. For further information on considerations regarding
MDM service providers, see Market Guide for MDM External Service Providers.
Human factors continue to represent the most prevalent stumbling block for MDM
initiatives, primarily through a lack of communication. Organizations that fail to engage
proactively with business stakeholders from the outset to establish and agree upon a
prioritized set of goals (outcome and metric) will struggle to meet their expectations of
value. Consequently, they will be challenged to establish the operational governance
structure (with clarity on roles and responsibilities) that is required to achieve sustainable
governance of their master data.
In a perfect world, an MDM strategy will reflect priorities in the D&A strategy. This, in turn,
reflects corporate (or, in the public sector, departmental) priorities. However, we do not live
in a perfect world, and establishing a stakeholder connection for collaboration often
stems from starting a conversation around the pain points associated with master data,
and how resolving these impacts specific goals or KPIs. MDM program managers should
be able to draw a causal link between any proposed MDM program and the business
outcomes that matter to these stakeholders to take them on the journey. For more
information, see 7 Steps to Build a Successful Business Case for MDM Programs and
Toolkit: How to Connect Data to Business Outcomes.
The best-practice team structure is owned and operated by the business (as opposed to
IT) and is tiered into layers such that the establishment of policy takes place at the
highest level (e.g., the governance council or board), while the next level involves policy
enforcement (e.g., data stewards). Enterprises often misuse the term “steward” to indicate
resources that actually perform the day-to-day functions of data maintenance, so make
sure to make a clear distinction when planning your approach. In addition to standard
data governance and management functions, it is also productive for the governance
team to manage and maintain the design artifacts within the MDM program. See A Day in
the Life of a Data and Analytics Steward.
Figure 3 depicts these best practices. Note that the sponsors, the governance board and
the data stewards are all on the business side, although collaboration with IT in the areas
of project management and business modeling often occurs. They are also supported by
the various teams within IT that are required to support the pertinent information
management infrastructure. In the case of master data governance, these would be the IT
resources supporting the MDM infrastructure. In situations where governance has
expanded to include other categories of data, the IT and information management teams
corresponding to that data should also support the business side.
Enterprises that follow these guidelines are able to build robust and lasting governance
teams that foster productive processes and relationships across the business and IT, and
that help ensure the continuing success of the MDM program. Organizations that create
teams or processes that are either overly simple or overly complex are virtually certain to
waste valuable time and resources on an MDM program that fails to provide lasting value.
Styles are also evolving to include augmented or contextual MDM (see How Augmented
Data Management Capabilities Are Impacting MDM and Data Governance). For the
purposes of this research, however, the foundational four styles serve to demonstrate
considerations related to the varying degrees of impact or intrusiveness to existing
business processes.
The styles may also be used in combination. For example, placing a registry within a data
warehouse for master data would, in essence, combine the consolidation and registry
styles.
Organizations will often start with the styles that are least invasive to the current
environment while still meeting early requirements. Then, they may work through the more
invasive styles over time (tracking delivered benefits throughout) until the desired end
state has been reached. This results in the creation of an MDM roadmap that
acknowledges that styles may evolve over time based on organizational maturity, domain
maturity and respective needs. An organization can start with the registry style to avoid
changes to operational applications. Another might bypass registry style and start with
consolidation style, to start to enforce rules around master data (arrived at via their data
governance process in a persistent data hub). For further information on implementation
styles, see Accelerate Business Value by Using Gartner’s Master Data Management
Implementation Styles and Implementing the Technical Architecture for Master Data
Management.
Organizations that anchor their MDM technical and business deliverables to recognized
interim implementation styles are able to effectively plan the MDM program in terms of
required resources, and to communicate achievement milestones within the enterprise.
Those that do not follow these guidelines risk unclear communication of technical
capabilities, as well as scope creep for each functional release, which has resulted in
failure for many MDM programs.
DASOM The Data and Analytics Strategy and Operating Model (DASOM)
framework enables chief data officers (CDOs) to create a strategy
that meets the needs of a modern and forward-looking
organization.
© 2023 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of
Gartner, Inc. and its affiliates. This publication may not be reproduced or distributed in any form
without Gartner's prior written permission. It consists of the opinions of Gartner's research
organization, which should not be construed as statements of fact. While the information contained in
this publication has been obtained from sources believed to be reliable, Gartner disclaims all warranties
as to the accuracy, completeness or adequacy of such information. Although Gartner research may
address legal and financial issues, Gartner does not provide legal or investment advice and its research
should not be construed or used as such. Your access and use of this publication are governed by
Gartner's Usage Policy. Gartner prides itself on its reputation for independence and objectivity. Its
research is produced independently by its research organization without input or influence from any
third party. For further information, see "Guiding Principles on Independence and Objectivity." Gartner
research may not be used as input into or for the training or development of generative artificial
intelligence, machine learning, algorithms, software, or related technologies.
Webinar Webinar
The Foundations of Master The Gartner Top Trends in Data
Data Management & Analytics for 2023
Get an MDM framework that incorporates Explore how to optimize your resources,
best practices for people, process and speed up change and drive innovation.
technology.
eBook Roadmap
An Essential Guide to Enhance Your Roadmap for Data
Data Fabric and Analytics Governance
Find out why data fabric belongs in your Learn how your peers are executing
data management thinking. effective data governance initiatives.
Already a client?
Get access to even more resources in your client portal. Log In
Connect With Us
Get actionable, objective insight to deliver on your mission-critical
priorities. Our expert guidance and tools enable faster, smarter
decisions and stronger performance. Contact us to become a client:
Become a Client