The ironies of automation
When a task is automated, the human is left with the parts the automation cannot do, which are the hardest. The skills needed to intervene when it fails decay, because nobody practises them any more. And the operator ends up monitoring a system they understand less and less.
Evidence grade: practice A widely adopted practitioner model with clear provenance.
Use it when
Reasoning about what AI assistance does to an engineering organisation's understanding of its own systems; the case for reviewing for understanding and for building capability.
Where it stops working
It is an analytical essay about industrial control and does not study software, so it applies here by analogy.
Where the standard uses it
- TJ-5AI-assisted engineeringAdoption, governance, capability-building, and risk.
Sources
- Lisanne Bainbridge. Ironies of Automation. Automatica, 19(6), 775–779, 1983. In the bibliography
Used alongside it
- AI-assisted developer productivity contested
- Proportionate AI governance practice
- Security of AI-generated code research
- Staged bets and checkpoints practice
Cite this model
Chicago, BibTeX and licence →Engineering Management Academy. (2026). The ironies of automation. In Engineering Management Academy Body of Knowledge (Version 3.1, TEC.ironies-of-automation). https://www.engineeringmanagement.academy/body-of-knowledge/techniques/ironies-of-automation