Who it is for
For anyone tasked with rolling AI out to a skeptical team without panic, mutiny, or a single wasted training session.
Roll AI out to a skeptical team — no panic, no mutiny, no wasted training sessions.

You've been handed a job harder than its description suggests. Your organization is adopting AI — or is about to — and making that adoption work is on you.
Three months after most rollouts, the already-enthusiastic use the AI tools daily, while the skeptics — who attended the training and produced an output or two under supervision — quietly return to the workflow they know. That's not resistance.
For anyone tasked with rolling AI out to a skeptical team without panic, mutiny, or a single wasted training session.
You've done the diagnostic work. You know which roles carry the most anxiety, you have a rough sense of your organization's trust score, and you've mapped the prior failures sitting in your team's memory.
You've built a communication architecture. You know your team's fears, you've layered your message across three structural levels, and you've identified the right channels to carry it.
Your last training session ends, the exit tasks are done, and you have a group of people who can use the tool. Now you can turn that competence into adoption you actually measure.
Three weeks into your pilot, someone on the team posts to the company-wide Slack channel — not to their manager, not to you, but to everyone.
You've been given a job harder than the job description suggests. Your organization is adopting AI — or is about to — and you've been tasked, formally or informally, with making that adoption work.
Before you can build a message that addresses your team's concerns, you need to know what those concerns actually are. Most change managers skip this and start communicating before they've listened. These prompts are for your own honest written reflection before you build a formal team-readiness map.
Run this before you draft a single communication. The goal is a role-by-fear matrix for your specific team — not a survey, but a structured thinking tool you fill in from what you already know about each job category, supplemented by a small round of informal conversations.
Your team's readiness is partly a function of their history with you and with your organization. A team that has weathered three "mandatory" software adoptions later abandoned, or a restructuring after a "transformation" initiative, won't respond to enthusiasm. They'll respond to evidence.
Agility at Scale's 2026 framework for AI change management makes a point that applies directly: the end state of AI transformation keeps shifting, so your team is being asked to commit to a change that can't be fully specified in advance. That ambiguity is hard enough to accept when trust is high.

EPUB, PDF, and HTML are included so the book can work on an e-reader, as a designed copy, or as a searchable desk reference.
For e-readers and reading apps.
The designed edition with diagrams and layouts intact.
Searchable, copy-pasteable, and practical as a reference.
Yes. You get the complete edition, including the chapter sequence and internal materials described on this page.
EPUB, PDF, and HTML are included so you can read on an e-reader, keep a designed copy, or use the searchable browser version.
Because this is an instant digital download, broad change-of-mind refunds are not offered after the files have been accessed. Refund requests are reviewed within 7 days for duplicate purchases, accidental purchases before access, access failures we cannot fix, wrong files, corrupted files, or pages that materially misdescribe the book.