The Hidden Reason AI Projects Fail
You walk into the office on Monday. 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.
I’m Rob Llewellyn. And if you’re leading transformation in a medium or large organisation, this video’s for you. Today, we’re tackling the real engine behind successful AI: change management.
Now, let’s make this practical. I want to give you a simple five-part structure 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.
S – 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 we solving? And what story connects this to our strategy?
If you don’t answer those early, you leave a vacuum — and fear will fill it.
Use Kotter’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 organisation 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.
H – Human Emotions Are the Core of AI Change
Here’s where leaders often slip.
They plan the systems, the vendors, the governance. But they forget the people. AI triggers something 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 a machine’s judgement. To let go of tasks that defined their role. To believe that this isn’t the beginning of their obsolescence.
This is where Bridges’ Transition Model becomes essential. It teaches us to lead people through three emotional phases:
- Letting go of the old.
- Navigating the uncertain middle.
- 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. Celebrate even small moments of progress. When people feel understood, they engage. When they don’t, they resist.
I – Integrate Structured Frameworks for Stability
AI needs 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 it in the questions they ask, the jokes they make, 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 they trust.
And Refreeze – Once adoption begins, lock in new habits. Update the performance metrics. Align incentives. Bake it into the culture.
You can also layer in Agile here — because unlike other transformations, AI evolves fast. You’ll need room for iteration, feedback, and recalibration. Kotter gives you momentum. Bridges gives you empathy. Lewin gives you anchoring. Together, they give you control.
F – Foster Psychological Safety for AI Adoption
AI transformation asks people to admit they don’t know. 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 without looking stupid?”
And that safety isn’t built in keynotes. It’s built in team meetings, feedback sessions, and manager 1:1s. Make it explicit. Say, “It’s okay not to know. We’re learning together.” And mean it. Let your leadership team model vulnerability. Have them share what they’re struggling to understand about AI. That normalises learning — and accelerates adoption.
Transparency isn’t a nice-to-have — it’s your insurance policy. Especially when the stakes involve identity, data, and careers.
T – 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?
- Indifference.
- When people resist, they’re telling you something.
- Maybe it’s fear.
- Maybe it’s fatigue.
- Maybe it’s a deeper value conflict.
Instead of shutting it down — investigate.
- Run listening sessions.
- Ask managers to map resistance hotspots.
- 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. Explain how AI is governed. Be transparent about the limits of automation. If people are worried about skills, launch a capability accelerator. Build confidence before the fear sets in.
Let me give you a quick example. At one European insurance firm, AI was introduced to optimise underwriting. But long-standing underwriters pushed back hard. Not because they hated tech — but because they weren’t involved. So leadership made a shift. They co-designed the AI workflows with underwriters. The AI didn’t replace judgment — it supported it. And when results came in, they celebrated human-machine collaboration, not replacement.
Engagement skyrocketed. Adoption followed. And the programme became a blueprint for other departments.
Your Next Steps to Lead the Shift
Let me leave you with three immediate actions.
First, run a five-question AI change diagnostic with your team.
Ask:
- What excites you about our AI plans?
- What concerns you?
- What support do you think you’ll need?
- What skills feel at risk?
- What would success look like six months from now?
Second, map your current AI initiative to the SHIFT model.
- Use it to pressure-test your change approach.
- Where are you confident?
- Where are you exposed?
Third, pick a framework — and actually apply it.
- Don’t just say “we’re using Kotter.” Write out how you’ll walk through each step in the AI context.
- Define your urgency.
- Build your coalition.
- Set your short-term wins.
- Refreeze 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 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, stronger outcomes. Because in AI change management, success isn’t a login count. It’s a shift in behaviour. A shift in trust. And ultimately, a shift in results.
.png)