Skip to content

The Leader's Job During AI Adoption Is Not What Most Leaders Think It Is

Victoria KenwardAugust 27, 20264 min read

The Assumption That Stalls EverythingThere's a belief I encounter constantly among business leaders navigating AI adoption: this is an IT problem, or a vendor problem, or a process problem, it's no...

The Leader's Job During AI Adoption Is Not What Most Leaders Think It Is

The Assumption That Stalls Everything

There's a belief I encounter constantly among business leaders navigating AI adoption: this is an IT problem, or a vendor problem, or a process problem, it's not really a leadership problem. The thinking goes: we chose the tool, we ran the training, we set the expectation. What happens next is on the team. That thinking is exactly why most AI rollouts stall.

What Leaders Actually Get Wrong

When we rolled out the first version of RogIQ internally at Haley Marketing, our team pushed back hard. Adoption was low. Frustration was high. And the product, which we knew had real problems, because it was version one, became the scapegoat for something deeper. Looking back, the mistake wasn't the product. The mistake was the leadership posture. We assumed that telling people to use the new tool was the same as giving them a reason to. We assumed that because we could see the potential of AI clearly, our team could too. We assumed that grown professionals would try an imperfect tool in good faith if we asked them to. None of those assumptions held. Here's the harder truth: if you're not actively using AI on a daily basis, if you're not exploring what it can and can't do, where it works and where it fails, you cannot model the behavior you're asking your team to adopt. And if you're not modeling it, you have no credibility to encourage it, explain a failure, or guide someone through the discomfort of learning something genuinely new.

The Biology of Resistance

One of the things that shifted my thinking on this: our resistance to change is not a character flaw. It's a biological reality. Human beings are wired for homeostasis. Our systems, physical, psychological, organizational, pull toward equilibrium. Change is effortful by design. And AI, specifically, is not a small change. It touches how people create, how they're evaluated, what their job looks like, and, for many, whether their job exists in its current form. Post-pandemic, that resistance has intensified. Trust is thinner. Tolerance for uncertainty is lower. People are asking harder questions before they buy in. Leaders who treat this as weakness, who push harder on adoption without acknowledging the fear, usually get surface compliance at best. Underground resistance at worst.

What Actually Moves People

The leaders who get this right do a few things consistently:

They acknowledge the fear directly. Not a vague "I know change is hard" acknowledgment, but a specific one. "I know you're worried this changes what your job looks like. Here's what I actually think it means for you." Specificity is what makes the reassurance credible.

They model the behavior themselves. Not in a performative way, not a screenshot of a ChatGPT conversation in the all-hands deck. Actually using the tools, making mistakes with them visibly, and showing the team what it looks like to learn something in public.

They celebrate the signal, not just the result. When someone tries a new workflow, shares a lesson from a failure, or asks a good question about how the tool works, that gets recognized. Not just the wins. The willingness to engage.

They hold the ambiguity without pretending it isn't there. We don't know exactly how AI will reshape every role. Leaders who pretend they do lose credibility fast. The more honest, and ultimately more motivating, frame is: we don't have every answer, but here's what we're committed to figuring out together.

The Reframe That Changes Everything

If your team's adoption of new tools and new revenue streams feels stuck, it's worth asking whether the bottleneck is really operational, or whether it's relational. Do your people trust that leadership is invested in this, not just announcing it? Do they believe the change is real, or another initiative that will fade in 90 days? Do they feel seen in their resistance, or pressured past it? Those are leadership questions. No software deployment answers them. The hardest part of introducing something genuinely new isn't finding the right tool. It's becoming the kind of leader whose team believes the new thing is worth the discomfort of learning it. That's the work. --- Victoria Kenward is Co-CEO of RogIQ, a marketing operating platform for agencies and small marketing teams.

Contact us today