The Evaluating Self

80Complacency and Bias in Human Use of Automation

Raja Parasuraman and Dietrich H. Manzey, Human Factors 52(3), pp. 381–410, 2010

Complacency and bias, 2010 — the review in five moves Complacencydefined What doesnot fix it Automationbias Attention atthe centre The modeland its loops Monitoring below anormative rate, and afailure missed. Needscompeting tasks. Central display, lowfailure rates, skill,practice and forcedfixation: all fail. Decision aids yieldomission errors fromalerts, commissionerrors from advice. Both are the samereallocation ofattention away fromthe raw evidence. Potential, bias,consequence. Oneloop raises it, onelowers it. Complacency is an active reallocation of attention, not a passive state the operator sinks into. Reliable automation rarely punishes inattention, so the absence of consequences deepens it.
Figure 80.0 — The review's five moves. Two literatures, each with its own name for the effect, joined at the point where attention is allocated.

Parasuraman and Manzey take two terms that grew up in separate literatures and argue that they name the same thing. Complacency came out of aviation, where investigators used it for crews who stopped checking, and it was studied in supervisory control, where an operator watches an automated process while working by hand on something else. Automation bias came out of decision research, where a person is handed an aid that names a fault and recommends a response, and it was studied as a heuristic, a cousin of confirmation bias. Both literatures kept finding the same things: the effect appears in students and in experienced pilots alike, it survives practice, it grows as the machine becomes more reliable, and instructions to cross-check do not remove it. What joins them, the review argues, is attention. Complacency is not a state the operator sinks into; it is an active reallocation of attention away from the automated task and towards the manual ones. The same reallocation, applied to the raw readings that would confirm or refute a decision aid, produces the errors that had been called bias. The paper closes with a model in which a disposition, a task context and a machine's reliability combine into an attentional strategy that two feedback loops push in opposite directions.

Automation complacency

The word entered the literature as a coding item. The Aviation Safety Reporting System, set up in 1976, defined complacency for its incident reports as non-vigilance based on an unjustified assumption of satisfactory system state. Wiener discussed that definition in 1981 alongside others, including complacency as "a low index of suspicion", and argued that the concept would earn its place in safety work only once experiments had given it a mechanism. Three decades later no consensus definition exists, and Parasuraman and Manzey assemble a working one from three features common to the accident analyses and the experiments: an operator is monitoring an automated system; the frequency of that monitoring falls below some optimal value; and the shortfall has an observable consequence, usually a missed malfunction.

The accident record supplied the motive. In a survey of 100 highly experienced airline captains, more than half named complacency a leading factor in accidents, and a 1999 analysis of automated-aircraft accidents put it among the top five factors. Outside aviation the standing case is the grounding of the cruise ship Royal Majesty off Nantucket: an antenna cable frayed, the satellite signal was lost, the radar plotting aid silently reverted to dead reckoning without correcting for tide and wind, and the ship was carried onto a sand bank. Investigators cited overreliance on the aid and insufficient monitoring of the other navigational sources. Dekker and Hollnagel called complacency and situation awareness folk models without scientific standing; the reply is the experiments, which the accident reports had only motivated.

What the multi-task studies found

The first serious attempt to produce the effect in a laboratory failed. Thackray and Touchstone gave participants a simple conflict-detection task with an aid that failed twice in two hours, and found them as accurate with the aid as without it. Parasuraman and Manzey blame the emptiness of the session rather than its length: the participants had nothing else to do.

Parasuraman, Molloy and Singh supplied the missing ingredient in 1993. Participants ran three tasks at once from the Multi-Attribute Task Battery: compensatory tracking and fuel management by hand, and engine monitoring supported by imperfect automation. Following Langer's notion of a premature cognitive commitment — an attitude formed on first meeting a device and confirmed every time it behaves the same way — they also varied whether the automation's reliability held constant or fluctuated. Detection of its failures averaged 82% when reliability varied and 33% when it held constant, a difference of 149%. Under single-task conditions the same malfunctions were easy, detected about 97% of the time, and participants asked only to back up the automation caught nearly all of them.

