Hyundai Robot Dispute Shows Why Workforce Readiness Must Come Before Automation
What has happened?
Workers at Hyundai’s Ulsan car factory in South Korea have taken partial strike action amid concerns about the possible future use of humanoid robots.
The dispute followed increased attention around Hyundai and Boston Dynamics’ Atlas robot, which is being developed for industrial work.
Hyundai plans to introduce Atlas at its non-unionised Metaplant facility in Georgia by 2028. The company has not announced a date for deploying the robot at its South Korean factories.
Workers at Ulsan are seeking stronger employment safeguards and greater certainty about how automation may affect jobs and working conditions.
For ComputeGlobal’s audience, the lesson is important.
Automation readiness is not only about whether a robot can technically complete a task.
It is also about whether the organisation has prepared its people, roles, policies and operating model for the change.
Why this matters for businesses
Most automation projects begin with a technical question.
Can a robot lift this component?
Can AI inspect this product?
Can an autonomous machine move goods across the warehouse?
Those questions matter, but they are incomplete.
Businesses must also consider:
- Which roles will change?
- Which tasks will remain human-led?
- What new skills will employees need?
- How will performance be measured?
- Who is accountable if the system fails?
- How will staff raise safety or quality concerns?
- What evidence will employees receive about the purpose of the project?
- How will the organisation prevent uncertainty from becoming resistance?
The Hyundai dispute shows that even a technically capable automation programme may face serious difficulty if workforce planning begins too late.
Employees may view the technology as something being done to them rather than something being designed with them.
That can affect morale, implementation speed, knowledge transfer and day-to-day cooperation.
Why this story matters
This story matters because workers want to understand what new technology means for their jobs.
Imagine that a business announces a robot will soon complete part of a production process.
Employees may immediately wonder:
Will my role disappear?
Will my targets increase?
Will I be expected to supervise the robot?
What happens if it makes a mistake?
Will I receive training?
Is the new process safe?
If management does not answer those questions clearly, people may assume the worst.
In simple terms, automation creates operational change and human uncertainty at the same time.
A responsible programme must manage both.
What organisations should do next
Businesses considering robotics or AI should include workforce readiness from the beginning of the project.
The starting question should not only be:
“Can this task be automated?”
It should also be:
“How should the work, roles and responsibilities change if we automate it?”
Useful questions include:
- Which tasks are being considered for automation?
- Why have those tasks been selected?
- What evidence shows that automation may help?
- Which employees currently understand the process best?
- How will they contribute to the design and pilot?
- Which tasks will remain dependent on human judgement?
- What training and career pathways will be offered?
- How will safety incidents and system failures be managed?
- What commitments can the organisation make about redeployment or role redesign?
- How will progress and concerns be communicated?
Early consultation does not mean giving up management responsibility.
It means using operational knowledge and addressing legitimate concerns before the technology is installed.
Impact on different organisations
SMEs
SMEs often have close working relationships and limited specialist resources.
That can make consultation easier, but it can also mean that one automation project significantly affects a small team.
SMEs should explain the operational problem clearly and involve the employees who perform the task every day.
A small pilot may allow the business to test both the technology and the new working arrangements without committing to a large change.
Medium businesses
Medium-sized organisations may have several teams affected by one project, including operations, maintenance, IT, quality, health and safety and human resources.
They should create a cross-functional implementation group before selecting the final technology.
The project should include a skills-gap assessment and a plan for training supervisors, operators and maintenance staff.
Large businesses
Large organisations may deploy automation across several lines, departments or sites.
Without common governance, each project may communicate with workers differently and create inconsistent expectations.
Large businesses should establish organisation-wide principles covering:
- Consultation.
- Safety.
- Role redesign.
- Redeployment.
- Skills development.
- Data and monitoring.
- Human oversight.
- Incident reporting.
Multinationals
Multinationals must adapt automation programmes to different employment laws, industrial relations systems, cultures and workforce expectations.
A deployment model that works in one country may create resistance in another.
Global standards should set minimum requirements, but local teams should have authority to adapt consultation, training and implementation methods.
Public sector
Public-sector organisations may introduce robotics and AI into logistics, healthcare, laboratories, estates, transport and infrastructure.
They should consider public accountability, recognised unions, equality duties, service continuity and the need to maintain human judgement in high-impact decisions.
Projects should be transparent about what the technology will and will not do.
Contractors and subcontractors
Contractors may introduce automation within a client-controlled environment.
They should confirm who is responsible for:
- Consulting affected staff.
- Delivering training.
- Managing safety.
- Monitoring performance.
- Responding to incidents.
- Handling workforce changes.
- Maintaining the equipment.
Automation should not create unclear accountability between the client and its supply chain.
Practical workforce and automation-readiness checklist
- Define the operational problem before selecting technology.
- Identify the tasks that may change, not only the job titles.
- Involve frontline employees in workflow mapping.
- Record which tasks require experience, judgement or human approval.
- Assess health, safety and human-robot interaction risks.
- Explain why automation is being considered.
- Identify affected teams, contractors and representatives.
- Complete a skills-gap and training-needs assessment.
- Define future operator, supervisor and maintenance responsibilities.
- Establish escalation and manual override procedures.
- Clarify how worker performance data will be collected and used.
- Decide how errors, downtime and system failures will be investigated.
- Create a fair plan for redeployment, retraining or role redesign where appropriate.
- Pilot the technology with clear technical and workforce measures.
- Review employee feedback before wider rollout.
- Build workforce, training and change costs into the business case.
Where ComputeGlobal fits in
ComputeGlobal supports organisations planning responsible and practical automation adoption.
This may include:
- Automation-readiness assessments.
- Workforce-readiness reviews.
- Workflow and task analysis.
- Robotics and cobot feasibility studies.
- Human-robot interaction planning.
- Skills-gap assessments.
- Operational performance reviews.
- Technology adoption roadmaps.
- Grant-ready automation business cases.
The aim is not to recommend automation automatically.
It is to help organisations understand whether the task, technology, workforce, systems and business case are ready for a controlled and sustainable decision.
