CDMP-RMD practice question 31 of 35

Which of the following reasons is a reason why MDM programs are often not successful?

Full set: 100 questions
Answer options
A: Too much emphasis on technology rather than people and process components
B: All of the above Correct answer
C: Poor positioning of MDM program responsibility within the IT organization
D: Not enough business commitment and engagement
E: MDM initiative is run as a project rather than a program
Correct Answer:
B. All of the above
Explanation

Master Data Management (MDM) is a complex, business-led discipline, not merely a technology implementation. Its success depends on a holistic approach. Each option listed represents a common and critical failure point. An overemphasis on technology (A) ignores the essential governance and stewardship (people and process) needed to define and maintain master data. Lack of business commitment (D) results in poorly defined data and low adoption. Treating MDM as a finite project (E) instead of an ongoing program leads to the decay of data quality post-implementation. Finally, poor organizational positioning (C), such as isolating it within IT, severs the program from the business owners who must lead it. Therefore, all listed factors are significant reasons for MDM program failure.

Why Incorrect

A. This is a valid reason for failure, but it is not the only correct option among the choices.
C. This is a valid reason for failure, but it is not the only correct option among the choices.
D. This is a valid reason for failure, but it is not the only correct option among the choices.
E. This is a valid reason for failure, but it is not the only correct option among the choices. ---

References

1. DAMA International. (2017). DAMA-DMBOK: Data Management Body of Knowledge (2nd ed.).

Page 351, Section 11.5.1, Business Case: "MDM requires significant business involvement... Lack of business sponsorship is a key reason for failure." (Supports option D).

Page 357, Section 11.7, MDM Implementation: "MDM is a program, not a project. It requires ongoing effort to maintain data and processes." (Supports option E).

Page 347, Figure 103: This diagram shows MDM as an intersection of people, process, and technology, illustrating that an over-focus on technology at the expense of the others is a flawed approach. (Supports option A).

Page 356, Section 11.6.2, Stewardship: Emphasizes that MDM governance and stewardship roles are business-focused, implying that positioning the program solely within IT is a structural weakness. (Supports option C).

2. Loshin, D. (2009). Master Data Management. Morgan Kaufmann.

Chapter 3, The Business Case for MDM, Page 46: "Without a clear business case and executive sponsorship, it is unlikely that an MDM program will succeed." (Supports option D).

Chapter 12, Pitfalls and Best Practices, Page 235: Loshin explicitly lists "Believing that MDM is a technology project" as a key pitfall, highlighting the need to balance technology with business process and governance. (Supports options A, C, and E).

3. Spruit, M., & Pietzka, K. (2015). MDM-as-a-service: The key to successful master data management? Computers in Industry, 68, 111-122.

Section 2.2, MDM Challenges: The paper discusses organizational challenges, stating, "A lack of business involvement and unclear responsibilities are major reasons for MDM projects to fail... MDM is often seen as a purely technical IT project, which it is not." This statement synthesizes the validity of options A, C, and D. DOI: https://doi.org/10.1016/j.compind.2014.12.004

Scroll to Top