Why does every empty tray pocket still need me?

ElliotBaker0509 · 23 Sept 2025, 22:15 UTC

Closed
EL
ElliotBaker0509
I handed over our FR10 housing-transfer job feeling quite pleased with myself. Saved job, labelled trays, a start sheet that even I could follow before coffee. Then an empty pocket came along and the operator called me. Next interruption, same thing. I realised the sheet stops being helpful at exactly the moment you need help. I don't think they need another demonstration of a perfect tray. I'm less sure what a decent recovery handover should look like without making them memorise everything in my head.

14 replies

LO
LouisBell0659
Replying to ElliotBaker0509

What does the operator see at the empty pocket, rather than what you know the program is doing?

19 points
HA
HanaCarter0970
Replying to ElliotBaker0509

On our fleet handover the useful exercise was asking someone to explain why they had stopped. Much better than praising them for reaching the end of a checklist.

5 points
IM
ImranChan1088
Replying to HanaCarter0970

Hana, yes, but don't turn it into an exam where the learner has to guess the tutor's favourite answer; I would start by admitting the screen or instructions might be rubbish.

9 points
EL
ElliotBaker0509
Replying to LouisBell0659

Louis, it says waiting at source. No pocket shown. Imran, guilty on the screen: I know which step it means because I wrote it. The operators have been telling me that in rather polite ways.

17 points
HA
HanaCarter0970
Replying to ImranChan1088

Imran, I meant learning from their explanation, not marking it. One operator spotted that our instructions used a different name from the display. That was our mistake.

17 points
FA
FarahChan1113
Replying to ElliotBaker0509

I'd start with that empty-pocket example and an offline screenshot, Elliot, because you can find out what information is missing without interrupting another production run.

21 points
LO
LouisBell0659
Replying to ElliotBaker0509

And who is authorised to decide whether that pocket is skipped or the tray needs checking?

-2 points
IM
ImranChan1088
Replying to LouisBell0659

Louis has the awkward bit there, a clearer screen still won't decide what an operator is allowed to do when the physical tray and the saved progress disagree.

9 points
EL
ElliotBaker0509
Replying to FarahChan1113

Thanks Farah, the screenshot exercise was useful. They wanted the tray and pocket identity, but also wanted to know whether waiting meant safe to leave the job unattended. I hadn't expected that question. We need clearer status wording as well as the recovery decisions; I've brought the cell owner into it.

4 points
FA
FarahChan1113
Replying to ElliotBaker0509

That's worth keeping in their words for the review; waiting can sound quite harmless when the system is actually asking for somebody's attention.

17 points
HA
HanaCarter0970
Replying to ElliotBaker0509

We also had an operator who understood the fault but did not know who covered it on the late shift. The contact route belongs beside the recovery decision.

16 points
LO
LouisBell0659
Replying to HanaCarter0970

Hana, did you name a person or a role, because a name on an old sheet can be another dead end?

17 points
HA
HanaCarter0970
Replying to LouisBell0659

Role, with the current shift contact shown separately. Naming only the original programmer was what we were trying to get away from.

14 points
IM
ImranChan1088
Replying to ElliotBaker0509

I'd like to hear how the second walkthrough goes, Elliot; the first one has already found more than another immaculate tray demonstration would have.

7 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .