Test an automation before you trust it
Run it on last month’s real cases and count what it got wrong.
Judgment & risk
Why AI can be unfair, and the checks that catch it before a customer does.
5 min readPlain English
In one sentence
AI learns from human-made data, so it can repeat that data’s stereotypes and blind spots; the fix is to test for it and keep people in charge of decisions about people.
Think of it like…
Picture a new hire who learned the job only from decades of old office files. They’d pick up plenty of useful know-how, and the old habits too, like assuming the manager is a man. Nobody told them to be unfair; the files did.
Bias can creep in at three points. You can catch it at a fourth.
Providers work to reduce bias, but it isn’t solved, so the last check is yours.
Good at
Bad at
A job ad at a design studio. AI flags wording that might put some applicants off. The owner decides what to change.
Marketing images at a bakery. Image tools can default to a narrow idea of who your “customers” are. Describe the range of people who actually shop with you, and check before posting.
Customer replies at an online shop. The same complaint, run with two different customer names, should get the same tone and the same offer.
Myth vs reality
Myth: “A computer can’t be biased: it’s just math.”
Reality: The math learns from human data, so it can repeat human patterns, unfair ones included, at scale and in a confident tone. Treat its defaults as a starting point, not a neutral one.
What’s a quick, practical check for bias in an AI-drafted customer reply?
Run it on last month’s real cases and count what it got wrong.
Draft replies from your own answer bank. Nothing goes out unreviewed.
A quick way to decide how much checking an answer needs.