Skip to content
Tiatra, LLCTiatra, LLC
Tiatra, LLC
Information Technology Solutions for Washington, DC Government Agencies
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact
 
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact

31% of employees are ‘sabotaging’ your gen AI strategy

Nearly one in three (31%) company employees say they are “sabotaging their company’s generative AI strategy,” according to a survey from AI vendor Writer — a number that jumps to 41% for millennial and Gen Z employees. 

The survey also found that “one out of ten workers say they’re tampering with performance metrics to make it appear AI is underperforming, intentionally generating low-quality outputs, refusing to use generative AI tools or outputs, or refusing to take generative AI training.”

Other activities lumped in as sabotage include entering company information into non-approved gen AI tools (27%), using non-approved gen AI tools (20%), and knowing of an AI security leak without reporting it (16%).

These are the kinds of things industry analysts and observers pushed back against as being “sabotage,” given that in many cases such breaches of conduct involve attempts to improve productivity or make it easier to get work done. Undermining the overall AI strategy might be a more precise description, for some.

“If they are intentionally misleading their employer about the results of using generative AI for a particular process, or dumping their company’s sensitive data into a third-party consumer tool, that’s definitely sabotage,” says Brian Jackson, principal research director at Info-Tech Research Group. But “if they are not using generative AI outputs because of legitimate quality concerns, that may well be part of doing their job. Or if they are using third-party tools but not sharing confidential company details, then it’s also not malicious.”

Still Jackson agrees that actual sabotage is going on, much of it for the obvious reason: boards and senior exes publicly touting AI as a way to reduce the workforce.

“Who is going to be motivated to adopt if they know the intent is to replace them?” Jackson asks. Because “AI can automate new aspects of knowledge work that have required human creativity and intelligence, there might be resistance if people feel like AI is being used to replace people in areas where we enjoy working and where we value a human touch.”

Jackson advises listening to employee feedback on where AI adds value rather than taking a “top-down approach that would risk alienating workers who feel they are training technology that will put them out of a job.”

Jackson also believes that some CEOs aren’t helping to relieve the overall tension around AI and job losses by touting workforce reductions due to AI in situations where it was not true.

“Executives sometimes look to spin layoffs — it’s a rationalization — as, ‘We are not doing this because the company is in trouble. No, we are doing [the layoffs] because AI is making us so efficient that we don’t need as many people anymore.’ Instead of admitting that they over-hired, they prefer to say, ‘We are using AI as mature and tech-savvy leaders,’” he says.

A data analyst overseeing AI integration at an $80 billion retail chain — who asked that his name and employer not be stated — said he has directly seen acts of AI pushback.

Although “outright sabotage is rare, I’ve observed more subtle forms of pushback, such as teams underutilizing AI features, reverting to manual processes, or selectively ignoring AI-generated recommendations without clear justification. In some cases, it’s rooted in fear: Employees worry that increased automation will reduce their role or make their expertise less valued,” the data analyst says. But “what appears to be resistance is actually a cry for inclusion in the change process. People want to understand how AI supports their work, not just that it’s being imposed on them.”

One HR specialist said she also sees a lot of AI sabotage happening, but believes the motivation for it is not unreasonable.

“Employees are resisting, delaying, and, in some cases, actively undermining gen AI rollouts. But labeling this as sabotage oversimplifies what’s often happening,” says Patrice Williams Lindo, CEO of Career Nomad. “It’s not always malicious. It’s often protective. When employees believe gen AI adoption threatens their jobs, especially in environments with frequent layoffs or weak psychological safety, pushback becomes a survival tactic.”

“Sabotage can become real if fears are ignored,” Lindo adds. “If leadership dismisses employee concerns, doesn’t connect AI to clear upskilling pathways, and enforces top-down rollouts, employees may deliberately slow adoption or feed poor-quality inputs to protect themselves.”

Combatting sabotage is tricky

Countering AI resistance requires better training and communication. But training and communication alone won’t eliminate it entirely, especially if executives are candid about plans for layoffs if AI strategies succeed. 

And with AI sabotage likely impossible to fully eradicate, companies can be exposed to significant risks — and liabilities.

Cameron Powell, a technology attorney with the law firm Gregor Wynne Arney, says companies might be exposed to legal penalties if their employees engage in deliberate sabotage. Those companies should remind employees that if they engage in sabotage they too can face personal legal peril.

