Leading AI Change Effectively

Welcome to Transformation Professionals, the podcast for managers, leaders and consultants driving transformation and AI adoption in medium to large organizations. Brought to you by cxotransform. This show is designed to help you elevate your impact, harness AI driven insights, lead with confidence and create real business value. Now over to business transformation and AI expert Rob Llewellyn.

So you walk into the office on a Monday morning and the team's already talking not about the weekend, but about the new AI rollout. Some are curious, some are confused, and some are quietly updating their CVs. Because here's the hard truth. 70% of AI initiatives fail not because the tech doesn't work, but because the people don't change. Rob I'm Rob Llewellyn and if you're leading transformation in a medium or large organization, this video is for you. Today we're tackling the real engine behind successful AI, and that's change management. Now let's make this practical. I want to give you a simple five part structure that you can use. It's built around the acronym shift because that's exactly what we're driving a shift in how people think, feel and work. So let's start with S, because story and strategy must come first. Most AI rollouts start with features, but your job is to start with purpose. Why are we doing this? What problem are you we solving? And what story connects this to our strategy? If you don't answer those early, you have a vacuum and fear will fill it. So you can use Cotter's first step, create urgency. But in the context of AI, urgency isn't just about competition, it's about relevance. People need to understand how AI helps the organization adapt and how it helps them stay valuable. When your AI story connects emotionally and strategically, you win early belief. And that's the foundation for everything that follows. So next is H. Because human emotions are are the core of AI change. This is where leaders often slip up. They plan the systems, the vendors, the governance, but they forget the people. AI triggers something much deeper than most digital change because it doesn't just change tools, it threatens identity. You're not just asking someone to learn a new interface, you're asking them to trust the machine's judgment, to let go of tasks that define their role, to believe that this isn't the beginning of their obsolescence. This is where Bridger's transition model becomes essential. It teaches us to lead people through three emotional letting go of the old, navigating the uncertain middle, and embracing the new beginning. When introducing AI, don't just manage tasks, guide transitions, acknowledge the grief of losing old ways, support the ambiguity of learning something new, and celebrate even small moments of progress. When people feel understood, they engage. And when they don't, well, they resist. Next, there's I, which is where we integrate structured frameworks for stability. AI needs a lot more than motivation. It needs structure. Lewin's model is perfect for this. Unfreeze. Start by surfacing resistance. People may not voice it, but you'll see in the questions they ask, the jokes they make, and the silence in the room. Use that resistance as data. It shows you where to lean in change as you roll out AI. Give people scaffolding, not just training, but hands on sessions. Use cases they care about, champions that they really trust, and refreeze once adoption begins, lock in new habits, update the performance metrics, align incentives, and bake it into the future. You can also layer in agile here because unlike other transformations, AI evolves very fast and you'll need room for iteration, feedback and recalibration. Cotter gives you momentum, Bridges gives you empathy, and Luin gives you anchoring. And together they give you control. Then we move on to F, which is about fostering psychological safety for AI adoption. AI transformation asks people to admit they don't know, and that's risky unless they trust the environment. Your teams need to feel it's safe to ask, will I be replaced? What if I don't get it? How do I learn something without looking stupid? And that safety isn't built in keynotes. It's built in team meetings, feedback sessions, and manager one to ones. So make it explicit. Say to people, it's okay not to know. We're all learning together and really mean it. Let your leadership team model vulnerability. Have them share what they're struggling to understand about AI, and that normalizes learning and it accelerates adoption. Transparency isn't a nice to have. It's your insurance policy, especially when the stakes involve identity data and careers. And finally there's t where we turn resistance into a source of momentum. Resistance isn't the enemy. It's a signal. It's a mirror. And if you listen, it becomes your advantage. The worst reaction you can get is indifference. When people resist, they're telling you something. Maybe it's fear, maybe it's fatigue, maybe it's a deeper value conflict. So instead of shutting it down, investigate it. Run listening sessions. Ask managers to map resistance hotspots and use anonymous surveys if needed. And then act on what you hear. For example, if privacy concerns are high, bring in your data ethics team and explain how AI is being governed. Be transparent about the limits of automation. If people are worried about skills, then launch a capability accelerator. Build confidence before the fear sets in. So let me give you a quick example. At one European insurance firm, AI was introduced to optimize underwriting. But long standing underwriters really pushed hard. Not because they hated tech but because they weren't involved. So leadership made a shift. They co designed the AI workflows with the underwriters. The AI didn't replace judgment, it supported it. And when results came in they celebrated human machine collaboration, not replacement. Engagement skyrocketed and adoption followed and the program became a blueprint for other departments. So let me leave you with three immediate actions. First, run a five question AI Challenge diagnostic with your team. Ask them what excites you about our AI plans or concerns you? What support do you think you'll need? What skills feel at risk and what would success look like six months after now? Second, map your current AI initiative to the shift model. Use it to pressure test your change approach. Where are you confident and where are you exposed? And third, pick a framework and actually apply it. Don't just say well, we're using Kota. Write out how you'll walk through each step in the context of AI. Define your urgency, build your coalition, set short term wins and rephrase what matters. And as you lead, don't forget to measure what matters. Adoption rates are only the beginning. You'll also want to track employee confidence with AI tools, reduction in manual processes, time to value for AI features and feedback sentiment across the different business units. At the leadership level, look at alignment with business KPIs, not just usage stats, but business impact faster decisions, better forecasting, fewer errors and stronger outcomes. Because in AI change management, success isn't a login count, it's a shift in behavior, a shift in trust, and ultimately a shift in results.

Thank you for listening to this episode of Transformation Professionals. We hope today's insights help provided valuable guidance for your professional development. For more resources to enhance your capabilities, visit Rob Llewellyn's Enterprise Transformation and AI channel on YouTube or explore Cxotransform.com to learn more about our range of online courses.