Defining the proper business case is a critical requirement before deciding what Customer MDM approach and architecture to adopt. MDM is not exclusively a technology issue, but it is also a business capability. As such, companies need to align the proper MDM implementation with their overall strategy to address one or more of the following: risk mitigation, cost reduction, and/or revenue growth.
Not all Customer MDM implementations are the same. Analytical, operational, and enterprise MDM offer different challenges from both IT infrastructure and business model perspectives. Addressing analytical or operational data will lead to distinct levels of complexity, risk, and impact that need to be fully analyzed.
Customer MDM requires bringing many disparate data elements, systems, and processes into a common framework. But this involves a lot more than just data integration. It also requires aligning multiple business units into an integrated set of data, processes, rules, standards, policies, and procedures. It is about fostering collaboration to achieve a high level of success in overall data management, including: data governance and stewardship; data quality; data architecture, analysis, and design; data security; business intelligence; and reference and metadata management.
MDM is not a one-time project. It is a very pervasive program that requires executive sponsorship and complete collaboration from the many groups impacted. It also doesn't have a predefined formula. Current data management maturity within the company will dictate the proper steps to be taken, making it very important to position yourself properly from the beginning. Don't be discouraged, though. It is a long and tenuous road but very worthwhile in the long run. If done right, the outputs more than justify the inputs.