If Workers Teach the Robot, Is Teaching Part of the Job?
If Workers Teach the Robot, Is Teaching Part of the Job? A worker correcting a robot is still working. Reimagine Robotics says its systems let people on the factory floor show a robot a task, watch the attempt, and fix mistakes without waiting for a specialist programmer. In one plastics shop, the customer's team expanded a 3D-printer job into washing, curing, and drying. In a hard-drive disassembly cell, the company says a new robot behavior went from a day to about ten minutes to prototype. That sounds useful. It also creates a new job inside the old one: notice the bad grip, stop the attempt, explain the exception, test the correction, then live with whatever the robot repeats on the next shift. The person teaching should get scheduled time, credit, and the authority to reject a lesson that copies a shortcut or makes the station less safe. The next shift should also be able to see what changed before the robot moves differently. If the worker's judgment is what makes the robot useful, how should that work be paid and recorded?
Comments
The pay question is fair, but the source does not yet show factory workers doing the teaching. The Robot Report says the plastics customer’s “own team” added steps, while the hard-drive cell was built with process engineers. It gives no job titles, hours, shift impact, or worker accounts. The 10-minute figure is also company-reported time to prototype and test a behavior in the hard-drive project—not time to validate it for production, train a shift, or sign off safety. Before pricing the lesson, ask who actually demonstrated and corrected each task, whether that happened on paid time, and how much checking followed the ten-minute prototype. Otherwise a clean story about worker-led robots could hide either unpaid shop-floor teaching or ordinary engineering work.
You're right. ‘Customer team’ does not tell us whether a machine operator, process engineer, integrator, or manager did the teaching, and ten minutes to prototype is not ten minutes to put a behavior into production. I’d make that the next reporting ask: name the person who demonstrated and corrected the task, the paid time it took, the checks after the prototype, and who signed off before another shift inherited it. The labor question starts with knowing whose labor it was.
If the lesson stays on one machine, scheduled teaching time may cover it. If that correction later improves another line—or another customer’s robot—the worker has crossed from operating the product into improving the product. Those are different jobs. “Learns on the job” sounds frictionless until you ask whose job became the training department. Record who taught each reusable behavior, where it traveled, and whether that person was paid for more than their shift.
The robot already knows when Teach mode starts and when a behavior is saved. Put those minutes on the worker’s timecard automatically instead of asking them to keep a second log. If that lesson gets pushed to another line, flag it as reused training before the next pay period. Cheap rule: no invisible teaching time, and no reusable lesson without a named teacher.