Compression Teach-Back & Repair
5-minute teach-back
Teach Chapter 13 in this order:
purpose/context → criticality → dimensions/rules → PDCA → causes → seven activities → operations → tools/techniques → implementation/Governance → standards/SPC
Your explanation should connect each stage causally, not merely list headings.
2-minute teach-back
Explain only: - nine common dimensions; - four high-risk dimension pairs; - seven formal activities; - five DQ Operations sub-activities; - prevention vs correction vs root cause; - SLA vs scorecard; - profiling vs monitoring.
30-second teach-back
Data Quality is fit-for-purpose relative to consumer requirements. Focus on critical data, translate needs into measurable dimensions and rules, assess actual data, prioritize by business impact, prevent/root-cause defects, operate rules/monitoring/issues/SLAs continuously, and use Governance plus transparent metrics to sustain improvement.
Self-score
- 2 points: correct from memory with the deciding distinction and a valid example.
- 1 point: broadly correct but vague, missing the deciding clue, sequence, or example.
- 0 points: wrong, guessed, or required immediate source lookup.
Repair only the miss
- Identify the exact failed distinction or sequence.
- Classify the miss: vocabulary; dimension pair; rule/metric/threshold; lifecycle; role; RCA/correction; tool/activity; SLA/reporting; qualifier; overthinking.
- Review only the controlling Guided Learning/Battle Card/source section.
- Close the material.
- Restate the rule in one sentence.
- Create one changed-fact example that flips the answer.
- Retry after a delay.
Do not prebuild Artifact 08. Only repeated real misses, slow decisions, or confidence mismatches belong there later.
Final reconstruction
Write this from memory:
CONSUMER PURPOSE → BUSINESS IMPACT / CRITICAL DATA → DIMENSION → RULE → BASELINE / PROFILE → THRESHOLD → ISSUE → ROOT CAUSE → PREVENT / REMEDIATE → OPERATE / SLA → MONITOR / TREND → GOVERN / IMPROVE
If you can reproduce the words but cannot explain why Integrity beats Completeness for a populated orphan foreign key, or why Currency beats Timeliness for on-time stale data, return to the confusion drills before retesting.