Do I really need data governance when I’m doing Master Data Management?
This is a question that I have been asked many times over the years and my answer is always an unequivocal “yes”! Of course that is always followed up with the question “why”? And that one is a little harder to answer…
You can easily Google and find plenty of people that will tell you straight that you need Data Governance for Master Data Management but what they won’t tell you is why. I can understand why that might be the case and I struggled myself for many years trying to describe the relationship between the two until somebody challenged me to come up with an analogy. What I came up was a comparison to how we treat our own physical health.
Value your health = Value your data
If we are really healthy people, and we eat loads of fruit and vegetables and healthy whole foods, and everything we put in or consume is of really good quality and dense in nutrients, we are going to function really well, we are going to be at the top of our performance, we’re going to be in a great shape.
However, if we start consuming only crisps and snacks, sweets, fizzy drinks and food with little to no nutritional value over time we are going to start getting sluggish and tired; we’re going to start getting some aches and pains and perhaps some weird and wonderful symptoms that we’ve never experienced before, and that doctors can’t quite put their finger on. The same is true if you do master data management without Data Governance.
Consider your Master Data Management repository is the human body… if you put good, clean, healthy data into it then it’s going to work really well. You are going to have the right data in the right place, the right processes will work, you will make the right decisions on the data.
However, if you feed your system with rubbish, with poor quality data or missing data parts, or perhaps the wrong data in the field then you’re going to start having things go wrong. Processes fall over and you are going to upset customers or suppliers. Production lines might have to stop because you don’t have the right information or the right parts. Things will start to go wrong and unravel pretty quickly.
You may be thinking that seems a little dramatic but that is based on real life experience, and I have three scenarios that I have really genuinely seen happen as a result of people trying to Master Data Management without Data Governance in place.
In these instances, the data migration onto your new Master Data Management solution has gone well. You’ve had a team of analysts on their project who have worked hard to map the data, to migrate it, to make sure it was good enough quality to go into your new system. All goes well; you have a successful go live, everything is looking really good. But what I can tell you in these circumstances, if you haven’t put in place data governance to protect and proactively manage that data, over time it starts going wrong.
People will start using fields for slightly different things, or people want to change things but there’s no process for agreeing to do that, and so perhaps things can’t get changed and users get frustrated. Or perhaps things do get changed, because you just ask the friendly person in IT and they agree with you and change it, but you cause problems for other people because neither of you understood the downstream impact of making that change. And slowly but surely, over time, without Data Governance in place your MDM solution becomes poor quality, and I can promise you, your users will start complaining about it.
The second scenario I have seen is where the data migration to begin with never even happens. It fails and you fall at that first hurdle. In this scenario, there usually hasn’t been enough engagement with business users and the business hasn’t done enough analysis, or any data quality assessment.
That means we don’t even get to your successful go live that I was describing in the first scenario. In this situation, you can’t even get your data to go successfully into the Master Data Management solution.
Now, in one real life instance where I came across this, it actually was the weekend before the ‘go live’ when they had a dress rehearsal for the data migration and they found so many issues with the data either not being mapped correctly, or it was too poor quality to actually go into the target system, that they actually abandoned it and the whole programme was put on hold with only one week to ‘go live’.
If you’re in the middle of a Master Data Management Programme at the moment, you know as well as I do these are not cheap programmes, and this whole programme was put on hold for 18 months before they managed to get the business case approved to restart it. They had invested a lot of time and effort and significant amounts of money, and it nearly all got wasted! And of course they had all the additional costs of the rework needed to fix the data.
In this scenario, the data is not quite as bad as in the second scenario so we can actually get it into the Master Data Management solution. It has some niggles and some problems, but surely it will alright?! I like to describe this as shoehorning the data into your new MDM system. We just keep pushing and pushing the data until it will eventually load into our new Master Data Management system. The attitude is that once it’s in there, the business can fix it and it doesn’t need to be done as part of the project.
Well, the business won’t fix it because they’ll be too busy telling you how rubbish your new system is, because not only have you got the poor-quality data from the old systems in it, but you’ve probably made it worse by shoving it into a system that’s set up and structured differently.
I even came across one instance where I was told that they had to turn off the relational integrity of the database of the new MDM solution, because the data was so poor that it would break the system and it wouldn’t run if they didn’t!
These scenarios are the realities of the type of scenarios that you are likely to face if you try and do a Master Data Management Programme without Data Governance. The first one is your best-case scenario; that you do a good job to begin with, and then it’s a few years down the line before you start having major problems, but you start having niggly problems quite soon on. Scenarios two and three are quite catastrophic, and you really don’t want to face them.
The Business Case
So why doesn’t everybody just implement Data Governance at the same time as Master Data Management? Well, it usually comes done to issues making the business case for it and often a desire within the business for things to go quicker, or just a poor understanding within the business about the importance of Data Governance.
But the answer to that is simple: if you do Master Data Management with Data Governance, what you’re going to actually have is the right people from the business involved in agreeing which data is going to go into your Master Data Management solution, what the fields really mean, and by agreeing which fields are the right ones to match and merge and you’re going to have data quality rules agreed.
Therefore, you can actually measure the data and improve it both before the migration into the system, and afterwards. And you’ll be laying the framework, the foundations for a successful data migration, and therefore a successful starting place for your master data management solution. I really, really believe that master data management and data governance are better together.
That’s great, but where do I start?
Start with identifying the data domains which are in scope of your MDM solution. It could be customer data, product data orsupplier data, but identify those domains.
Agree who’s going to support Data Governance and MDM, because you want to agree who is going to support the master data system once it’s gone live and you also need to agree who is going to support data governance – it will possibly be the same team.
Go back to your data domains where you have worked out of what is in scope of your Master Data Management solution and agree data owners. And then work with those data owners to create some definitions for the data and some data quality rules, and you’ll be giving yourself a really good start for your MDM initiative.
Don’t forget if you have any questions, you’d like covered in future videos or blogs please email me – firstname.lastname@example.org
Originally published on www.nicolaaskham.com