HenryBarnes0525 · 23 Mar 2025, 22:44 UTC
Sit with the operators and list the actual interruption states first; a recovery sheet based on what you remember designing can miss what they really encounter.
16 pointsThey listed an occupied destination pocket too. I'd only thought about missing source parts. That's already one reason to stop writing this alone.
6 pointsExactly, and somebody has to own the decision when the physical part location and the saved job position disagree; don't bury that under a generic restart arrow.
24 pointsWe're adding visible symptoms, the approved response and escalation contact per state. Ambiguous part location goes to the designated lead. Need controls to approve the recovery paths before training.
13 pointsLet an operator explain the draft back using the screen they actually see. I cannot judge your recovery logic, but unfamiliar status names can make a correct sheet unusable
11 pointsDid a desk walkthrough with two operators. They spotted three labels that don't match the display. Fixed those; practical recovery training is still waiting for the approved procedure.
12 pointsGive the escalation contact a backup as well; otherwise you've replaced 'call Henry' with one different person who will eventually take a day off.
23 pointsThis discussion is closed to new replies after six months without activity. Last activity: .