Much of quality control is based on patterns. We assume we know what “normal” looks like, and we treat deviations from that pattern as possible errors. This applies in many areas: routines in a workplace, data entry formats, how a report usually looks, or typical outputs from a language model. As long as most of what we see is correct, this works reasonably well. Deviations are useful signals.

The problem starts when the error rate gets too high. When mistakes are no longer rare, they stop standing out as deviations. The pattern itself becomes polluted by errors. If you keep relying on “difference from the pattern” as your signal, the whole control system begins to fail. At some point, seeing an anomaly no longer reliably means “something is wrong.”

Once errors are common, something counterintuitive happens: correct behavior starts to look like the deviation. A correct entry in a dataset where most values are wrong looks suspicious. A person who follows the proper procedure in a team that has normalized shortcuts looks like they are breaking the routine. A language model output that is actually correct can appear “off” compared to the wrong but consistent answers everyone has gotten used to. What is right becomes the exception.

At the same time, recurring mistakes can start to look like they follow the pattern. If the same error happens often enough, it stops being treated as an error and becomes “how we do things.” The wrong value, the incorrect process, or the misleading answer becomes familiar. Instead of flagging it, people defend it: “That’s how the system works,” “We’ve always done it this way.” Errors are then perceived as normal.

When this happens, pattern-based quality control doesn’t just weaken; it can invert. The logic quietly shifts from “pattern ≈ correct, deviation ≈ error” to “pattern (including errors) = normal, deviation (often correct) = suspicious.” The mechanism that was supposed to catch mistakes now protects them and pushes back on corrections. The system starts treating the right thing as the problem and the wrong thing as the standard.

To avoid this, you need something more solid than “what we usually see.” That can mean checking samples against clear criteria instead of just visual similarity, comparing current routines to documented requirements, or using trusted reference data or test cases. It also means paying attention when people notice that the same “small” error appears everywhere, or when someone doing the right thing keeps being told they are doing it “wrong” simply because it doesn’t fit the current pattern.

The core point is simple: when error rates get too high, you can no longer trust patterns alone. If you keep using deviations from a flawed pattern as your main signal, you risk flipping reality: errors look normal, and correctness looks like the mistake.