Meet the usual suspects.

Everyone in the room knows the number is wrong. Nobody wants to be the one who says whose number it is.

So the problem goes unnamed.

And an unnamed problem cannot be assigned, funded, or fixed. It sits there collecting interest until it lands on someone downstream who had no say in creating it.

That is the gap The Data Crime Files were built to close. Nine characters. Nine failure patterns I have watched cost real programs real money, credibility, and weekends.

The Bad Data Bandit does not break into your organization. He is already living inside the records nobody owns.

The Spreadsheet Smuggler moves critical data outside the governed system.

The Silo King protects his kingdom while the enterprise pays the price.

Freeze-Date Frank locks the data before the business is finished changing it.

They are portrayed as animals in tailored coats for a reason.

“We have a duplicate problem nobody owns” is a sentence that often gets softened before it reaches the steering committee.

“The Bandit is inside our customer master” is a sentence the room can actually say.

It identifies the crime without putting a colleague on trial. Once the risk is named, it can be owned. Once it is owned, it can be priced. And once it is priced, leadership can decide whether to fix it or knowingly accept it.

Two suspects are harder to confront.

Ego Eddie protects his image over the truth. Lazy Larry delays the decision until delay becomes the decision.

Those are not data conditions. They are leadership conditions. They rarely make it onto the slide because the crime already has a chair in the meeting.

I included them anyway.

Bad leadership is a data crime. It simply sends the invoice later.

Read the files. If you recognize one of these characters in your program, that is not an indictment. It may be the least expensive discovery you make all quarter.

Every one of these crimes is visible early. The difference between a fix and a write-off is whether someone acts while the evidence is still fresh.

Start with Case #001: The Bad Data Bandit.

He interrupts business processes. He creates mistrust in the data, so leaders stop believing the reports. Planning moves offline, spreadsheets multiply, and teams begin making decisions outside the systems designed to support them.

Once trust disappears, the business builds its own version of the truth.

He is already inside.