Team Communication Scripts (By Resistance Type)

When you announce an AI implementation or workflow change, three types of resistance surface immediately. Fear-based ("I'll lose my job"), control-based ("You're taking away my autonomy"), and skepticism-based ("This won't work here"). Each requires a different script.

Use these talking points verbatim or adapt them to your firm's context. The goal is to address the root concern directly, not to paper over it with generic reassurance.

This shows up as: "Will AI replace me?" "I don't know how to use this." "What if I can't keep up?"

The person is worried about job security, skill obsolescence, or being left behind. They need concrete reassurance and a clear path forward.

What to Say

Opening acknowledgment: "I hear you saying you're worried about [specific concern]. That's a legitimate question, and I want to address it directly."

Job security reassurance (be specific): "Your role isn't being eliminated. Here's what's changing: [specific tasks being automated]. Here's what stays with you: [client relationship management, judgment calls, strategic work]. We're removing the repetitive work so you can focus on the parts of your job that require your expertise."

Skill development commitment: "We're providing [specific training program] starting [date]. You'll have [X hours] of paid time to complete it. I'll check in with you weekly during the first month to answer questions and troubleshoot issues."

Timeline transparency: "You'll have [specific timeframe] to get comfortable with this before we expect full adoption. We're not flipping a switch overnight."

Example script for associate attorney: "You're asking if document review AI means we need fewer associates. No. It means you'll spend less time on first-pass review and more time on the analysis that actually develops your legal judgment. We're still billing the same hours to clients, but you'll be doing higher-value work. Starting next Monday, you'll have access to [tool name] and a 4-hour training module. I'll pair you with Sarah, who's been using it for two months, for the first week."

What NOT to Say

Don't use vague reassurance: "Don't worry, everything will be fine." (This dismisses the concern without addressing it.)

Don't make it about their attitude: "You just need to be more open to change." (This implies the problem is their mindset, not a legitimate concern.)

Don't threaten: "Well, if you don't adapt, you'll be left behind." (Fear-mongering destroys trust.)

Don't set unrealistic timelines: "You'll pick this up in a day or two." (Underestimating the learning curve sets them up for failure.)

This shows up as: "I have my own system that works." "Why wasn't I consulted?" "This feels like micromanagement."

The person values autonomy and feels the change is being imposed on them. They need involvement and clarity on what they still control.

What to Say

Acknowledge their expertise: "You've been doing [task] successfully for [X years]. I'm not questioning your results. I'm asking you to try a different method because [specific business reason]."

Clarify what they still control: "You still decide [specific decisions]. What's changing is [specific process]. You'll have full discretion over [specific area]."

Invite their input: "I need your expertise to make this work. What concerns do you have about [specific aspect]? What would make this easier to implement in your workflow?"

Offer choice where possible: "You can choose between [Option A] and [Option B] for [specific task]. Both meet the requirement that [specific outcome]. Which fits your workflow better?"

Example script for senior accountant: "You've built a reconciliation process that's worked for five years. I'm not saying it's wrong. I'm saying the firm is standardizing on [tool name] so we can cross-train staff and reduce key-person risk. You'll still decide how to handle exceptions and judgment calls. The tool handles the mechanical matching. I want your input on the exception workflow. Can you walk me through your current process so we can replicate the parts that matter?"

What NOT to Say

Don't impose without explanation: "This is the new process. Just follow it." (This triggers control resistance immediately.)

Don't dismiss their methods: "Your way is outdated." (This insults their competence.)

Don't micromanage the transition: "You need to do it exactly like this, step by step." (This removes all autonomy.)

Don't make unilateral decisions: "I've already decided. I'm just informing you." (This guarantees resentment.)

This shows up as: "We tried something like this before and it failed." "This is just the latest fad." "I don't see how this solves our actual problem."

The person doubts the change will work or is necessary. They need evidence, not enthusiasm.

What to Say

State the specific problem: "We're implementing this because [specific metric] is below target. Right now, [specific task] takes [X hours] per [unit]. We need to reduce that to [Y hours] to stay competitive."

Show the evidence: "[Competitor/peer firm] implemented this and reduced [specific metric] by [X%]. Here's their case study. [Client] is now requiring [specific capability] in their RFPs. We've lost [X] opportunities because we couldn't deliver it."

Address past failures directly: "You're right that we tried [previous initiative] in [year] and it didn't stick. Here's what's different this time: [specific change in approach, leadership commitment, resource allocation]."

Commit to measurement: "We'll track [specific metrics] weekly. If we don't see [specific improvement] by [date], we'll reassess. I'm not asking you to take this on faith. I'm asking you to test it with me."

Example script for consulting partner: "You're skeptical because we rolled out [previous tool] three years ago and no one uses it. Fair. That failed because we didn't integrate it into the workflow and we didn't train anyone. This time, [tool name] is mandatory for [specific process] starting [date]. Everyone, including me, is using it. We're tracking [specific metric] in our Monday meetings. If it's not saving us [X hours] per project by end of Q2, we'll kill it. But we're not half-implementing this one."

What NOT to Say

Don't oversell: "This will revolutionize everything!" (Hyperbole triggers skepticism.)

Don't ignore past failures: "That was different." (Without explaining how, this sounds defensive.)

Don't ask them to trust you: "Just trust me on this." (Skeptics need data, not faith.)

Don't hide the challenges: "It'll be seamless." (Nothing is seamless. Lying about difficulty destroys credibility.)

| Signal | Resistance Type | Lead With | |--------|----------------|-----------| | "Will I lose my job?" | Fear | Job security specifics + training plan | | "I don't know how to use this." | Fear | Step-by-step learning path + support | | "Why wasn't I consulted?" | Control | Request for input + decision authority | | "I have my own system." | Control | Acknowledge expertise + clarify what stays | | "We tried this before." | Skepticism | What's different this time + evidence | | "I don't see the point." | Skepticism | Specific problem + measurable outcome |

Record these conversations. Not literally, but document who raised which concerns and what you committed to. Follow up within one week with the specific resource, timeline, or data point you promised.

If you can't answer a question on the spot, say: "I don't know. I'll find out and get back to you by [specific date]." Then do it.

The worst response to any resistance type is silence or delay. Address it immediately, even if your answer is incomplete.