Detection of the engine malfunction, by task load and by constancy per cent detected 0 25 50 75 100 97% about 100% 82% 33% one task,done by hand one task,backing up the aid three tasks,reliability varies three tasks,reliability constant Parasuraman, Molloy and Singh, 1993, Figure 1 and accompanying text. The last two bars differ only in whether the automation's reliability held steady.
Figure 80.1 — The 1993 result. The effect lives entirely in the right-hand pair; alone with the automation, an operator watches it well.

That pattern is what makes the everyday sense of the word wrong. Complacency is not passivity. The operator is working hard, and the work is going somewhere else.

Where the operator's attention goes Manual task A Manual task B Manual task C Automated task D Attention allocation strategy Human operator Trust in the automation Attention goes where the operator must act; what remains goes to the machine's task. Sampling of the automated task is set by trust, so constant reliability drives it down.
Figure 80.2 — Attention allocation and trust, redrawn from the paper's Figure 3. Sampling of the automated task is the residue left by the manual ones, and trust sets how small that residue is.

What does not remove it

Moving the automated display from the periphery to the centre of the screen changed nothing. Cutting the failure rate to one failure in a thirty-minute session changed nothing: alone with the automation most participants caught it, under multiple tasks about half did, and fewer caught a late failure than an early one. In a driving simulator where lateral control was automated and a vehicle merged suddenly into the lane, the system did not react, half the drivers failed to brake and take over, and 14% did not respond in time to avoid the collision. Lowering reliability helped a little: detection varied inversely with reliability, but monitoring stayed worse than manual performance even at low reliability, and no floor appeared below which the cost vanished.

Expertise did not help. Pilots with about 440 hours showed the effect; general aviation pilots using a real cockpit alerting system detected fewer engine malfunctions with it than without it; experienced controllers given a conflict probe that failed once missed the conflict more often than the same conflict handled by hand. An hour of extra practice left the effect intact. Training that addresses attention rather than the task did better: variable-priority training, alternating which task gets 80% of the trainee's effort, improved multitasking and produced a trend towards less complacency.

The most instructive failure was Duley's. He superimposed the automated engine display on the manual tracking task, interleaving the elements so that neither masked the other and every fixation of the tracking task put the automated task in foveal vision too. Tracking was as good as before, and so was the complacency effect. Whatever is being withdrawn is not only the eyes. Eye movements carry part of the story: among controllers who missed the conflict there were significantly fewer fixations of the radar display under automation, and among those who caught it there were none.

Trust is the weakest joint. It is the obvious explanation for why constant reliability breeds inattention, and the direct evidence is thin: one replication reproduced the constancy effect with no accompanying rise in measured trust, another found an inverse relation between trust and monitoring only when two experiments were pooled, and Lee and See found no convincing link at all. Parasuraman and Manzey suspect the measure, and propose that what an operator does to verify a machine indexes trust better than what the operator says. Individual differences are real and poorly characterised: the one scale in use, twenty items on attitudes to everyday automated devices, predicts poor monitoring only above a threshold.

Automation bias

A decision aid does two things: it alerts, and it recommends. Each function has its own failure. Mosier and Skitka defined automation bias as using the aid's output as "a heuristic replacement for vigilant information seeking and processing", which places it among the ordinary decision heuristics, with the qualification that this one comes from a machine.

Omission errorCommission error
Which function failsthe alertthe recommendation
What the operator doesnothingwhat the aid says
Everyday casemissing the motorway exit the navigation aid failed to announceturning into a one-way street because the aid's map is out of date

Three things are held to produce it: cognitive economy, since a recommendation is cheaper than an analysis; imputed authority, since participants asked to predict how well an automated aid would do against a human helper expected the machine to be considerably better before either had done anything; and diffusion of responsibility, the slackening that occurs whenever two parties are given one job.

The evidence runs across four domains. In a simulated engine fire, an automated checklist recommended shutting down the engine that was not on fire, and 75% of pilots complied, against 25% working from a paper checklist. In a full simulator study, when a false engine fire warning appeared with no supporting reading anywhere on the flight deck, every pilot shut the engine down, though in debriefing the same pilots said that such a message alone would not justify it. Two thirds of them reported having seen a second indication supporting the warning, which had not been there: Mosier called it phantom memory. Non-pilots running a three-task simulation missed 41% of the events the automation failed to announce, against about 3% unaided, having been told the gauges were always valid. Radiologists reading mammograms fell from 46% to 21% detection on cancers the aid left unmarked, and in a command-and-control task accuracy fell from 89% unaided to 70% when the aid was wrong — worst where the aid recommended a specific action and where its overall reliability was highest.

How often the operator got it wrong, with the aid and without with the aid, in the cases where the aid was wrong without the aid wrong engine shut down critical event missed cancer missed, unmarked case wrong battlefield decision stall in icing conditions 75% 25% 41% 3% 79% 54% 30% 11% 88.9% 30% 0 25 50 75 100 per cent of cases in which the operator got it wrong In order: Mosier 1992; Skitka 1999; Alberdi 2004; Rovira 2007; Sarter and Schroeder 2001.
Figure 80.3 — How often the operator got it wrong, with the aid and without it. The aided bars count only the cases in which the aid itself was wrong.

The in-flight icing study shows the asymmetry plainly: an aid that named the icing condition, and one that also prescribed pitch, flap and power, both cut stalls when their information was right and raised stalls to 88.89% when it was wrong, against 30.00% for pilots flying on their own sense of the aircraft. Aids that recommend actions produce more commission errors than aids that only analyse information, and an aid that publishes its confidence case by case costs less when wrong.

Two interventions that ought to work do not. Neither a briefing on omission and commission errors nor an explicit prompt to verify the aid changed the error rates, in 181 non-pilots or in 48 experienced glass-cockpit pilots, and a second crew member working redundantly changed nothing. What did change them was accountability: participants who expected to justify their accuracy afterwards made fewer errors of both kinds and more use of the monitor provided for checking the aid.

Toward an integrated model

The two constructs meet first at the omission error, which is complacency under another name: the operator has leaned on the alerting function and stopped watching the environment. The commission error splits. Discounting information that contradicts the aid is a decision bias in the strict sense. Following the aid without looking for the contradiction is not a bias in weighing evidence at all; it is a failure to gather it, which is the same reallocation of attention.

Moray had pressed a sharp objection. Monitoring a machine less often than one's own tasks is rational when the machine is reliable, and misses are the price of a sound strategy; complacency can be diagnosed only against a normative sampling rate. Parasuraman and Manzey accept the demand and doubt the supply. Moray's normative rate comes from the sampling theorem, which needs the bandwidth of the signal, and the bandwidth of most real information sources cannot be computed; nor does the theorem price the cost of a head movement.

The answer came from a process-control microworld simulating a spacecraft life-support system. Bahner, Hüper and Manzey gave operators an aid that diagnosed faults and recommended responses, and mouse access to every tank level, flow rate and history graph needed to check a diagnosis. Because a complete check was enumerable, actual sampling could be set against normative sampling, and complacency measured before any failure had occurred. Every group sampled less than a complete check required; operators merely told that the aid might fail sampled less than operators who had met a few rare failures during training. In a companion experiment, 18 of 24 participants followed the first wrong diagnosis they met; four fifths of them had not checked enough to catch it, and one fifth had looked at every parameter that contradicted it.

That last fraction is what the integration turns on. In a further study, about 43% of operators missed the first wrong diagnosis; half had sampled incompletely and half had sampled everything. Those who caught the error took markedly longer over a parameter that did not fit the diagnosis than over one that did. Those who missed it showed no such increase: they had looked at the contradiction and spent nothing on it.

Three ways to follow a wrong recommendation The aid diagnoses wrongly Sampled less than the check required Sampled everything, processed none of it Saw the contradiction and set it aside 6 of the 11 who followed a wrong diagnosis 4 of 11; they recalled the values the aid implied, not the ones shown 1 of 11; aware of it and unable to say why The simulation was stopped at the error and participants were asked what they had read. Reichenbach, Onnasch and Manzey. The first two routes are attentional; the third is not.
Figure 80.4 — Three ways to follow a wrong recommendation, with the counts from the study that stopped the simulation and asked. Only one of the three is a bias in weighing evidence.

