I taught our Universal Robots UR5e job for tray-to-fixture loading with a small aluminum housing in a small production training area. Everyone can start it, but an empty pocket or interrupted run means a call to me. I don't think this is attitude.
Our handover covered a clean run and left the awkward decisions out.
@HazelBaker0484 Have you asked operators to explain the restart instruction in their own words? You may find one sentence means several different things to the team.
@AishaBell0692 During a discussion, I asked operators to explain the restart wording and received several different interpretations. That gives us a concrete ambiguity in the handover to address.
Use the conflicting interpretations to revise the instruction into condition, permitted action and escalation criteria.
After the responsible integrator reviews it, check understanding again through an unprompted teach-back.
Because I wrote the ambiguous instruction, I'm concerned that teach-back could feel like blaming the operator. How can I frame it as a check of the handover?
@HazelBaker0484 For my own handover, I framed the discussion around locating gaps in the guide I had written. Asking where it required a guess helped operators contribute corrections without defending their interpretation.
@HazelAdams0136 We've found a wording problem, but the reviewed recovery guidance isn't ready. I still need to support the team through the unclear cases.