“If the company is found to have negligently supervised or enabled the employee’s sabotage and that sabotage violates other laws, such as violations of data privacy or HIPAA or confidentiality or consent to one’s data being used in training sets, and so on,” it can be liable for those violations, Powell said. “Employees might also generate information that binds the company to contracts that it does not really want, or that constitutes defamation of a third-party. Or an employee might infringe third parties’ copyrights or trademarks, or disclose trade secrets of the company or one of its partners, any of which could expose the company to liability.”

Powell also points out the risk to employees themselves: “The potential for liability is also a key part of the education companies should be giving their employees, letting them know that sabotage isn’t just hurting the company, but could expose the employee to civil and criminal penalties, as well as jail time.”

Regardless of the fallout, fractional CMO Lars Nyman sees AI sabotage efforts as nothing new.

“This is luddite history revisited. In 1811, the Luddites smashed textile machines to keep their jobs. Today, it’s Slack sabotage and whispered prompt jailbreaking, etc. Human nature hasn’t changed, but the tools have,” Nyman says. “If your company tells people they’re your greatest asset and then replaces them with an LLM, well, don’t be shocked when they pull the plug or feed the model garbage data. If the AI transformation rollout comes with a whiff of callous ‘adapt or die’ arrogance from the C-suite, there will be rebellion.”

See also:

  • 11 surefire ways to fail with AI
  • IT leaders’ top 5 barriers to AI success


Read More from This Article: 31% of employees are ‘sabotaging’ your gen AI strategy
Source: News

Category: NewsJuly 21, 2025
Tags: art

Post navigation

PreviousPrevious post:Textron takes flight with gen AINextNext post:딥엘 CTO “실시간 음성 번역으로 기술력 확장···‘하나에 집중한 AI’의 가능성 입증”

Related posts

The 4 disciplines of delivery — and why conflating them silently breaks your teams
April 22, 2026
The silent failure between approval and delivery
April 22, 2026
AI hype to AI value: Escaping the activity trap
April 22, 2026
The changing face of IT: From operator to orchestrator
April 22, 2026
Ways CIOs can prove to boards that AI projects will deliver
April 22, 2026
5 lessons from Everest for high-risk AI projects
April 22, 2026
Recent Posts
  • The 4 disciplines of delivery — and why conflating them silently breaks your teams
  • The silent failure between approval and delivery
  • AI hype to AI value: Escaping the activity trap
  • Ways CIOs can prove to boards that AI projects will deliver
  • 5 lessons from Everest for high-risk AI projects
Recent Comments
    Archives
    • April 2026
    • March 2026
    • February 2026
    • January 2026
    • December 2025
    • November 2025
    • October 2025
    • September 2025
    • August 2025
    • July 2025
    • June 2025
    • May 2025
    • April 2025
    • March 2025
    • February 2025
    • January 2025
    • December 2024
    • November 2024
    • October 2024
    • September 2024
    • August 2024
    • July 2024
    • June 2024
    • May 2024
    • April 2024
    • March 2024
    • February 2024
    • January 2024
    • December 2023
    • November 2023
    • October 2023
    • September 2023
    • August 2023
    • July 2023
    • June 2023
    • May 2023
    • April 2023
    • March 2023
    • February 2023
    • January 2023
    • December 2022
    • November 2022
    • October 2022
    • September 2022
    • August 2022
    • July 2022
    • June 2022
    • May 2022
    • April 2022
    • March 2022
    • February 2022
    • January 2022
    • December 2021
    • November 2021
    • October 2021
    • September 2021
    • August 2021
    • July 2021
    • June 2021
    • May 2021
    • April 2021
    • March 2021
    • February 2021
    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020
    • May 2020
    • April 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • April 2019
    • March 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • July 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    Categories
    • News
    Meta
    • Log in
    • Entries feed
    • Comments feed
    • WordPress.org
    Tiatra LLC.

    Tiatra, LLC, based in the Washington, DC metropolitan area, proudly serves federal government agencies, organizations that work with the government and other commercial businesses and organizations. Tiatra specializes in a broad range of information technology (IT) development and management services incorporating solid engineering, attention to client needs, and meeting or exceeding any security parameters required. Our small yet innovative company is structured with a full complement of the necessary technical experts, working with hands-on management, to provide a high level of service and competitive pricing for your systems and engineering requirements.

    Find us on:

    FacebookTwitterLinkedin

    Submitclear

    Tiatra, LLC
    Copyright 2016. All rights reserved.