Trigpoint
Collections › Human-Automation Interaction › Use, misuse, disuse, abuse
Over-reliance and refusal to use have independent causes.

Use, misuse, disuse, abuse

use, misuse, disuse, abuse · Parasuraman & Riley (1997)
Bibliography checked ✓ Lab case ✓ Human-automation interaction · trust and reliance Tell the editor privately ▸
↓ Lab cases on this page (1)
In three sentences The relationship between people and automation splits into four categories: appropriate use, and three ways it goes wrong: misuse (over-reliance), disuse (distrusted and left idle), and abuse (pushed through on the design side with no regard for human factors). Each of the three failure modes has its own causes and they feed each other. The most common managerial illusion is treating misuse and disuse as two ends of one dial.

↳ Seen a counter-example?

The reliance-calibration quadrants Parasuraman & Riley (1997) Trust High Low Misuse overtrust: relied on even when broken Appropriate use trust tracks reliability Appropriate rejection the unreliable earns no reliance Disuse undertrust: often fed by false alarms Low High True system reliability Abuse: design-side, off this plane, yet it creates the mismatches on it Redrawn sketch of the framework logic: misuse and disuse have independent causes, not two ends of one knob. Figure: trigpoint.pub
Figure 1 · The reliance calibration quadrants: trust against actual reliability, with two directions of mismatch. Misuse (too much trust) and disuse (too little) have independent causes and are not two ends of one dial. Abuse is a design-side dimension that does not sit on this plane but produces the mismatches on it. View full size ▸

1. What happened

Some people lean on automation too hard and others will not use it at all; the two are often treated as two directions of one problem. In 1997 Parasuraman and Riley rewrote "automation failure" from an argument about whether humans or machines are more reliable into a question of whether reliance is appropriate, and set out the four terms[1]Parasuraman, R., & Riley, V. (1997). Humans and Automation: Use, Misuse, Disuse, Abuse. Human Factors, 39(2), 230–253. Bibliographic details checked against the official record. The summary of the definitions of the four terms follows secondary accounts that agree with one another.. Misuse comes from trust above actual reliability: monitoring slackens and output is followed uncritically. Disuse comes from trust below actual reliability, most often driven by an alarm with too high a false alarm rate, which in turn usually traces back to a design that never worked out the base rate of the event being detected.

Abuse turns the camera back on the design and management side: pushing automation through without regard for its human consequences is the upstream source of the first two. The least intuitive point: driving the false alarm rate down to cure disuse can push misuse up. The two problems have independent causes and do not share a dial.

Attribution where due: The concept and the naming of the four-term taxonomy come from the same place, Parasuraman and Riley (1997). This page found no earlier coiner to separate out.

2. Why this matters to you

When an automated alert in a workflow starts getting skipped, the first instinct is to blame the person. The quadrant reading runs the other way. Check the alarm's false alarm rate and the base rate first, which is a design question. Then check whether reliance is calibrated to actual reliability, which is a relationship question. The person's discipline comes last. And there is a question that usually gets skipped entirely: should this have been automated at all? Ask the four separately and the fixes stop fighting each other.

Boundary: the four terms are a taxonomy of mismatch, not a maturity scale; misuse and disuse have independent causes and can coexist; the verbatim definitions have not been checked against the primary source.

↳ Is your case inside this boundary or outside it?

Verification layer · Members
The guided layer of this node is open to all readers.
Verification details and failure boundaries are for members.

Lab cases One first-hand case from our studio

Trigpoint PassField record · same incident, another lens

False alarm P0, second lesson: before you suppress false alarms, work out whether you are raising blind trust

One false alarm incident walked through the four quadrants again: false alarms feed disuse, and once the correction goes too far it turns round and feeds misuse. The two problems do not share one dial.

Trigpoint Pass content · same incident as the open preview case on Vigilance decrement

Read the member edition ▸

Full access to the lab cases. Trigpoint Pass ▸

References

How to read the source notes “Bibliographic details checked” means author, year, title and venue were confirmed. It does not mean the source's claims were checked. “Follows secondary accounts” means the claim rests on sources that report it, not on the original document. Definitions as of 2026-09-20.

  1. [1] Parasuraman, R., & Riley, V. (1997). Humans and Automation: Use, Misuse, Disuse, Abuse. Human Factors: The Journal of the Human Factors and Ergonomics Society, 39(2), 230–253. https://doi.org/10.1518/001872097778543886 ↩

↳ Is a citation wrong?

Tell the editor privately: a correction, a counter-example or where it applies

An editor reviews submissions once a week. Once a note is handled, its summary and response are listed on the discussion and response record; nothing is published before then. No sign-up is needed, and the nickname may be left blank.

What are you submitting?
Set a public name to be credited by name ▸
Submit anonymously, without signing in

Signing in lets you follow the status on your page. What you have written is kept.

You are signed in: this note is linked to your account, visible only to you and the editor, so you can follow its status on your page. The text is never published. Full privacy policy ▸

Submit anonymously instead, not linked to your account ▸

No email is collected. Your original text and nickname are read only by the editor and are never published; the discussion and response record carries only a summary the editor writes. The human check is provided by Cloudflare Turnstile. To limit abuse, the system keeps a hash of your IP address, not the address itself. Your original text is stored with our cloud provider and can be deleted on request. Full privacy policy ▸

Response record ▸