Why recovery confirmations get skipped on a busy shift

In almost every Backup Feature Usage Review we have run from the Klang office, at least one confirmation dialog is dismissed without being read. Managers hear that sentence and think of negligence. Operators hear it and think of a queue.

The reasons we actually write down are narrower. The dialog uses English legal phrasing on a screen the rest of the shift reads in Bahasa Malaysia. The same dialog appeared twice in a row after a timeout. The operator has been told, informally, that pressing through is how the last restore finished before a customer cutoff. None of those reasons appear in the recovery manual.

When we note a skipped confirmation, we add a short clause: skipped because the wording duplicated the previous screen; skipped because the shift lead nodded; skipped because the clock on the wall was past the agreed restore window. That clause is what makes the briefing useful. You can change a sentence on a dialog more easily than you can change a habit, but only if you know which sentence is in the way.

We do not ask operators to perform more slowly for our benefit. If a confirmation is skipped, we write it as it happened. The mild discomfort in the room afterwards is part of the work. It is better than a report that pretends every dialog was read.

Back to field notes · Request a usage review