# Employees Sabotage AI: A Step-by-Step Plan for Founders > The team doesn't use AI because they fear losing their job or status. The founder can't force them, but can remove the causes of resistance. Here is a step-by-step plan on how to regain control… - Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board) - Published: 2026-10-31 - Updated: 2026-10-31 - Source: https://aiadvisoryboard.me/blog/employees-sabotage-ai-what-to-do-step-by When you announce AI in your company, the team doesn't greet it with applause. People quietly stop using new tools, "forget" about pilot projects, and reply to feedback that "everything is complicated." This isn't laziness — it's sabotage driven by fear of losing their job or status. As a founder, you can't force them to use AI, but you can remove the reasons why they do. ## TL;DR - AI sabotage is a reaction to fear, not to technology. - The founder should try automation firsthand. - Key employees join training before frontline staff. ## Why the Team Blocks AI People sabotage AI when they see it as a threat, not a tool. Fear of job loss, fear of looking incompetent compared to a machine, and uncertainty about what is expected of them lead to passive resistance. An employee may not refuse outright, but simply won't open the service, won't enter data, and won't provide feedback. As the owner, you see this as a lack of results. The team sees it as protecting their position. Until you reconcile these two perspectives, no training will help. > **Definition:** AI sabotage is passive or active employee resistance to using artificial intelligence in work processes due to fear of change or loss of status. ## Is It Really Sabotage, or Technical Problems? Start with an honest check. Does the tool work as promised? Is the instruction clear? Do people have time for training, or are they loaded on top of their main work? Often what looks like sabotage is actually a poorly planned rollout. Ask yourself: 1. Have I tried this exact tool on my own work? 2. Do I know how much time it will take an employee per week? 3. Is it explicitly stated that this is not a replacement for the person, but help for them? If the answer to any of these questions is "no," the problem isn't the team — it's your approach. ## Step-by-Step Plan for the Founder ### Week 1: You figure it out yourself Use AI on a real task first. Not a demo, but real work: a meeting summary, a contract draft, a report analysis. If you can't explain firsthand what and why the tool does, the team won't believe you. ### Week 2: Key employees try it on their tasks Choose 2-3 people you trust and who influence the team. Give them time to learn without deadline pressure. They should become the first examples, not you. ### Week 3: Choose one priority task for automation Don't try to automate everything at once. Pick one routine that eats up the most time. Let key employees see the result on their own data. ### Month 2: Frontline employees join the active ones Once the first automations work, invite a wider group. Not everyone at once — those who showed interest. People follow the example of colleagues, not management orders. > **Definition:** Frontline employees are workers who perform core operational work without managerial functions. ## Checklist: How to Remove the Causes of Resistance - ☐ The founder has personally used AI on their own work - ☐ The team knows AI won't replace them, but will change their tasks - ☐ There is one working automation on real company data - ☐ Key employees are trained first - ☐ There is a clear plan on who and when switches to the new way of working - ☐ There is feedback from those who have already tried ## How This Works on Our Side Corporate intensive for key personnel: 4 live sessions of 2 hours over 2 weeks, up to 20 employees from the company. The company itself chooses 3 priority tasks, and by the end of the program has at least 3 working automations — with a money-back guarantee. No programming needed: participants describe logic in words, AI writes the code. https://course.aiadvisoryboard.me/corporate?utm_source=blog&utm_medium=article_body&utm_campaign=corporate ## FAQ ### Should I fire those who don't want to use AI? No. Firing increases fear and forces others to hide their use of tools. Better to find the cause of resistance and remove it. ### How to measure that sabotage is decreasing? Record how many people actively use the tool at the start and after a month. The number of working automations and feedback from training participants are best documented in writing. ### Can the IT department solve this on its own? No, if the founder doesn't take the first step. IT can set up tools, but can't [make](https://www.make.com/en/pricing) people trust them. ### How long will it take? First results appear in 2-4 weeks if the founder is personally involved. Full rollout to the whole team takes several months. ## Conclusion AI sabotage is a signal that the team doesn't understand what is expected of them and is afraid of losing their place. The founder should try the tool first, then involve key employees, and only then scale to the whole company. Don't try to force — create conditions where people themselves want to use AI. Do one thing tomorrow: pick a real work task and try to solve it with AI. If it works — show it to a key employee. If it doesn't — figure out why, and try again. The first free consultation-diagnostic helps break down one real company task and see where to start. --- When citing, link to https://aiadvisoryboard.me/blog/employees-sabotage-ai-what-to-do-step-by. More articles: https://aiadvisoryboard.me/blog