Sources: IBM's AI isn't up to the job to meet CEO Arvind Krishna's commitment to replace ~7,800 staff and some of the people who could fix that have been let go
Thomas Claburn / The Register :
Context & Ripple Effects
IBM had already tied generative AI to back-office workforce planning, with Krishna saying in 2023 that the company would slow or halt hiring for roles it expected AI to affect. The reported gap between that ambition and execution makes the earlier AI-linked back-office hiring plan a live operational test rather than a distant forecast.
The issue also sits alongside IBM’s push to build an enterprise AI business around WatsonX. Reports that personnel able to improve the systems have departed put delivery capacity—not just AI positioning—at the center of the story.
First-order effects
- IBM faces a near-term mismatch between its stated plan to automate work associated with roughly 7,800 roles and the reported capability of its AI systems, limiting its ability to execute that workforce change as envisioned.
- Letting go of employees who could improve the AI compounds the implementation problem: the company may have less internal capacity to close the reported performance gap.
Second-order effects
- The report raises the bar for IBM to demonstrate that its enterprise AI offerings can reliably automate defined business workflows, rather than relying on broad productivity commitments.
- Workforce and automation planning become more tightly coupled: if the technology is not ready, cost-saving assumptions and staffing decisions may need to be revisited or delayed.
Third-order effects
- This is a test of AI industrialization: enterprise value increasingly depends on integration, evaluation, and operational talent, not simply access to models or public automation targets.
- If similar execution gaps persist across vendors, companies may shift from headcount-replacement narratives toward narrower, measurable workflow deployments before restructuring around AI.
The trend: Enterprise AI is moving from strategic workforce promises to a harder execution phase in which deployment reliability and implementation talent determine whether automation claims translate into operating change.