This lesson is being recorded

Every video of this course is being uploaded to my YouTube channel. Subscribe so you do not miss it.

Bruno AshfordBruno Ashford @brunoashfordSubscribe

Module 13 · Lesson 13.6 · 10 min

Change Management

Address fear of replacement openly and turn your team into champions of the new way of working.

Module 13
Rolling Out to Your Team

From one owner's laptop to a company system

Bruno Ashford
Bruno Ashford · Module 1301 / 12
Why rollouts fail
Sending your team a link is not a rollout. It is a lottery.
Bruno Ashford
Bruno Ashford · Module 1302 / 12
The rollout

Three waves in 30 days

  1. 1Pilot groupTwo or three credible people
  2. 2First departmentProven skills only
  3. 3Whole teamWhen no safety issue is open
Bruno Ashford · Module 1303 / 12
Lesson 13.1

From owner to team

Share what is proven, not everything you built.

  • Company knowledge in shared CLAUDE.md
  • Personal preferences stay personal
  • Policy before tools
  • Credibility beats technical skill
Bruno Ashford · Module 1304 / 12
Lesson 13.2

What a plugin bundles

One folder, one install, one version for everyone.

  • Skills in skills/
  • Subagents in agents/
  • Hooks in hooks/hooks.json
  • Connectors in .mcp.json
Bruno Ashford · Module 1305 / 12
Lesson 13.2

The plugin commands

StepCommand
Check itclaude plugin validate ./acme-ops
Test itclaude --plugin-dir ./acme-ops
Add marketplaceclaude plugin marketplace add org/repo
Installclaude plugin install acme-ops@acme-tools
Manage/plugin
Bruno Ashford · Module 1306 / 12
Lesson 13.3

Four roles

  1. BBuilderCreates and edits skills
  2. AApproverSigns off changes and sensitive output
  3. UUserRuns skills daily
  4. MMaintainerKeeps versions and CLAUDE.md current
Bruno Ashford · Module 1307 / 12
The RACI rule
Two people accountable means nobody is accountable.
Bruno Ashford
Bruno Ashford · Module 1308 / 12
Lesson 13.4

30 days, 15 minutes a day

WeekFocus
1Install and first real win
2Two tasks from their own week
3Verification habits and pairing
4Contribute one improvement back
Bruno Ashford · Module 1309 / 12
Lesson 13.5: starting targets, adjust to your business

Adoption by day 30

80%use a skill 3+ times a week
3.5 / 5average confidence
< 15%rework rate
Bruno Ashford · Module 1310 / 12
Lesson 13.6

Change management

Fear goes underground if you ignore it.

  • Say clearly what AI is for
  • Link tools to real frustrations
  • Make champions visible
  • Ask resisters what worries them
Bruno Ashford · Module 1311 / 12
Recap
Package what works, name who owns it, train on real work and measure every week.
Bruno Ashford
Bruno Ashford · Module 1312 / 12
01 / 12

Use ← → to move. The marker highlights text and the pencil draws on the slide; navigation locks while you annotate. Undo removes the last mark, Esc exits.

1Say the quiet part out loud

In the kickoff, tell the team directly what AI is for in your business and what it is not for. If you have no plan to cut roles, say so. If roles will change, say how, and what support people will get. Vague reassurance creates more fear than a clear answer.

2Show what people gain

Connect the tools to each person's frustrations: the report nobody likes writing, the chasing, the copy and paste. When people see the tool taking away the worst part of their week, resistance drops quickly.

3Write your change message

Use Claude to draft a kickoff message in your own voice, then edit it until it sounds like you. Keep it short, honest and specific.

Prompt for Claude
Using our company CLAUDE.md for tone, draft a short kickoff message (under 250 words) from me to the team announcing our AI rollout. Say clearly what the tools are for, that no roles are being cut because of this project, what each team gains, the 30-day plan, the pilot group, and how anyone can raise concerns privately. Plain language, no hype, no jargon.
4Create champions and celebrate wins

Give your pilot group a visible role: they help others and suggest improvements. Share one small win every week in your team meeting, with names and hours saved. Recognition spreads adoption faster than any mandate.

5Handle resistance with curiosity

When someone resists, ask what they are worried about before you push. Often it is a real issue: the skill gets their client wrong, or they fear being blamed for AI mistakes. Fix the issue or clarify accountability, and most resistance disappears.

Some of your team are scared. They read the headlines about AI replacing jobs, and then their boss starts talking about AI agents. If you do not address it, the fear goes underground: people slow-walk the rollout, find reasons the tools do not work, and keep doing it the old way.

The truth is simpler and better. In most small businesses, the goal is not fewer people, it is the same people doing more valuable work. But you have to say it clearly, mean it, and show it.

Key points

  • Address fear of replacement directly and early.
  • Link each tool to a frustration people already have.
  • Champions and visible wins spread adoption faster than mandates.
  • Resistance often hides a real, fixable issue.

Avoid

  • Assuming silence means agreement.
  • Promising no changes when you are not sure, and losing trust later.
  • Celebrating only speed, never the people behind the wins.
  • Treating resisters as problems instead of sources of information.
Real-world example: a law firm

A 15 person law firm's senior paralegal openly opposed the rollout, worried that drafting tools would make her role redundant. The managing partner met her privately, explained that the aim was to remove admin so paralegals could do more client work, and asked her to lead the review of all AI-drafted documents. She became the firm's strongest champion, and her review standards became the verification checklist everyone uses.

Bruno Ashford Subscribe