Fitness for Purpose
Data Quality should only be measured within the context of how it will be used. The concept of “Fitness for Purpose” is central to any data quality metrics within a data governance program.
By Martin Dunn
Data Quality should be measured within the context of how it will be used. The concept of “Fitness for Purpose” is central to any data quality metrics within a data governance program.
Many data governance programs struggle right out of the gate as organizations attempt to define data quality standards for enterprise data. The governance team will often discover that individual business stakeholders have different, sometimes conflicting needs for some enterprise data.
There are many reasons why people have a different view of enterprise data.
1. Legal or regulatory policies may require that an enterprise application preserves the information that was gathered when the contract was signed even if this information is now out-of-date
2. System limitations and/or the prohibitive cost of system modifications result in data anomalies such as creating duplicate customer accounts to handle multiple billing options
3. A customer-facing web site relies upon email for registration and communication, but it also gathers a physical address during registration. The web site uses the customer’s state to distribute the leads to sales-people so it does not really care about the validity of the other address elements resulting in some “bad” addresses in the database.
All three of these examples may impact the number of customer records held in each system and/or the demographic information captured on each customer record. Each individual system owner considers that their data is of sufficient quality even though errors and out-of-date data exists. The data governance team will find it challenging to get alignment around policies for customer addresses from these three system owners without factoring in the purpose of the data.
Data governance teams can avoid much frustration by defining all data quality measures in terms of the intended use of the data, and by recognizing that data created for different purposes can rarely be combined unless the data model recognizes the context of the origination of the data.
Martin Dunn was the co-founder of Delos Technology which developed the MDM technology marketed under the Siperian brand. The Delos MDM technology introduced many MDM concepts that are now widespread within the MDM discipline including a data steward console to adjudicate match results, opt-in synchronization, cell level delta detection and the concept of measuring trust.
Martin is now a partner with Gaine Solutions and continues to advance the techniques by which enterprise Master Data is managed.
Key Questions to Ask During Master Data ConsolidationsTypical master data consolidation starts with combining the operational master records from all the data silos where they exist. The key aspect being, creation of master data indexes to support single view; knowing...
Opt-in SynchronizationNot all operational systems will choose to, or be able to, consume the changes made to master data in an MDM hub. The reasons for being out-of-synchronization may be technical, regulatory, political or economic but at some point it will be...
Changing a Match RuleWhen we are talking to companies about our MDM platform we cover a broad range of topics, from measuring ROI, to more technical questions about the way the software operates. A common technical question is "How do we change a match rule?" Our...
Ready to master data mastering?
Subscribe to our mailing list and we’ll send you courses, insights, product updates, and more. Get to know the ins-and-outs of your Gaine MDX platform, features, and solutions.