What Happened
Across industries, AI rollouts are quietly failing. Not because the technology is broken, but because the people using it are pushing back. Workers are pretending to adopt new tools while actually ignoring them, faking competence to avoid scrutiny, or actively undermining systems they were never properly brought into. Experts say the culprit is consistently the same: organizations are skipping the human steps entirely and wondering why the machines aren't delivering.
The Communication Angle
Here is the contrast that defines this mess. Company A announces its AI rollout with a slick all-hands presentation. Leadership shows dashboards, talks efficiency gains, and sends everyone back to their desks with a login and a deadline. Company B calls its department heads together first, asks them what their teams are afraid of, listens to the answers, and builds the rollout timeline around those conversations. One of these companies has workers who are faking adoption six months later. You already know which one.
The failure in Company A is not a technology failure. It is a sequence failure. Leadership communicated the destination before they communicated the reason. People do not resist change. They resist being changed without explanation. When workers hear "we are implementing AI" before they hear "here is what this means for your role specifically," their brains fill in the blank themselves. And they will fill it in with the worst possible answer every time.
What should have been said instead is simpler than most executives want to believe. Before any tool goes live, leadership needs to answer three questions out loud, directly, with specifics. What problem does this solve. What does my job look like after this. What happens if I struggle with it. Notice that none of those questions are about the software. They are all about the person. That is the sequence that builds trust instead of resistance.
The silent sabotage described in this story is not malicious. It is a rational response to a communication vacuum. When people are not told the truth clearly, they protect themselves. Skill-faking happens because workers were never given a safe way to say they needed help. Resistance hardens because no one created a channel for honest feedback. These are all downstream effects of leaders who confused announcing with communicating.
This is exactly the kind of scenario I break down in Say It Right Every Time. The chapter on delivering unwelcome information gives you a framework for sequencing hard news so that people stay open instead of shutting down. The core principle there applies perfectly here: when the message feels like a threat, your audience stops listening and starts planning. Your job as a communicator is to defuse the threat before you deliver the news, not after the resistance has already taken root.
Never Be Lost
for Words Again
Get word‑for‑word scripts for the conversations that shape your life, from job interviews and negotiations to difficult talks with family and partners, so you always know exactly what to say and how to say it.
Never Be Lost
for Words Again
Get word‑for‑word scripts for the conversations that shape your life, from job interviews and negotiations to difficult talks with family and partners, so you always know exactly what to say and how to say it.
Key Takeaway
Before your organization flips the switch on any new system or tool, hold a thirty-minute session with your team leads where you ask only this: "What is the one thing your people are most afraid this will do to their jobs?" Write the answers down. Address every single one directly, in writing, before launch day. Not in vague reassurances. In specific, factual sentences. That one step will do more to prevent sabotage than any training program you can buy.
