Irony of Automation
Updated 2026-08-04
INTRODUCTION
English translation pending.
CORE DEFINITION
The Irony of Automation, described by Lisanne Bainbridge, observes that automating routine work does not remove human responsibility but relocates it. As systems take over normal operation, people become passive monitors, yet human intervention is needed only in the rare edge cases that automation cannot handle. At that moment the operator has lost the practice that once kept the skill sharp. The result is a paradox: greater automation raises the competence required for takeover while steadily eroding the conditions that produce it.
SCAFFOLDING EFFECT
Reduce cognitive load
- Fragility Check: Ask what happens when the automated layer fails at the moment people are least practiced. - Manual Mode Design: Keep a genuinely practiced manual path rather than a theoretical one. - Skill Budget: Treat operator competence as a resource that decays without use.
Anchor fast decisions
Automation absorbs the frequent routine cases that used to train operators. What remains for humans is the rare and hardest subset, so practice hours fall while the difficulty of intervention rises. Under normal conditions vigilance also decays, because long stretches without events reduce alertness and situational awareness. When the rare failure arrives, the operator must diagnose an unfamiliar situation with degraded skill and degraded attention, which makes the resulting error larger than it would have been without automation.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Ironies_of_Automationverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS