Automation complacency is reduced monitoring of an automated system because it has been reliable. Laziness has nothing to do with it, and neither does character. It is an entirely rational allocation of attention that becomes dangerous precisely when the system is good, because the better it performs the less reason anyone has to watch it, and the rarer and stranger its failures become.
Definition#
Automation complacency: a reduction in the frequency and depth with which a person monitors an automated system, arising from a history of reliable performance, and resulting in slower detection of the failures that do occur.
How it differs from automation bias#
They are routinely used interchangeably and they are not the same thing.
Automation bias is about the weight given to output that has been seen: accepting a recommendation that should have been questioned. Automation complacency is about attention: not looking closely enough, or often enough, to have an opinion at all.
The practical difference matters. Bias is addressed by changing how a decision is made. Complacency is addressed by changing workload, sampling and interface design, because you cannot instruct someone to pay more attention to something that has been correct four hundred times running.
What the 2010 review established#
Parasuraman and Manzey's 2010 review of two decades of human-factors research found complacency and bias appearing in experts as well as novices, resistant to training, and worsening under workload. That last point is the operational one: complacency is a function of how much else the person is doing rather than a stable trait.
Parasuraman and Riley's earlier framework separated four failure modes, use, misuse, disuse and abuse, and located complacency within misuse. Their fourth category is the one organisations skip: abuse, meaning automating without regard for the human consequences, which places the failure with the deploying organisation rather than the operator.
The uncomfortable finding is Dzindolet's. Explaining how an automated aid can fail increased reliance on it. Awareness training is a weak control and can move behaviour in the wrong direction.
The reliability paradox#
This is what makes complacency structurally different from most safety problems. An unreliable system keeps people alert. A highly reliable one produces exactly the conditions in which its rare failures are least likely to be caught, and those failures tend to be the unusual cases, arriving without warning, in circumstances nobody has practised.
So improving the system does not solve the problem. It moves it, concentrating the risk into fewer, stranger, less-expected events. Any organisation whose confidence rests on "it has been accurate for months" has described the mechanism rather than escaped it.
Where this literature comes from#
Nearly all of this literature comes from process control, aviation and clinical decision support, where the human is watching a system perform a bounded task with observable outcomes. Generative AI is a different shape: outputs are open-ended, errors are frequently unverifiable in the moment, and there is no alarm. Whether the countermeasures developed in those settings transfer is plausible and untested.
Why "a human reviews it" degrades#
Complacency is the reason "we have a human reviewing it" degrades over time without anyone changing the process. The control is written once and then erodes as reliability builds confidence and workload rises. Nothing is announced. Nobody decides. That is drift in its most measurable form.
The countermeasures that work are structural rather than motivational: sample deliberately rather than review everything nominally, put time in the plan for the checking, vary what gets checked so it cannot be anticipated, and count the overrides. Zero overrides in a quarter is the clearest available signal that complacency has set in.
Related SuperSkills research#
On the sibling concept, automation bias. On the opposite failure, algorithm aversion. On why review positions fail, human in the loop is not a safeguard. On the rule, when should I override AI. On measurement, how to measure AI adoption properly.
Key sources
- Parasuraman, R. and Manzey, D. H. (2010). Complacency and Bias in Human Use of Automation. Human Factors, 52(3).
- Parasuraman, R. and Riley, V. (1997). Humans and Automation: Use, Misuse, Disuse, Abuse. Human Factors, 39(2).
- Dzindolet, M. T. et al. (2003). The role of trust in automation reliance. IJHCS, 58(6).
- Bainbridge, L. (1983). Ironies of Automation. Automatica, 19(6).
About this definition#
Automation complacency is an established term from human factors research and is not a SuperSkills coinage. Rahim Hirji is the author of SuperSkills (Kogan Page, 2026).
About this research#
Written by Rahim Hirji, author of SuperSkills (Kogan Page, 2026), keynote speaker on AI and human capability, and founder of The SuperSkills Intelligence Company.
Cite this
Hirji, R. (2026). What is automation complacency? The SuperSkills Intelligence Company. Last reviewed 26 August 2026. thesuperskills.com/research/what-is-automation-complacency