Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

8 Key Takeaways From the MDM and Data Governance Summit

DZone's Guide to

8 Key Takeaways From the MDM and Data Governance Summit

As I reflect back on the conference, I wanted to share some of my key highlights and takeaways from the event as we all start to prepare for our IT and data strategies in 2018.

· Big Data Zone ·
Free Resource

Hortonworks Sandbox for HDP and HDF is your chance to get started on learning, developing, testing and trying out new features. Each download comes preconfigured with interactive tutorials, sample data and developments from the Apache community.

A few weeks ago, I had the great opportunity to attend the MDM and Data Governance Summit held in NYC. The summit was packed with information, trends, best practices, and research from the MDM Gartner Institute. Much of the information is something you don't find in webinars or white papers on the internet. Speakers were from many different industries who brought different perspectives to the data management concepts.

I also got to meet IT business executives who are all along different parts of their MDM and data governance journey. As I reflect back on the conference, I wanted to share some of my key highlights and takeaways from the event as we all start to prepare for our IT and data strategies in 2018.

1. MDM Main Drivers

The top five main drivers of MDM are:

  1. Achieving synergies for cross-selling

  2. Compliance

  3. Customer satisfaction

  4. System integration

  5. Economies of scale for M&A

A new driver also has been considered recently — digital transformation — and MDM is at the core of digital transformation.

2. IT and Business Partnerships are More Important Than Ever

If there was one thing that everyone at the summit agreed upon, it was that the partnership of the business and IT directly impacts the success of the MDM and data governance programs more than any other factor. For one banking company, this happened naturally, as the business also understood the power of data and the issues related to it. But largely, the experience of the people involved in this partnership is that it's an uphill battle to get the buy-in from the business. Tying the project to a specific business objective is critical in these scenarios. The bottom line is that a solid partnership between business and IT will provide the right foundation for an MDM program.

3. Managing Change Is Critical

It's widely accepted that any MDM journey is long, and takes energy and perseverance. One company mitigated this process by starting with the domain that they thought would have the most impact.

4. Data Governance Council

Only about 20% of the audience had some form of data governance council but all the case studies presented had a data governance council in place. The council was made up of both business teams and IT teams. There is no real pattern from the organizational structure perspective. An insurance company that has a hugely successful MDM implementation has the Enterprise Information Management Team as part of the Compliance Team. Another financial company had the team reporting to the COO. It all depends on how your company is organized and does business.

5. GDPR

This topic was everywhere. 50% of the audience said they were impacted by this regulation. But looks like a lot of companies still lag way behind in terms of preparing their enterprise data for compliance. This is a serious issue, as there are less than 150 days to get ready. One of the speakers said that MDM is the heart of GDPR implementation.

6. Next-Generation MDM

Data-as-a-Service is something every company should aim for in the next two to three years. Also, bringing in social media and unstructured data will be key to gain actionable insights from MDM initiatives. Large enterprises have moved beyond CDI and PIM to focus on relationships and hierarchies. Cloud MDM will be in demand, but there is potential for creating more data silos as integration becomes a challenge.

7. Big Data Lakes

There are just too many technologies in the Big Data space. Therefore solution architecture becomes key when building a Data Lake. A common implementation was to load the data from legacy systems into Hadoop without any transformation. But without metadata, the lake quickly becomes a swamp. So, to get true value from Big Data Analytics, MDM and Data Governance have to be effective and sustainable. Also from a technology perspective, there needs to be sound integration with big data systems. My company Talend has been at the forefront of Big Data Integration providing a unified platform for MDM, DQ, ESB and Data Integration.

Quotes

Finally, I want to end this blog with some great quotes from the speakers:

  • "Digital transformation requires information excellence."

  • "If you don't know where you are, a map won't help."

  • "Big data + data governance = big opportunity."

  • "Data is a precious thing and will last longer than the systems themselves."

  • "There is no operational excellence without data excellence."

  • "A shared solution is the best solution."

  • "People and processes are more critical than technology."

  • "Rules before tools."

  • "Master data is the heart of applications and architecture."

  • "There is no AI without IA (Information Agenda)."

As you prepare for MDM and data governance initiatives in 2018, I hope some of my takeaways will spark new ideas for you on how to have a successful journey to MDM.

Hortonworks Community Connection (HCC) is an online collaboration destination for developers, DevOps, customers and partners to get answers to questions, collaborate on technical articles and share code examples from GitHub.  Join the discussion.

Topics:
big data ,data governance ,data management ,digital transformation ,mdm ,gdpr ,data lakes ,data analytics ,unstructured data ,data integration

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}