The day a whole region vanished from the dashboard

A few years ago I was asked to look at an executive dashboard that tracked sales pipeline across global regions. One region showed zero pipeline. Not low. Zero.

Nobody had noticed, because there was nothing to notice. The nightly job ran on schedule. No alert fired. The charts loaded and the numbers looked tidy. The dashboard was technically perfect and factually wrong.

The root cause turned out to be two independent failures working together. An internal reference table that mapped records to regions had gone stale, so a large set of records stopped matching. Separately, a key field used when joining two tables had a data-quality mismatch, so records that should have lined up fell through the join. Either failure alone might have looked like a dip. Together they erased a region.

That incident is why I say this: the most dangerous data bug is not a crash. A crash is loud. The dangerous bug is a believable number that nobody questions.…