Training & Alignment

Bias

Models learn from data, and data carries history: who was hired, who got credit, who was photographed. Such skews migrate into the model, where they are scaled up and given an air of objectivity. Bias does not disappear through good intentions but through measuring along the groups it affects, and through a willingness to correct results that flatter your own statistics.

An example

A speech recognition system in a call center understands standard German well and strong dialects poorly. On average the recognition rate is 94 percent, a good figure on which the system is signed off. For a portion of callers it is 71 percent, and these callers are systematically served worse. The average did not show the finding; it hid it.

A closer look

Bias arises in three places: in the data, in the evaluation during training, and in application, when a system is deployed on a group it was not built for. Usually only the first is discussed.

Why it matters

Bias is rarely intentional and almost always a question of evaluation. It becomes visible as soon as you break performance down by group instead of looking only at the mean: by region, age, language, gender, company size, depending on the use case. That is an analysis of an hour and should be part of every acceptance. For systems that decide about people, the EU AI Act demands it anyway. What matters is honesty about what follows: if a group is served worse, the question is whether the system is deployed at all, not just whether it gets better.

Commonly misunderstood

Bias can only be measured if it has been named beforehand between which groups, and from what size on, equality is expected. Without that, it stays at anecdotes.

Where this term does its work in the magazine.

3 articles use the term or take up its principle.