
Why Gleb Tsipursky wants skeptics inside AI projects
Gleb Tsipursky is CEO of Disaster Avoidance Experts, a boutique consulting and training firm that helps mid-sized and large organizations address the human side of AI adoption. Tsipursky argues that resistance is useful evidence, and explains why involving skeptics in pilots can improve testing and build buy-in, even if it takes longer.
Tsipursky argues that employee resistance can reveal gaps in trust, clarity or training. He recommends giving skeptics formal roles in pilots and governance, while accepting that this can slow decisions.
What’s one opinion about your industry that most of your peers would disagree with?
Resistance to AI is useful data, and leaders should bring skeptics into AI projects instead of working around them.
What convinced you? Tell us about the moment, client or result that changed your mind.
The clearest case I have comes from the e-commerce company with about two hundred staff that I describe in my book. Early on, employees worried that AI would overshadow roles they had spent years perfecting, and others feared that if AI could draft half their emails, management might downsize the team. The company turned this around by naming those concerns openly, running pilots through mid-level managers, and highlighting small, practical wins. That experience convinced me that resistance is not an obstacle to remove. It shows where trust, clarity, or training is missing.
What’s the usual way people in your field handle this, and what do you do instead?
The common approach treats AI as a software rollout. Leaders select a tool, run training on its features, and handle skeptics as obstacles to route around or wait out. I recommend the opposite: deliberately include skeptics in pilot teams, governance committees, and task forces, and give them a formal role such as red-teaming a tool before deployment. For example, a skeptical finance employee can stress-test a forecasting tool before rollout, which improves the tool and builds buy-in at the same time. I also recommend an anonymous channel for dissent, because quiet skeptics rarely raise their hands in meetings.
Where has this view cost you, or where have you had to admit you were partly wrong?
This approach costs time. Involving skeptics can slow pilots and lengthen decisions, and leaders who want a fast rollout will feel that friction. It also does not guarantee buy-in, because some skeptics remain skeptical even after the evidence comes in. I accept that trade-off, because the alternative tends to produce quiet foot-dragging that costs more over time.
What should someone in your field stop doing, and what should they start doing?
Stop treating AI adoption as a tool launch measured by licenses issued, and stop treating skeptics as roadblocks. Start pairing each pilot with a skeptic, measuring time saved and errors caught, and sharing failures openly as lessons, so employees see that the organization values learning over perfection.
Thank you to Gleb Tsipursky and the team at Disaster Avoidance Experts for sharing an honest view with Leaders Perception readers.
Have a view your industry needs to hear?
Leaders Perception publishes interviews with business owners and leaders who see their industry differently. Five questions, about ten minutes, no calls. It is free and every completed interview gets published.
