What is Data Quality Management?
Data quality management, told as a story about continuously tending the reader address list so it's never wrong, missing, or duplicated.
The address was wrong, so the book went to the wrong house.The same reader sometimes got sent two copies.
What happens when cleaning the list keeps getting put off.Messy address data means even a well-written book never reaches the reader.
Data quality management keeps the address list accurate, complete, and duplicate-free, continuously.The list is never cleaned just once — it needs constant attention.
Data quality is measured by dimensions like accuracy, completeness, consistency, and timeliness. There's no fixed count, so uniqueness and validity are often added.The list gets proofed just like a manuscript's typos.
Keeping the list clean doesn't end with a single cleanup.Keeping the list clean is closer to tending a garden, continuously.
Data quality management = continuously tending the reader address list so it stays accurate, complete, consistent, and timely.
Data quality management measures and refines data against standards like accuracy, completeness, consistency, uniqueness, and timeliness. Profiling diagnoses the current state, cleansing fixes errors, and rules are then set at the point of entry to prevent new ones. It isn't a one-time cleanup — it runs continuously within a data governance framework.
When grown-ups say it
- Data Quality Management
- The whole business of continuously tending the address list. Measured by dimensions like accuracy, completeness, consistency, uniqueness, timeliness.
- Data Profiling
- Diagnosing the address list's current state first. Done before cleansing.
- Data Cleansing
- Directly fixing wrong or duplicate entries. Never finished after just one pass.
- Data Governance
- The framework for who manages the address list and how. The structure that keeps quality management ongoing.
- Data Standardization
- Unifying the format addresses are written in. One way to keep consistency.
- Master Data Management
- Unifying one reader's records into a single one. The key to preventing duplicate address entries.
- Requirements Engineering
- Deciding in advance exactly what must be recorded. Even address-list fields ultimately come from a spec. → the one who asks before writing
- IS Audit/PMO
- The checker who watches the whole publishing run. Database audits can look at data quality too. →the checker who watches the whole publishing run