What it means
Data quality dimensions provide a repeatable way to judge whether information is complete, accurate, consistent, timely, valid, and fit for its intended use.
Why it matters
A dataset can be technically available and still produce unsafe decisions when its defects are not measured against the purpose, users, and consequences of the analysis.
Practical focus
- Define the scope, owners, acceptable risk, and required outcome for data quality dimensions before choosing a tool or platform feature
- Implement quality rules, ownership assignments, acceptance thresholds, and exception workflows through documented, reviewable configuration and change control
- Collect profiling results, failed-rule counts, trend reports, and approved exception records and compare the results with approved baselines, service objectives, and policy requirements
- Exercise a critical quality rule failing after a source, schema, or transformation change as a planned test case, including detection, containment, rollback, escalation, and evidence retention
Common mistakes
- Treating data quality dimensions as a one-time technical setting instead of an operating control with owners and review cycles
- Using default thresholds or broad exceptions without connecting them to business, privacy, security, and availability requirements
- Keeping evidence in disconnected tools so reviewers cannot reconstruct who changed what, why it changed, or whether it worked
- Testing only the normal path and discovering during an incident that a critical quality rule failing after a source, schema, or transformation change was never rehearsed
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: