data quality and qa

Root Cause Analysis

Identifying the underlying source of repeated quality failures, rather than treating each one individually.

Root cause analysis takes a cluster of related failures — identified through error analysis or error bucketing — and digs into why they're happening: an ambiguous line in the guidelines, a reviewer applying an outdated standard, a taxonomy gap, or a systematic misunderstanding shared across a specific group of annotators.

The output of root cause analysis should be a fix at the source rather than repeated correction downstream — a guideline clarification, a targeted recalibration session, or a taxonomy update — since re-rejecting the same category of mistake indefinitely is far more expensive than fixing why it keeps happening.

This discipline is what separates a QA process that actually improves over time from one that's stuck perpetually catching the same errors batch after batch.

What this means for trainers

If you keep getting the same type of feedback across multiple rejections, that pattern is worth naming explicitly when you escalate or appeal — it helps whoever's doing root cause analysis find the actual source faster.