Most leaders I talk to are focused on the wrong problem.
They want to know which tools to buy, which workflows to automate, which vendors to trust. That’s the wrong starting point, and one of the most reliable ways to waste time, budget, and team trust all at once.
Reasons for a Stalled AI Rollout
Leadership decides it’s time. A tool gets selected. An announcement goes out. Adoption is expected.
Three months later, the AI rollout is stalled, utilization is low, ROI is invisible, and leadership is frustrated. Nobody was defiant and deliberately sabotaged the project. The team just didn’t understand what the change was asking of them, and leadership never took the time to explain it.
That’s a people problem, and it stalls any significant organizational change. I spent years as a Scaling Up coach watching companies fail to execute strategy for the same underlying reason: they moved the organization before the organization was ready to move. AI implementation is no different. The technology is newer. The failure mode is identical.
What “people first” actually means
It doesn’t mean therapy sessions before you buy a software license. It means sequencing your implementation correctly.
Before any tool goes live, your team needs three things.
Clarity on the why. Not “AI is the future.” They need to understand specifically what problem this solves, what changes about their day-to-day, and what stays the same. In a legal firm, your paralegals need to know whether AI is helping them draft faster or replacing judgment calls they’ve owned for years. In a fractional HR firm, your consultants need to know whether their client relationships are still theirs to manage. Ambiguity produces resistance.
Honest answers about job security. This gets avoided constantly. Leaders dance around it. But your people aren’t blind. They’re running the calculation themselves, based on whatever information you’ve given them. When you don’t answer the question directly, they fill the gap with the worst version of the story, and they behave accordingly. A direct conversation, even when the honest answer is that some roles will evolve, produces less damage than silence.
A seat at the table during rollout. The fastest-adopting teams I’ve worked with had one thing in common: someone asked them what they needed before deciding what to implement. The employees who feel included in the process become your internal advocates. The ones who feel excluded become your quiet resisters.
People-First Implementation
Your people are already using AI. They’re not waiting for the official rollout. They’re using personal accounts, free tools, and consumer-grade platforms because the pressure to perform keeps rising and nobody handed them a better option. They’re uploading client data to get faster answers. They’re trying to be resourceful.
A people-first approach addresses this directly. It starts by understanding what your team is actually doing, not what you assume they’re doing. It builds governance around actual behavior, not theoretical risk.
Low adoption means tools you’re paying for that aren’t performing. Resistance means a team that has lost some trust in leadership’s judgment. Unmanaged exposure means a compliance or confidentiality incident waiting to surface.
Where to Start
I always start with an AI Readiness and Exposure Audit. We look at where your team actually stands: what they know, what they’re already doing, where the exposure is, and what needs to be in place before any tool goes live. That assessment shapes the entire roadmap. It’s the difference between an implementation that sticks and one that stalls.
If you’re planning an AI rollout in the next six months, this is where the work starts.
