
Rethink Resistance to Lead Change | Travis D. Hahler
Rethink resistance to lead change. Travis D. Hahler shows why brains send a check engine light and how six neurological barriers predict where AI transformations stall.
With Gleb Tsipursky
AI adoption stalls when leaders treat it like a normal software rollout. Gleb Tsipursky shows how to clear the emotional blockers before you scale.
CategoriesHuman Capacity

Companies are buying AI like crazy and adopting it like molasses. The number named in this episode is blunt: 95% of enterprise pilots show no measurable P&L impact. The tools are in the building. The results are not.
AI adoption fails here because leaders treat it like the last software project. A CRM or an ERP gets a checklist, a training class, and an SOP. AI does not work that way. People have to talk to it, test it on their own work, and stay willing to look clumsy while they learn.
Gleb Tsipursky is the author of The Psychology of AI Adoption at Work: From Resistance to Results, published by Georgetown University Press. The profiles in this episode come from more than 100 consulting projects, more than 600 focus-group responders, and more than 10,000 survey forms, plus his Harvard Business Review article on middle managers. This conversation is about what to do before you scale the pilot.
Gleb's diagnosis is direct. Companies are treating AI as a normal technology. They run the same change plan they would use for a finance system or an HR system: announce it, train it, hand out the checklist, and wait for use.
That plan assumes the tool is standard. AI is not. He calls the work natural language programming. Each employee has to talk to the tool, figure out where it helps, and change the workflow. Leaders who skip that step also skip motivation. They are not focusing on people's psychology, and they are not focusing on getting people engaged.
He names three big emotional blockers and says they have to be addressed before AI can be adopted well. Training that ignores them teaches a skill people will not use. The pilot stays a pilot.
The same pattern shows up as a Drift Tax: the company pays for the tool, the licenses, and the launch, then pays again when the work never changes. That repurchase of performance is the subject of The Drift Tax: Why Organizations Pay Twice for the Same Performance, and How to Stop, which cites this body of research.
Gleb ties a 94% technology-anxiety finding to two biases. The first is confirmation bias. Leaders expected wide acceptance, so they look for proof that the old rollout should have worked. The second is anchoring. They are anchored to how the last system was adopted, so they copy that pattern onto AI.
He also names the fear under the executive team. He jokes about FOFU, the fear of messing up, because a bad AI bet can hit a bank account, a reputation, and a job. Culture slogans do not touch that fear. He says biological safety has to come before psychological safety. Those threat signals are FONE Factors: status, certainty, and fairness are already in the room when someone hears that AI might replace them.
Rank-and-file resistance, he says, is a different set of blockers. Leaders asked him about leadership bias. He answered that first, then came back to the emotions on the floor.
Gleb calls middle managers the gatekeepers. They can make or break AI adoption. From most resistant to most enthusiastic, the five profiles are:
The research basis he gives is chapter 5 of the book and the Harvard Business Review article he said was published on September 1. Executives do not need every manager to become a catalyst. They need to know which profile is sitting on the pilot, because a building full of wait-and-see traditionalists will look like agreement and produce no use.
Employee attitudes are finer-grained than the manager set. Gleb starts at the resistant end. The AI alarmist is often the largest group. The fear is job loss first, then blame for errors. These are people who refuse the tools.
He walks the rest of the curve in order:
The split he cites from Pew is the size of the problem: 52% of people are more anxious than excited about AI, and only 9% are more excited than anxious. A launch aimed at the excited 9% will not move the anxious half.
Gleb starts with an executive choice. To the extent AI creates efficiency, aim that efficiency at growth rather than at cutting jobs. He cites Stanford research that more AI-forward companies in the same industry grow the top line over 9% faster and grow headcount over 6% faster. They do the same work with fewer people per unit, then take share, and still need people to take that share. Some of his clients commit to being job neutral: they will not fire people because an AI tool made a task faster. Jobs will change. The commitment is about what the company will not do.
The second move belongs to middle managers. People believe that using the tool trains their replacement. The conversation he wants is the opposite, and it has to stay honest. People who learn the tools become the productive ones the company keeps. He cites a PwC finding that domain experts with AI skills command a 69% wage premium. Outside the company, the skill is worth more too.
The second blocker is meaning. A CRM lookup does not threaten someone's craft. AI can. Gleb's move is to find the work people love and the frustrations that block that work, then build prompts and agents for those jobs. The tool takes the friction and leaves the identity. Training is more likely to stick because it does not feel like an attack on the person.
The third blocker is colleagues who punish AI use. Alarmists and pragmatic resistors set a social cost. Gleb's move is modeling. Executives and middle managers use the tools in public on the work they already own: P&L analysis, board presentations, major sales meetings, email, and performance reviews. Norms move when the people with status go first.
Until those three are handled, scaling the pilot spreads the failure. He puts it plainly: you can lead a horse to water, but you cannot make it drink. If you do not address the emotional blockers first, you will be lost when you try to scale the AI pilot across the enterprise.
The close of the conversation is a systems point, not a motivation speech. Organizations try to implement AI while they are still conducting business in a pre-AI operating system. The old system asks people to remember, to comply, and to push through resistance with willpower. That will not carry a tool that requires experiment, talk, and local adaptation.
Getting from resistance to results is architecture. A Leadership Execution System is the set of prompts, roles, and feedback that makes the new behavior the normal one: the growth commitment, the manager conversation, the identity-safe use cases, and leaders using the tool where everyone can see it. Fast Leader Show is the official podcast of Execution Architects. Execution is an outcome of system architecture, not human willpower.
Asked which single skill he would take back to age 25, Gleb does not pick a prompt library. He picks emotional self-management. Emotions motivate the leader and everyone else. A leader who cannot see that will keep launching pilots the workforce is too afraid to use.
Pros
Cons
The problem is that companies are treating AI as a normal technology.
They're not really focusing on the buy-in. They're not focusing on people's psychology.
You need to get people to be much more motivated, engaged, enthusiastic about AI tools.
They can make or break AI adoption.
By using AI tools, you're not training your own replacement.
If you don't address the emotional blockers first, you will be lost when you try to scale up the AI pilot across the enterprise.
Never trust your gut.
Gleb says leaders treat AI like a normal technology project. The tool is easier to click than a legacy system and harder to adopt, because each person has to experiment. Pilots stall when emotional blockers are ignored. He points to MIT research that 95% of AI pilots do not show the impact leaders expected.
Fear of job loss, threat to professional identity, and shame or social stigma from colleagues who punish AI use. Each one needs a different first move: a growth commitment, tools aimed at loved work, and leaders modeling their own use.
Identify which of the five profiles you have. Skeptics and wait-and-see traditionalists block by doubt or by inaction. Cautious implementers scale a practice once enthusiasm exists. Experimenters and catalysts create energy, and catalysts need governance so they do not outrun the rest of the company.
Gleb recommends an executive commitment to growth rather than to cutting jobs with the efficiency AI creates. Some of his clients commit to being job neutral. He is clear that jobs will change. The commitment is that people are not fired because a tool made the old task faster. He cites Stanford figures that more AI-forward firms grow revenue and headcount faster than peers.
Fast Leader Show is the official podcast of Execution Architects. To build alignment with a post-AI operating system, visit executionarchitects.com.

Rethink resistance to lead change. Travis D. Hahler shows why brains send a check engine light and how six neurological barriers predict where AI transformations stall.

Paul Ingram, Kravis Professor at Columbia Business School and author of What Do You Really Stand For?, explains values-led decisions, the triad method, and the cost of misalignment.

Build superteams by designing how your team uses time. Psychologist Ron Friedman shares research on focus, meetings, peer accountability, and continuous improvement.

Stop forcing willpower through stress. David A Gerber shows why neck-up efforting burns leaders out and how full-body presence plus composure protects decisions.
Watch on YouTube, or take the audio with you.