---
title: "Before You Automate a Process, Make Sure the Information Is Telling the Truth"
canonical: https://dxdev.com/blog/2026-06-27_before-automation-make-sure-information-is-true/
datePublished: 2026-06-27
---
A complaint arrives that looks simple: something is missing, a person cannot get access, or a page is not showing what it should. The instinct is to fix the visible problem quickly.

That is reasonable. It is also how a small mistake can turn into a larger one.

In one system, a first diagnostic flagged several records as wrong. The obvious next step was a bulk cleanup. A closer look showed that most were valid records in an unusual but intentional state. Only a smaller set needed a correction.

If the first result had been treated as the answer, the cleanup could have changed perfectly valid content.

Someone reports missing access or a broken page, and the quickest-looking fix would change records before anyone has checked whether the unusual case is actually an error.

## The real job is to separate unusual from wrong

Most teams already have plenty of information. Spreadsheets, forms, customer records, task lists, and reports can all tell a story. The problem is that a surprising value is not always a bad value.

An empty field might mean a record is incomplete. It might also mean the field does not apply. A person without access might be missing an email address. Or the system might be using the right address for the wrong person. A report might look inconsistent because data is damaged. It might also be showing two legitimate parts of the process that were never meant to match.

The difference matters because automation is fast. If you tell an automated process to clean up everything that looks unusual, it can make a confident mistake much faster than a person can.

## Where AI can help

AI is useful here when it helps a person ask better questions before acting. It can compare records, group similar cases, describe inconsistencies in plain language, and prepare a short list of items worth checking.

The useful pattern is not, "AI found the answer." It is, "AI helped turn a pile of confusing information into a small set of decisions a person can actually review."

A good diagnostic should make three things clear:

1. What looks unusual.
2. What the system believes that unusual result means.
3. What will change if someone approves a fix.

That third part is important. In the example, a preview made the difference visible before anything changed. It showed what would be preserved and what would be corrected. The preview did not just make the process safer. It made the decision easier to trust.

## A practical question to ask about your own work

Think about a process that currently depends on someone scrolling through a spreadsheet, searching an inbox, or checking several systems before they can decide what is wrong.

The first AI-assisted improvement may not be an automatic fix. It may be a diagnostic that answers: **what is actually different here, and what would happen if we changed it?**

That kind of tool removes guesswork without pretending that judgment is unnecessary. It gives people a clearer starting point, reduces the chance of a rushed cleanup, and makes the work easier to hand off.


## The practical check

Build a small read-only diagnostic that shows the shape of the case before automating a correction. Distinguish a real error from an unusual but valid record.

## Where AI fits

AI can organize diagnostic evidence and prepare a read-only explanation of the possible cases. It should not make the correction or treat a pattern as proof.

## The human decision

People inspect the evidence, decide whether a correction is justified, and approve any consequential action.
## The lesson

Before automating a correction, build a way to see the shape of the problem. A process becomes safer when it can distinguish a real error from an unusual but valid case.

If you want the implementation story behind this lesson, the Build Log explains how a diagnostic preview prevented a destructive cleanup.