I programmed our initial Universal Robots UR5e job for tray transfer with a machined sleeve in a workshop tray handling cell and handed it over to the operators. They can start the saved job, but they need me when a pocket is empty or a run is interrupted.
I suspect the handover omitted recovery decisions, rather than the operators lacking willingness.
@AlexBell0646 A teach-back could reveal where the handover becomes unclear. What do operators understand the restart instruction to mean when they explain it without prompts?
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.
Rewrite that line around the visible condition, permitted next step and when to call for help. Have the responsible integrator check it, then repeat the teach-back without prompting.
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?