The psychology behind AI resistance: What CIOs need to know
Summary
Employees are showing new forms of resistance to AI — active refusal, passive avoidance and superficial use — because AI threatens basic human needs like security, competence and social standing. The article draws on Maslow’s Hierarchy of Needs and expert commentary from Sebastian Raaff (Novartis) and Mark Beccue (Omdia) to explain how speed, visibility and perceived threat make AI feel different from past technologies.
CIOs are urged to engage transparently: explain AI’s benefits and limits, involve employees early in tool development, integrate HR, learning and compliance into change management, and design workflows where humans add emotional intelligence and nuance. When employees see the journey, they are more likely to accept the destination.
Key Points
- AI resistance stems from primal concerns — job security, competence and social role — amplified by AI’s speed and visibility.
- Resistance appears as active refusal, passive low usage, or superficial, cynical use of AI tools.
- CIOs must communicate AI’s benefits and limitations openly to build trust and reduce uncertainty.
- Involve employees in building AI tools (not just handing down finished products) to foster ownership and familiarity.
- Change management should start before an MVP and include HR, L&D, communications, risk, legal and line managers.
- Design human+AI workflows that let people contribute emotional intelligence, nuanced judgement and escalation when AI fails.
- When leaders are transparent and engaged early, AI deployments are far more likely to deliver real value.
Context and relevance
This piece is important for CIOs and senior tech leaders navigating AI rollout. It links established psychological theory to practical change management steps, aligning with broader trends that prioritise ethical, human-centred AI adoption and hybrid human–AI workflows. Organisations that ignore these behavioural dynamics risk low adoption, wasted investment and damaged morale.
Why should I read this?
Quick, useful and directly applicable if you’re responsible for getting AI into daily use. It explains why people push back (it’s not just stubbornness) and gives concrete leadership moves you can start doing today — involve staff early, be honest about limits, and design for human strengths. Saves you time by cutting through the buzz and focusing on what actually makes deployments work.
Author style
Punchy: the article is direct and practical — a must-read for CIOs who need to turn AI plans into real, usable tools without alienating staff. If you care about adoption and ROI, this is high-impact reading.