So a commission error has three sources: an overt reduction in sampling, a covert withdrawal of attention from information that was looked at, and an active discounting of a contradiction that was seen. The first two are attentional and account between them for most of the observed errors. That is the paper's central claim, and it makes complacency and automation bias two readings of one instrument.

The model

Complacency potential — a tendency to deal with a particular system less attentively — is set by that system's reliability and constancy, by the operator's history with it, and by the person. Whether the potential becomes an attentional bias depends on the task context, chiefly workload and how accountable the operator feels, and on the operator's state; fatigued operators, in one study, cross-checked an aid more carefully than alert ones. The attentional bias produces selective processing of information, whose cost is a loss of situation awareness: invisible while the automation works, and an omission or a commission error the moment it does not.

The model and its two loops System properties The person Task and state reliability and level attitudes, traits workload, fatigue Complacency potential Attentional bias in processing Loss of situation awareness Automation works no consequence Automation fails omission, commission raises complacency potential: a reliable machine rarely punishes inattention lowers it: an automation failure the operator actually meets
Figure 80.5 — The model. Note which loop is fed by the automation behaving well.

The two loops make the account dynamic rather than a list of factors. Because automation is usually reliable, inattentive operation usually has no consequence, and the absence of consequences raises complacency potential further: the positive loop, which the authors name after learned carelessness in industrial safety. A failure actually experienced runs the other way, which is why the operators who had met failures in training sampled more. The remedies follow the loops: aid the analysis rather than the choice, publish the machine's confidence case by case, raise accountability, and let operators meet failures before the failures matter.

Since 2010

The integration has held. That complacency requires competing tasks, that it survives expertise and practice, and that decision aids produce both omission and commission errors across aviation, medicine, process control and command and control are settled findings, and the attentional reading of automation bias is the standard one. The term has travelled furthest, into clinical decision support, forensic examination and algorithmic risk scoring, where it is often used without the distinction that gives it its content.

The loose joints are the ones the authors named. Trust still does not measure well: self-report scales predict monitoring poorly, and the behavioural indices the paper recommended have been adopted without displacing the questionnaires. Moray's requirement that complacency be diagnosed against a normative sampling rate remains the honest standard and the rare practice; most studies still infer it from missed failures, which is what he objected to. The reliability threshold below which an aid stops paying for itself, put at roughly 70%, has not survived as a constant, and looks instead like a function of workload and of whether the raw data are available at all.

That last qualification has grown teeth. Bahner's design depended on an operator who could enumerate and inspect every reading the aid had used. Aids built since do not always expose one, and where the evidence cannot be sampled the distinction between failing to check and being unable to check collapses, along with the normative model that gave complacency its meaning.

The diagnosis returns to where the field began. Ironies of Automation argued that the more reliable a system, the less its operator monitors and the less able that operator becomes to take over when it fails. Parasuraman and Manzey supply the measured mechanism and correct one thing about it. What the reliable machine takes is not principally skill. It is attention, which it takes quickly, from experts as readily as from novices, and in proportion to how well it has been working.

Claims drawn from this chapter · 10

An aid that hides its inputs makes under-checking impossible to measure

Saying an operator checked too little requires knowing what a full check would have been. That is knowable only where he can list and inspect every reading the aid used; where the aid does not expose them, failing to check and being unable to check cannot be told apart.

BecauseMoray's demand for a normative sampling rate is accepted rather than met, since the sampling theorem needs a bandwidth most real sources do not have, and the one design that answered it worked only because every parameter was inspectable
LimitsMost studies still infer complacency from missed failures, which is what Moray objected to, so this is the honest standard rather than the settled one. It concedes much: if no normative rate can be computed, the charge loses content in most settings.
PracticeBefore adopting a tool, ask what a complete check of one output would consist of. If you cannot write that list, oversight is not a plan.
After AIA model that answers without exposing what it drew on is the case in which the measure collapses, and the phrase used to license it — a human in the loop — names a duty nobody can specify.

An aid that recommends action produces more errors than one that reports

Aids that prescribe what to do cause more wrong actions than aids that only report what they found, and the damage is worst where the aid is most reliable. In the icing study both aids raised stalls to 88.89 per cent when wrong, against 30.00 per cent for pilots flying unaided.

