Here's something you've probably experienced π
You're scanning a packet of crisps for your meal deal, and then the self-checkout stops you. Itβs telling you what to do next: scan it again, remove the unexpected item, or wait for a member of staff.
As annoying as it is to stand there like a wet lemon while someone walks over to tap the screen, it is at least useful. A lot of software knows something failed, but leaves you to work out who can actually sort it.
This week's issue looks at what good recovery should make clear: who needs to act, who controls the blocked state and whether an override should exist at all.
Top comments (0)