Lesson 2 — Criticality & Critical Data Elements
DQ effort is finite. Criticality tells you where deeper controls, measurement, and remediation produce the most value.
Critical Data Element (CDE)
A CDE is a data element whose failure would materially impair an important business or customer outcome. Criticality is therefore driven by value and risk, not merely by how many rows contain the field or how frequently it is viewed.
Common drivers include: - regulatory and financial reporting; - operational execution; - customer/product measures; - strategy and competitive differentiation; - financial, regulatory, reputational, customer, and operational risk.
Master and Reference Data are often critical because they are broadly reused. One bad code or identity can propagate across many processes, reports, validations, and controls.
Criticality decision chain
BUSINESS DRIVER → IMPAIRMENT/RISK IF WRONG → DATA ELEMENT → CRITICALITY LEVEL → CONTROL INTENSITY
A rare defect that can cause a regulatory filing error may deserve priority over thousands of low-impact defects.
What criticality is not
- largest table;
- most frequently entered field;
- newest element;
- easiest defect to fix;
- highest raw defect count.
Example
Marketing email completeness is weak, but no revenue or compliance effect exists. A less common tax identifier can trigger financial penalties if wrong. The tax identifier can be more critical even if fewer records are affected.
Exam rule: when the stem gives both defect volume and business impact, do not let volume distract you from criticality.
Source: pp. 428–429.