The Hesitation Gap

So here's the part most leaders miss

I've watched companies spend hundreds of thousands of dollars on an AI rollout and watch it quietly stall, not because the technology was wrong, but because nobody on the leadership team actually sat down with their people and asked what they were afraid of. The team's fear is almost never irrational. Most of the people I sit with have already watched a round of layoffs somewhere. They've already seen a colleague get told a tool would amplify their work and then watched that colleague's role get cut six months later.

When leadership pushes harder on adoption without addressing that, you don't get adoption. You get compliance. People use the tool when leaders are watching and stop the moment they're not. The rollout looks like it's working in the dashboard, and three quarters later you wonder why nothing changed.

This workshop is for the leaders who are tired of pushing on a rope. We do the work that adoption sits on top of.

What we do in the room

Three hours, broken with a real break in the middle. This workshop is built for leadership teams specifically. The broader-team workshop (AI Without Atrophy) is a separate engagement that can run before or after this one, depending on whether team resistance or skill atrophy is your bigger problem to address first.

1. The Real Source of Hesitation Where the team's resistance is actually coming from versus what they say in meetings. We work through the patterns I see most often (job security fear, identity fear, quality fear, equity fear) and your leadership team identifies which ones are alive on your team right now. This is usually the hardest part of the workshop. It's also the most useful.
2. The Conversations You've Been Avoiding Every leadership team has the conversations they don't want to have. With the team about layoffs. With the board about pace. With each other about whether the rollout is actually working. We name them, prioritize them, and build the script for the first one your team is going to have.
3. The Conditions for Safe Experimentation Adoption happens when people feel safe enough to test AI on real work, fail at it visibly, and tell leadership what they learned. We map the conditions you'd have to create for that to be possible on your team. Most organizations realize they're missing two or three of them. We figure out which ones.
4. The Leadership Agreement What your leadership team is committing to do differently in the next 30 days. Specific, named, owned. A working agreement (not a slide deck) the team signs on to and references in their next meeting.

Who should be in the room

• Executive teams setting AI direction for the organization
• Mid-level managers stuck between leadership pressure and team pushback
• HR and People leaders carrying the human side of the rollout
• Department heads who own the day-to-day of an active AI rollout

This workshop is leadership-only by design. The conversations don't work if the broader team is in the room. Once your leadership team has done this, you can run AI Without Atrophy with the wider staff with a much better chance of it actually landing.

The pre-workshop assessment

Optional but encouraged. A short intake every leader fills out before the workshop. It surfaces three things: where each leader thinks their team's hesitation is coming from, which conversations they've been avoiding, and what they think the leadership team agrees on versus where they're actually misaligned. Results stay confidential, but the patterns I see across the team get used to customize the session.

Why this matters

Honestly, most of the leaders I coach are dealing with one version of this. Their team is quietly nervous. Leadership doesn't quite know what to do. The pressure from the board or the market is real, so they push harder. The team pushes back, often passively. Nobody is having the actual conversation. AI sits on the team like a tool nobody fully picked up and nobody is allowed to put down. That gap, between what leadership wants and what the team is actually willing to do, is the hesitation gap. It's where most AI rollouts go to die. This workshop is built to close it.

What this workshop won't do

This workshop is built for leadership teams who are willing to be honest in the room. It won't work if the people in the room can't speak openly in front of each other (that's a culture issue that has to be addressed first). It won't tell you which AI tools to buy, and it won't replace the work of actually executing a rollout. What it does is give your leadership team the alignment, the language, and the playbook for the conversations that have to happen before any tool starts producing real adoption.

Frequently asked