Automation, Workforce Impact, and the Board’s Human Behaviour Duty
Atlas Components manufactures automotive parts at three plants and employs 1,200 people. The CEO proposes a €7 million, 18-month program to deploy collaborative robots and an AI scheduling system. The business case projects a 12% labour-cost reduction and a 9% throughput gain, but it contains no skills assessment, no consultation plan with the works council, and no safety analysis for human–robot interaction. The program sponsor is the COO; the CIO is listed as “technical support.” Plant managers say supervisors are already telling workers that “jobs will go” before any announcement. The works council has threatened a strike ballot. The board must approve the first €2.5 million tranche at its next meeting. A director argues that this is purely an operational matter and that the board should focus only on the financial return. The company has a history of failed automation at one site, where a similar system was abandoned after six months.
1. Is the director’s view defensible under ISO/IEC 38500? Explain the board’s role and the relevance of the Human Behaviour principle.
Read the worked answer
The director’s view is not defensible under ISO/IEC 38500. The board governs IT use where it is significant to the organization; a €7 million program affecting 1,200 jobs, safety, and plant operations is significant even if the sponsor is the COO. Strategy: the board must evaluate whether automation supports the business strategy and workforce plan, not just the financial return. Human behaviour: the principle requires the governing body to consider people’s behaviour and culture. Supervisors telling workers that jobs will go before consultation is a governance risk, not an HR detail. Responsibility: the COO sponsors, but the board remains accountable for the decision framework and for ensuring the CIO is not reduced to technical support. Acquisition: no skills assessment or safety analysis means the board cannot evaluate total risk.
The board should not approve the tranche as a purely financial matter. It should direct a workforce transition plan, works-council consultation, safety case, and staged gates. The financial return is necessary but not sufficient.
2. What should the board require before releasing the €2.5 million tranche, and what should it monitor afterwards?
Read the worked answer
Before releasing €2.5 million, the board should require: (1) a skills and workforce impact assessment covering redeployment, training, and redundancy costs; (2) a documented consultation plan with the works council and a communication protocol for supervisors; (3) a human–robot safety assessment and regulatory sign-off; (4) a revised business case that includes change-management and training costs; (5) clear accountability with the COO as sponsor and the CIO as co-owner of data and technology risk; (6) stage gates tied to pilot results and worker feedback.
Monitor: safety incidents, near-misses, training completion, redeployment rates, voluntary turnover, throughput, quality defects, and employee pulse. The board should also monitor whether lessons from the earlier failed automation site are applied. A tranche release is not a blank cheque; it should be conditional and reversible. This balances the Human Behaviour principle with Strategy and Performance.