DanLoop · 21 Dec 2025, 05:40 UTC
Write down what you ask the operator when they call. That would be my starting point, not a prettier start button. If you need five facts to decide, the handover needs to help them preserve those five facts.
19 pointsStart with one real interruption, then. A list of imagined possibilities tends to miss the ordinary confusing bit that made someone call you.
19 pointsFor the last call I needed the tray identity, last confirmed pocket and whether a sleeve remained held; the screen displayed only the next planned pocket, which was not helpful.
22 pointsOur screen once scattered those details over several pages. People read one page to maintenance and forgot the rest. Can yours show the interrupted transfer together?
16 pointsThat information helps explain the state. It does not assign permission to move anything. Have controls and the responsible cell people define the permitted recovery decisions, including when the operator must stop and escalate.
15 pointsLuis, yes, and name the role that answers. 'Ask Dan' works brilliantly until Dan is eating lunch, on leave, or has escaped to a meeting where the phone is off.
16 pointsDon't replace Dan with 'authorised person' and leave it there. The shift needs to know which role is available and how to contact it.
16 pointsEmma, the proposed screen groups the transfer details; Luis and Alex, controls and the shift lead are defining the decisions and escalation role together, with the sheet still marked as draft.
24 pointsGive the draft to somebody who wasn't in that discussion. Ask what they'd tell the shift lead from the screen. You can learn plenty without asking them to perform the recovery.
20 pointsDid the read-through happen? Interested in what they couldn't find.
1 pointsDan, include the state after a reviewed recovery is recorded and the application closes again. Your handover needs to agree with the retained-state design, not teach a second version of it.
22 pointsThe reader could identify the tray but read 'next pocket' as a confirmed placement, Emma; Luis, the post-review restart case is included with controls, not treated as a separate operator workaround.
20 pointsThat is a useful misunderstanding to catch. Show planned and confirmed in distinct terms, and retain an explicit unknown where neither can be established. More confident wording would make this worse.
5 pointsDid they know who to call, at least? One less mystery would be nice.
11 pointsYes, the shift lead and escalation contact were clear, Priya; the planned-versus-confirmed wording is being revised, so I am not calling the read-through passed.
6 pointsKeep that mistaken reading in the next check. Different reader, same example.
21 pointsThis discussion is closed to new replies after six months without activity. Last activity: .