01 · THE MONITOR'S SEAT
Picture the person who watches the machine that never fails. A pilot on a nine-hour cruise that the autopilot flies without a flutter. An operator whose plant runs itself for months. They are paid to be ready, to take over the instant something breaks. And for that exact reason, they almost never practise. The takeover, when it finally comes, demands more skill than the routine ever did, and it arrives on the one day the skill has quietly gone. The trap is not that automation makes people lazy. It is that it makes them rusty, invisibly, right up to the moment they are needed most.
02 · THE REPS STOP, THE SKILL THINS
That rust has a name. Deskilling is the loss of unaided skill after automation takes over work a person used to practise. The knowledge that catches an error, the feel for when a number is wrong, the pattern in the noise, none of it has to vanish in a dramatic moment. It can thin quietly from disuse. Long stretches of reliable automation create the timing problem: they remove routine practice before the rare event that demands a manual takeover. The point is not that every automated system produces the same decay curve. It is that a check can keep its name while the human capability behind it changes.
03 · THE IRONIES OF AUTOMATION
Lisanne Bainbridge described the design problem in nineteen eighty-three. Ironies of Automation ran for five pages in Automatica. Her argument was not that automation always fails. It was that designers automate the tasks they can formalize, then leave people to monitor the system and handle the difficult events the designers could not automate. Those residual tasks can require manual skill and rapid diagnosis, even though ordinary operation gives the person little opportunity to practise either one. Better machine control does not remove the human role. It can concentrate that role in the hardest moments.
04 · THE FINAL IRONY
That is the irony worth holding still. Automation can leave the hardest takeover to the person getting the least practice. Reliability and readiness can pull in opposite directions. A system may need human judgment only rarely, yet still need it immediately and at a high level when an abnormal event arrives. The operating question is therefore not just how often automation succeeds. It is what practice remains for the person expected to recover it when it does not.
05 · SIX POINTS, IN EXPERTS
A twenty twenty-five study put numbers on the concern in colonoscopy. Researchers examined one thousand four hundred and forty-three procedures conducted without AI at four Polish centres. They compared the three months before AI detection tools were introduced with the three months after. In those non-AI procedures, the adenoma detection rate fell from twenty-eight point four percent to twenty-two point four: an absolute difference of six percentage points. The study was retrospective and observational, so it does not prove that AI caused the decline. It does show a measurable change after AI entered the workflow, large enough to make retained unaided performance an operating question rather than an assumption.
06 · CANNOT BE OVERCOME WITH SIMPLE PRACTICE
A reminder to stay alert is not enough. In twenty ten, Raja Parasuraman and Dietrich Manzey reviewed evidence on complacency and bias in human use of automation. They found automation complacency under competing task load in both novice and expert participants, and wrote that it cannot be overcome with simple practice. They placed attention at the centre of the problem. That finding does not prescribe one universal remedy. It does rule out treating vigilance as a stable trait that a briefing can simply switch back on. If retained performance matters, the workflow needs a way to test it.
07 · Advertisement · Bubble AI App Builder
Some ideas do not need another document before they become testable. With Bubble AI, you describe the app you want, and Bubble creates a working starting point: interface, data, and logic you can inspect. From there, you refine visually, connect AI models and services, and turn the first version into something real enough to use.
08 · REPS AND DRILLS, NOT REMINDERS
The practical response is to replace reassurance with evidence. Schedule an unaided comparison: switch the aid off for a controlled sample, score the result, then compare it with the assisted baseline. Use a seeded error to test whether the monitoring layer still detects the failure it is meant to catch. Where the consequence warrants it, add an independent reviewer who does not inherit the same routine. These are proposed controls, not guaranteed cures, and their cadence should follow the risk. Their advantage is testability. Each produces a record of retained performance instead of an instruction to stay sharp.
09 · THE CHECK DECAYS INTO RITUAL
Without them, the verification layer rots. A firm builds checks: a second approver, a review step, all of it depending on a human who can still tell right from wrong. Deskilling is the slow leak underneath. The check still runs, on schedule, looking exactly as it did on day one. But the judgment it draws on has thinned to nothing, and it decays into ritual: a stamp, not a scrutiny. Metacognitive demand is the load the check puts on you today. Deskilling is what that load does to you over months. The reverse centaur does not arrive in a coup. It arrives one un-practised rep at a time.
10 · WHO STILL KNOWS HOW
So the question to keep asking is not whether the check exists. It is whether anyone behind it still knows how. Who on this team could catch the machine's error today, unaided, cold? When did they last try? A check is only as real as the skill standing behind it, and that skill leaves quietly, on the good days, while everyone believes it is still there. The load in the moment is one thing. What the load does across months is another. Watch the second one.