Resistance Playbook
Resistance Playbook
Diagnose. Intervene. Convert.
The problem
You have two resistant regional managers. Sarah has been vocal in meetings for weeks, articulate, specific, and influential. Marcus is quieter but you have heard he is privately telling his store managers to keep their Excel rosters running as a backup. Your change agent network is thin in both regions. You are thinking about bringing one or both of them into the Dayforce testing sessions, but you are not sure if that is the right play for both of them or just one.
This is exactly the kind of high-stakes, time-pressured scenario that Resistance Playbook was built for. Not a generic prompt. A specialist tool with the methodology, the frameworks, and the professional judgment encoded into every output.
What makes this different
Eight Behavior Patterns
Identifies the specific resistance pattern at play: from Silent Withdrawal to Active Sabotage. Your intervention matches the actual behavior, not a guess.
Branching Conversation Playbooks
Full ‘what to say if they say X’ logic trees. Managers get scripted openers, follow-ups for every response, and clear escalation triggers.
The Escalation Compass™
When to handle yourself, when to coach, when to escalate, and when to recruit the resistor as an advocate. Clear decision logic, not guesswork.
Dual-Audience Mode
Manager mode gives direct, practical conversation tools. Practitioner mode gives deeper diagnostic frameworks and intervention strategies.
See it in action
You have two resistant regional managers. Sarah has been vocal in meetings for weeks, articulate, specific, and influential. Marcus is quieter but you have heard he is privately telling his store managers to keep their Excel rosters running as a backup. Your change agent network is thin in both regions. You are thinking about bringing one or both of them into the Dayforce testing sessions, but you are not sure if that is the right play for both of them or just one.
Example prompt
I have two resistant regional managers: Sarah, a vocal objector with 14 years of experience who raises specific operational challenges in every meeting, and Marcus, who is quietly telling his store managers to keep Excel backups running just in case. I am thinking about bringing one or both of them into the system testing sessions with the Dayforce config team. Is that the right play for both of them? What would you actually do?
What standard Claude produces
Sarah: Yes, bring her in. She’s your best asset.
She's not resistant; she's engaged. Fourteen years of operational knowledge and a habit of raising specific challenges is exactly what a config team needs. She's already doing free QA work; you just haven't formalized it.
• Reframe her role before the session: you're not asking her to "try" the system, you're asking her to break it. This gives her status and agency rather than making her feel managed.
• Make sure the config team takes her challenges seriously in real time. If she raises something and it gets hand-waved, you'll lose her permanently.
• Debrief with her after. If her issues were resolved, she becomes a credible advocate to other managers.
Marcus: Don't bring him into testing yet. Solve the actual problem first.
His Excel backups aren't about Excel; they're about fear of being stranded with no fallback if something goes wrong. Testing sessions won't fix that; they'll just give him a more informed version of the same anxiety.
• Have a private conversation first. Don't make him feel caught. Ask directly: what would need to be true for you to feel safe letting go of the parallel process?
• Address the specific fear: a data migration confirmation, a rollback plan, or a defined escalation path during go-live.
• Then consider a testing session, framed around him validating that the safeguards he asked for actually work.
Sarah's resistance is public and content-based; meet it with inclusion. Marcus's is private and trust-based; meet it with a direct conversation first.
Good diagnosis. High-level action plan for each candidate. No further plan creation.
What Resistance Playbook produces
Sarah: Yes, she's a strong Conversion Play candidate.
Vocal Objector, 14 years' experience, raising specific operational challenges. That's substantive resistance, not emotional rejection. She hits all five conversion criteria: peer influence, technical curiosity, quality orientation, right behavior pattern, and willingness to engage.
The invitation framing matters. Don't say "we want to get you on board." Say: "Your job isn't to approve it; it's to stress-test it." That fits her identity and doesn't ask her to change her position before she's seen the evidence. Brief the config team first; if they dismiss her questions, the play collapses.
Marcus: Not yet.
His "just in case" language is the tell. This isn't a quality concern; it's a Trust Deficit. He doesn't believe go-live will hold, so he's building a safety net. Dropping him into testing sessions before you understand why he's hedging means he either finds more ammunition or sits there politely while the Excel backups keep running.
He needs a 1:1 first. Open with: "When you think about this going live, what's the scenario you're most worried about?" Then stop talking. Once you know what specific failure he's protecting against, you can decide whether the Conversion Play fits or whether there's a structural concern that needs addressing upstream.
Bottom line: Sarah goes into the next testing session. Marcus gets a conversation first.
Root cause identified. Two different actions. Offer of guidance for additional engagement strategies done in seconds.
Notice how the Resistance Playbook conducts the diagnostic and offers additional deliverables that it will create based on your need?
Want to see the full output? Download your free Claude skill →
The difference specialist methodology makes
Same scenario. Same prompt context. Different results.
Get Resistance Playbook
All sales are final. We encourage you to try the free Change Communication Audit before purchasing so you can evaluate the quality firsthand.
What you get
Everything you need to deploy this skill inside your own Claude account today. No subscriptions. No platform lock-in. Yours to keep.
- The Skill File, optimized for Claude, ready to deploy in minutes
- Quick-Start Prompt Guide, pre-built prompts for common resistance scenarios
- Behavior Pattern Reference Card, all eight patterns at a glance
- Downloadable .docx report generation
- 80+ languages. Zero extra cost.
Who it’s for
Built for practitioners who do the work, not observers who talk about it.
Change manager
Structured resistance diagnosis and intervention strategies for every pattern you encounter.
Middle manager
Practical, scripted conversation tools for the difficult conversations you’re dreading.
HR business partner
Evidence-based resistance frameworks that go beyond ‘communicate more’.
External consultant
Consistent diagnostic methodology across every client engagement.
80+ languages.
Zero extra cost.
80+
Languages
100%
Cultural context
$0
Extra cost
This skill works in over 80 languages out of the box. Prompt in English, get output in Japanese. Prompt in Portuguese, get output in Arabic.
Cultural context is maintained, not just word translation. The skill adjusts its frameworks, its tone, and its output for the culture you’re working in, not just the language.
No add-ons. No language packs. It just works.