Trace a Broken Dashboard With Five Whys
Use Five Whys to identify catalog-control gaps behind a data reuse incident.
A CEO dashboard used a deprecated churn table because it ranked first in catalog search and had no visible stale warning. Five Whys: symptom -> chain of causes -> process countermeasure Stopping at 'the analyst should have checked' feels satisfying but does not change the catalog conditions that made the mistake likely. Why 1 Why was the wrong churn table used? It ranked first in catalog search and looked active. This points to catalog signals, not just analyst behavior. Why 2 Why did it look active? It had no deprecation label, no successor link, and old high page views boosted…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in