Why AI rollouts stall, and how to restart one
By Rodney Noriega, Founder, Universal Enablement · Published Oct 12, 2026
Short answer
AI rollouts usually stall for people reasons, not technology reasons. Common causes: no specific job for the tool, no one in charge of it, little training, staff who don't trust the results, and staff worried about their jobs. The fix is to treat it as a change in how people work: one clear task, a named owner, hands-on training, and visible results.
The pattern is familiar. Someone buys ChatGPT, Copilot or Gemini licences for the team. A few keen people try it. Without a clear job for the tool, use drifts and the subscription quietly renews.
Pushback against new technology is old, and often misunderstood. The Luddites who smashed weaving machines in the early 1800s are remembered as anti-technology. Historians mostly see them as protesting how workers were treated as the machines arrived. Staff wary of AI today are often asking the same thing: what does this mean for me?
What gets a stalled rollout going:
- One task, not a platform. "Use AI more" fails. "Use it to draft replies to quote requests" works.
- A named owner who checks outputs and answers questions.
- Training on your real work, not generic demos.
- An honest answer about jobs. Say what the saved time will be used for.
- Shared results. Hours saved and mistakes caught, posted where the team can see them.
AI adoption is a people problem, not a technology problem. That's the idea behind how we work.
Related
Start with one workflow. In 30 minutes we'll look at where your team's time goes and tell you honestly whether AI can help.
Book a free 30-minute workflow review