Becausein a command-and-control task accuracy fell from 89 per cent unaided to 70 per cent when the aid was wrong, worst where the aid recommended a specific action and where its overall reliability was highest
LimitsBoth aids cut stalls when their information was right, so the comparison prices the failures and not the whole. The review's closing section adds that the reliability level at which an aid stops paying for itself is not a constant.
PracticeAsk the tool for the findings and reach the decision yourself. Where you cannot, make it publish how sure it is on this case, not in general.
After AIAn assistant that writes the patch rather than describing the fault is the recommending aid, in the configuration the paper found worst — high apparent reliability, a specific action proposed, no confidence attached to this answer.

Every pilot shut down the engine on a single unsupported fire warning

In a full simulator study a false engine fire warning appeared with nothing on the flight deck to support it, and every pilot shut the engine down. In debriefing the same pilots said the message alone would not justify it, and two thirds recalled a confirming indication that had never been there.

Becausethe study records what the pilots did, what they said they would do and what they remembered seeing, and the three do not agree; an automated checklist recommending shutdown of the wrong engine drew 75 per cent compliance against 25 per cent from paper
LimitsA simulator removes the cost of shutting down a good engine, and phantom memory is reconstructed at debriefing, so some of it may be the report rather than the perception.
PracticeName the second source before acting on the first, out loud or in writing. Remembering afterwards that you checked is not evidence that you did.
After AIThe reviewer who signs off a generated change and later recalls verifying it is in the same position, with less to check against: there is no second instrument, and the confirming memory comes from the fluency of the explanation.

Expertise did not protect pilots, controllers or radiologists from missing automation's errors

Experience at the job does not reduce the effect. Pilots with about 440 hours showed it, controllers given an aid that failed once missed that conflict more often than when working by hand, and radiologists' detection of cancers the aid left unmarked fell from 46 to 21 per cent.

Becausethe effect held across four professional populations and an extra hour of practice left it intact, while variable-priority training — alternating which task gets 80 per cent of the effort — produced a trend towards less complacency
LimitsPractice at the task did not help, but training aimed at how attention is divided did, so this says which practice is useless rather than that experts are beyond help.
PracticeDo not staff oversight by seniority and expect the problem to go away. To move the effect, train the allocation — protected stretches where the tool is off and the work is yours.
After AIThe comfort that senior people will catch what the model gets wrong has no support here. METR's 2025 trial found experienced developers slower with AI on their own repositories while believing themselves faster.

Half who followed the wrong diagnosis had looked at every reading

Following a wrong recommendation is usually a failure to gather the contradicting evidence, not to weigh it. About 43 per cent of operators missed the first wrong diagnosis; half had not checked enough to catch it, and half had looked at every reading and spent no extra time on the one that did not fit.

Becausethe life-support simulation made a complete check enumerable, so sampling could be measured against it, and those who caught the error lingered on the contradicting parameter while those who missed it did not
LimitsOne group of studies in one microworld, with few participants — 18 of 24 followed the first wrong diagnosis in the companion experiment. The split into reduced sampling, covert withdrawal and discounting is inferred from logs and dwell times.
PracticeDecide before you open the output which readings would have to disagree with it, and go and look at those. Debiasing how you weigh evidence addresses the smaller half of the problem.
After AIIt puts the danger in the interface rather than the reasoning. A model that shows its sources has not thereby been checked: the reviewer who opens every link and lingers on none looks identical in the audit log.

Nothing punishes inattention while the machine works, so it grows

Because automation is usually reliable, watching it less usually costs nothing, and the absence of a cost makes the operator watch less still. The loop runs the other way only when a failure is experienced: operators who met rare failures in training sampled the aid more than operators merely told it might fail.

Becausethe training contrast in the Bahner microworld is a direct test of the negative loop, and the positive one is the learned-carelessness effect carried over from industrial safety; the standing case is the *Royal Majesty* grounding
LimitsThe positive loop is borrowed rather than measured; what the studies show is the training contrast at one point in time, not a sampling rate declining over months.
PracticeArrange to meet the tool's failures early and on purpose — a known-bad case in the evaluation set, a look at last month's mistakes — because what restores checking is having been burned.
After AIReliability is now the selling point and rises between releases, so the loop is driven harder each quarter. The safety argument that the tool is right almost every time states the exact condition under which nobody catches the exception.

