Archos Labs
Data as a Decision Infrastructure

Bad Data Is a Symptom Not a Root Cause of Broken Systems

Rob Angeles4 min readPublished
Share
Bad Data Is a Symptom Not a Root Cause of Broken Systems

Bad data is a symptom not a root cause. Learn why data quality reflects broken trust, ownership, and incentives upstream

A CFO once hired me to fix their "data quality problem." Sales numbers didn't match. Customer counts varied by system. Basic facts were fiction.

"We need better data governance," he said. "Maybe some automation tools."

I spent a week there. The data wasn't the problem. The data was screaming about the real problem.

The Upstream Truth

Here's what I found. Sales reps entered fake email addresses because real ones triggered automated sequences that annoyed customers. Customer success inflated usage metrics because low numbers meant budget cuts. Finance kept three sets of books because each executive wanted different math.

The data was perfect. It perfectly reflected an organization where nobody trusted anybody.

Bad data is like fever. You don't cure fever. You cure infection. The fever just tells you something's wrong upstream.

Why Clean Data Gets Dirty Again

I've watched companies spend millions on data cleanup. Six months later, it's garbage again. Always. Because they mopped the floor while the pipe was still leaking.

A retail company cleaned their customer database. Spent $2 million. Pristine data. Within three months, duplicates everywhere. Why? Store managers got bonuses for new customer signups, not returning customers. So the same customer became "new" at every visit.

The data wasn't broken. The incentives were.

Another company standardized product codes. Beautiful taxonomy. Fell apart immediately. Why? Regional managers hoarded inventory by miscoding popular items. The messy data wasn't a bug. It was camouflage.

The Three Real Causes

Bad data has three root causes. Never technical. Always human.

First: No ownership. When everyone owns data, nobody does. A logistics company had five departments updating delivery status. All different. All "correct" according to their needs. Customer sees chaos. Each department sees clarity.

Second: Broken trust. People create bad data to protect themselves. A tech company's support team logged every angry customer as "neutral" because negative scores meant Performance Improvement Plans. Bad data was job security.

Third: Competing incentives. Sales wants growth. Finance wants accuracy. Operations wants efficiency. When these conflict, data dies first. It becomes whatever helps someone hit their number.

The Trust Test

Want to predict data quality? Map trust levels. Low trust equals bad data. Always.

A healthcare system proved this. Departments that shared budgets had clean shared data. Departments that competed for funding had incompatible systems. Not coincidence. Strategy.

People share good data with allies. They hide it from enemies. When your organization treats departments like competitors, data becomes ammunition. Truth becomes liability.

Fixing the Real Problem

Stop cleaning data. Start fixing relationships.

A manufacturing company had terrible inventory data. Instead of new systems, they changed incentives. Warehouse accuracy became shared KPI for warehouse and production. Suddenly, perfect data. Same systems. Different reasons to care.

A bank merged customer service and sales metrics. Combined bonus pool. Customer data magically unified. Nobody needed to be told. They needed to care.

The technical solution is always easy. The organizational solution is always hard. Guess which one works.

The Ownership Revolution

Best data quality improvement I've seen? A company assigned every data element to one person. Not committee. Person. Name on dashboard.

Product prices wrong? Call Sarah. Customer addresses messy? That's Miguel's phone ringing. Brutal? Yes. Effective? Absolutely.

When data has names attached, quality soars. When it's "everyone's responsibility," it's nobody's problem.

Starting Upstream

Next time you see bad data, ask three questions:

Who benefits from this being wrong? Someone always does. Find them.

What are they protecting? Usually themselves. From metrics. From blame. From work.

How can we make good data serve them better than bad data? Change that. Watch quality transform.

Bad data isn't your problem. It's your diagnostic tool. It shows exactly where trust breaks down, ownership disappears, and incentives misalign.

Stop treating symptoms. Start treating causes. The data will fix itself.

Share
Rob Angeles

Written by

Rob Angeles

Most consulting engagements split the thinking from the doing. Rob doesn't. Principal Consultant at Archos Labs, he owns the full stack — assessment, architecture, delivery — across retail, financial services, healthcare, and government.