All laws

§ 102Cognition

Automation Bias

People working with an automated aid tend to let it stand in for their own checking: they miss what it fails to flag and follow it when it is wrong.

Linda J. Skitka

Keep in mind

Answer for the outcome, not for having followed the tool

What to do

Wherever an automated aid feeds a decision (generated code, scanner results, an alert that says all clear), name a person who answers for the outcome, not for having followed the tool. On high-stakes paths such as security, data migrations and production changes, have the reviewer check against the requirement, not against the tool's own output, and keep a record of what the aid missed. Do not re-derive by hand what the tool has shown it does better; spot-check low-stakes output instead.

Why it happens

Checking costs attention, and an aid that is usually right makes each check feel wasted, so its output quietly replaces the search a person would otherwise do. Parasuraman and Manzey's review describes two kinds of error: "Automation bias results in making both omission and commission errors when decision aids are imperfect." It is not a beginner's mistake: "Automation bias occurs in both naive and expert participants, cannot be prevented by training or instructions, and can affect decision making in individuals as well as in teams." In a user study by Perry et al., participants with an AI code assistant wrote significantly less secure code than those without one, and were more likely to believe their code was secure.

In practice

On March 23, 2018, a Tesla Model X operating with Traffic-Aware Cruise Control and Autosteer moved into a gore area on US-101 in Mountain View, California, and struck a damaged crash attenuator; the driver died. The NTSB's probable cause included the Autopilot steering the SUV into the gore area due to system limitations, and the driver's lack of response due to distraction "likely from a cell phone game application and overreliance on the Autopilot partial driving automation system."

Read the account

When it stops applying

Algorithm Aversion: the opposite error is common too: Dietvorst, Simmons and Massey found that "people more quickly lose confidence in algorithmic than human forecasters after seeing them make the same mistake", and so drop an aid that still beats them.

Source

Kathleen L. Mosier, Linda J. Skitka, Susan Heers & Mark Burdick, Automation Bias: Decision Making and Performance in High-Tech Cockpits (International Journal of Aviation Psychology, 1998) and Linda J. Skitka, Kathleen L. Mosier & Mark Burdick, Does automation bias decision-making? (International Journal of Human-Computer Studies, 1999) — early empirical studies of the bias; Raja Parasuraman & Dietrich H. Manzey, Complacency and Bias in Human Use of Automation: An Attentional Integration (Human Factors, 2010) — the review quoted above; Neil Perry, Megha Srivastava, Deepak Kumar & Dan Boneh, Do Users Write More Insecure Code with AI Assistants? (CCS, 2023) — the code assistant study; Berkeley J. Dietvorst, Joseph P. Simmons & Cade Massey, Algorithm Aversion: People Erroneously Avoid Algorithms After Seeing Them Err (Journal of Experimental Psychology: General, 2015) — the counter.

Read the source

Portrait: Michael Schacht, CC BY-SA 4.0 · Wikimedia Commons

Cite this

Hammurabi, § 102, “Automation Bias.” https://kanywst.github.io/hammurabi/laws/automation-bias/

BibTeX
@misc{hammurabi-automation-bias,
  title  = {Automation Bias},
  author = {{Hammurabi contributors}},
  note   = {Hammurabi, § 102},
  url    = {https://kanywst.github.io/hammurabi/laws/automation-bias/}
}

Text under CC BY-SA 4.0: credit Hammurabi and link the article.

Read in a column

Related laws

Suggest a correction on GitHub