AI did not create the fear inside companies. It exposed it.
I have sat in that silence more times than I would like. After a while, you stop hearing it as silence and start hearing it as data. — The Situation In Q1 2022, I was brought in to assess why an enterprise AI deployment had stalled at eleven percent adoption after six months. Let me be precise about what eleven percent means in practice. The system was live, the training had been delivered, the dashboards were accessible, and nine out of ten people who were supposed to be using it had found creative ways not to. Some cited technical friction. Some said the interface was unclear. One memorable response, delivered entirely without irony, was that the tool “did not integrate well with existing workflows,” by which the person meant Microsoft Excel, which they had been using since 2009 and had no intention of replacing. The technology was credible. The vendor was serious. The business case, built over eighteen months, was robust. This was not a situation where a CISO had approved a toy and called it transformation. So I did what I usually do when the obvious answers have already been ruled out: I stopped asking about the technology and started asking about the people. I ran structured sessions with front-line teams and middle management. Not surveys, actual conversations, one level removed from senior leadership so people had some room to be honest. What emerged had almost nothing to do with AI. People were afraid. Not of the AI specifically. They were afraid of being seen to be wrong, afraid that using a new tool meant producing outputs that could be scrutinised, compared, questioned. They had spent years in an environment where errors were punished swiftly and questions were absorbed slowly or not at all. The culture had taught them, with considerable consistency, that visibility was risk. The AI had not introduced that fear. It had simply given it a new surface to sit on. I will be honest: I did not see it immediately. My first instinct, arriving with the brief I had been given, was to look at the implementation, the change management plan, the training quality, the communication cascade. I spent the first week in the wrong territory entirely. The moment I understood what was actually happening came midway through week two, in a conversation with a mid-level analyst who said, quietly, that she would rather do the work manually and be wrong on her own terms than use the system and have the wrong answer attributed to her in a log. That is not a technology problem. That is a decade of learned behaviour, dressed up as a UI complaint. — The Analysis The first thing to understand is that AI systems, by design, make work legible. They create records, trails, decision logs. They answer questions with timestamps attached. In an organisation where accountability has historically flowed downward and rarely upward, that legibility is not experienced as efficiency. It is experienced as exposure. This is the counter-intuition that most AI change programmes miss: the resistance is not irrational. It is a perfectly rational response to an environment where being seen has historically been dangerous. When you introduce a tool that makes every decision more visible, you are not simply adding technology. You are changing the terms on which people have learned to survive professionally. The silence before that resistance sets in is the same silence that kills projects long before any consultant is called in to diagnose them. The second insight is that money spent on AI change management cannot do the work that cultural repair needs to do. I have watched organisations invest heavily in adoption programmes, comms campaigns, lunch-and-learns, executive sponsorship videos, gamified dashboards showing which teams had hit their usage targets, and seen adoption numbers remain stubborn, because none of those interventions addressed what the people in those rooms had actually learned about what happens when you make a mistake in front of the wrong person. You cannot train away a culture. You can only build a different one over time, with evidence. The third point is the one that is most uncomfortable for leadership to hear: if your AI rollout has stalled, the diagnosis is sitting in your own management behaviour, not in the vendor’s implementation. The organisations I have seen successfully deploy AI at scale share one characteristic that has nothing to do with the sophistication of the model or the quality of the data architecture. Senior leaders in those organisations are visibly, repeatedly, publicly comfortable with being wrong. They use the tools themselves, in front of people, and say, “That gave me a result I did not expect, let me work through why.” That one behaviour, modelled consistently, does more for adoption than any change management framework I have encountered. — The Implication If you are leading an AI programme, or sitting on a board that is overseeing one, the question worth asking is not “What is our adoption rate?” The question is: “What does it cost someone in this organisation to be visibly wrong?” If the honest answer is “More than it costs to quietly underperform,” no implementation plan will save you. The technology will land. The adoption will not. And eighteen months from now, someone like me will be brought in to explain why a credible tool with a sound business case is sitting at eleven percent. The answer will be the same answer it always is: the AI was fine. The culture had work to do before the first model was ever deployed. — Closing Organisations do not fear AI. They fear what AI makes visible about the way they have always operated. Fix that first, and the adoption numbers will take care of themselves. AI does not create fear in organisations. It inherits it.