Operators alone caught nearly every fault and busy operators caught a third

An operator with nothing else to do watches an automated system well. In the 1993 experiment the same engine malfunctions were caught about 97 per cent of the time by people running only that task, and 33 per cent by people also flying and managing fuel by hand.

BecauseParasuraman, Molloy and Singh ran three Multi-Attribute Task Battery tasks at once, and detection averaged 82 per cent when reliability fluctuated against 33 per cent when it held constant, a difference of 149 per cent
LimitsThe first attempt to produce the effect, by Thackray and Touchstone, failed; blaming the empty session rather than the design is an interpretation. The numbers come from a laboratory battery with a fixed workload.
PracticeStop treating review as something to do alongside your own deadline. Either the checking is the whole task for that stretch, or it is not happening.
After AIThe multi-task condition was the experimental manipulation in 1993 and is now the ordinary arrangement of work: the person reviewing the model's output is also the person who owes the deliverable.

Parasuraman and Manzey found little evidence that trust explains the inattention

Trust is the obvious explanation for why a machine that behaves consistently stops being watched, and the direct evidence is thin. One replication reproduced the effect with no rise in measured trust, another found the relation only on pooling two experiments, and Lee and See found none.

Becausethe authors keep trust in their model while conceding the measurements do not carry it, and suspect the instrument: what an operator does to verify a machine indexes trust better than what he says
LimitsThis is an argument about measurement, not a demonstration that trust is irrelevant — a bad questionnaire and an absent mechanism look the same from outside. The one scale in use predicts poor monitoring only above a threshold.
PracticeAudit reliance by what you actually opened and checked last week, not by how much you say you trust the tool. The behaviour is the measure.
After AISelf-reported trust in AI is now surveyed constantly and used to justify deployments. A measure that could not predict whether an operator looked at a gauge will not predict whether anyone reads the model's output.

Putting the automated display in plain sight did not restore monitoring

What the operator withdraws is attention, not gaze. Duley laid the automated engine display over the manual tracking task, so that every look at the tracking task also fell on the automated one; tracking stayed as good as before and so did the rate of missed malfunctions.

Becausethe superimposed-display result is a direct test, moving the display from the edge of the screen to its centre likewise changed nothing, and controllers who missed a conflict made significantly fewer fixations of the radar display
LimitsThe two halves pull apart — the eye-movement data say gaze tracks detection, the superimposition study says gaze is not enough. The review's reading is that overt sampling and covert attention are separate contributors, not that looking is irrelevant.
PracticeStop counting visibility as oversight. A dashboard in front of someone, a diff on the screen: neither is evidence that anything was checked.
After AIWritten about a gauge. It now applies to every interface whose defence is that the model's reasoning was shown: the text was on the screen and in the reviewer's foveal vision, and nothing follows from that about whether it was read.

Telling operators to check the aid changed nothing; being held accountable did

Neither a briefing on how decision aids fail nor an instruction to verify the aid changed the error rates, in 181 non-pilots or 48 glass-cockpit pilots, and a redundant second crew member changed nothing. Participants who expected to justify their accuracy made fewer errors and used the checking tool more.

Becausethree interventions that ought to work were tested against a fourth in comparable tasks, and only the one that changed what the operator had to answer for moved both kinds of error
LimitsAccountability here means expecting to explain your accuracy to an experimenter, not the standing kind that also punishes; Edmondson Fearless Organization finds accountability without safety produces silence rather than checking. Buçinca's designs did change behaviour, so the pessimism is about telling, not intervening.
PracticeReplace the reminder to review carefully with a record of what the reviewer checked, which someone will read. Awareness training is the cheapest intervention and the one the evidence rules out.
After AIAlmost every current safeguard is one of the interventions that failed: a banner saying the model can make mistakes, a policy requiring human review, a second reviewer. The one that worked is the one nobody ships.

All claims · Source map