The real cost of ignoring master data management
It is rarely the thing that gets a project approved, and often the thing that decides how it goes. Nobody bills you for neglecting master data management. The cost shows up somewhere else.
Most data problems are ownership problems that turned into technical ones. If two people in the business would answer this differently, that gap is the actual problem.
Where the cost lands
- Time spent on work that should not have been necessary
- Enquiries that quietly never arrive
- Two systems with different customer records will disagree at the worst moment
- Rework, once the problem is finally visible
Decide which system is authoritative for each entity. In practice this is a scheduling problem more than a technical one. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.
What to do next
Reconciliation is cheaper than arbitration later. The cost of getting this wrong is rarely visible on the day it happens. It is the sort of thing that looks like polish right up until it costs you an enquiry.
What this looks like day to day
Data outlives the applications built on top of it, which is why the model deserves more thought than the screens. Three things worth confirming about master data management before you move on:
- Someone can say what the current setup is without going to look
- Reconciliation is cheaper than arbitration later — and you know whether that is true here
- There is a way to tell whether the last change to this helped
If you want a second opinion on how yours is set up, ask.