Organizational change management (OCM) for consulting engagements — stakeholder mapping, impact assessment, communication planning, training design, adoption tracking, and resistance management. Use this skill whenever change management, OCM, stakeholder mapping, adoption, resistance, communication plans, training rollouts, or organizational readiness come up. Use when user asks to "plan change management", "change readiness assessment", "stakeholder adoption plan", or mentions organizational change, resistance management, or transition planning.
How this skill is triggered — by the user, by Claude, or both
Slash command
/management-consulting:change-managementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Organizational change management (OCM) is the discipline of guiding people, teams, and organizations through transformation. Without structured OCM, even technically sound recommendations fail due to resistance, misalignment, or inadequate preparation. This skill covers frameworks, techniques, and deliverables for embedding change management into consulting engagements.
Organizational change management (OCM) is the discipline of guiding people, teams, and organizations through transformation. Without structured OCM, even technically sound recommendations fail due to resistance, misalignment, or inadequate preparation. This skill covers frameworks, techniques, and deliverables for embedding change management into consulting engagements.
Best for: Individual and organizational change, managing resistance, tracking adoption
Use ADKAR when you need to diagnose where change is breaking down. If adoption is stalling at the "Knowledge" phase, training is the lever. If it's failing at "Reinforcement," governance and accountability systems need strengthening.
Best for: Large-scale enterprise transformation, strategic change programs
Kotter is most effective when executive alignment is strong and you have 2-3 year implementation horizons.
Use Prosci when designing the OCM workstream. Every change initiative should address all three pillars.
Best for: Understanding emotional dynamics and resistance
This framework helps teams understand that resistance and chaos are expected and normal, not failures. Manage expectations accordingly.
Create a 2x2 matrix: Power/Influence (high/low) × Interest/Impact (high/low)
| Quadrant | Profile | Engagement Strategy |
|---|---|---|
| High Power, High Interest | Key Players | Full engagement, frequent communication, co-design, governance roles |
| High Power, Low Interest | Keep Satisfied | Regular briefings, address concerns quickly, prevent opposition |
| Low Power, High Interest | Keep Informed | Involvement in design, clear messaging, opportunities to shape |
| Low Power, Low Interest | Monitor | Periodic updates, minimal formal engagement |
For each stakeholder group, document:
Champions (cultivate and empower):
Resistors (understand, engage, or isolate):
Strategy: Don't ignore resistors. Engage them early. Often their concerns are legitimate and will surface later anyway. Sometimes their objections improve the solution. If they remain opposed, at least they understand why change is happening.
For detailed templates and guidance: references/change-management-reference.md
Input: "Our company is migrating from Salesforce to HubSpot. Help us manage the change."
Change management plan output:
Resistance flag: UK sales team identified as high-resistance — schedule dedicated session with their regional manager.
Input: "Our post-merger integration is facing significant cultural resistance."
Output: Resistance analysis identifying root causes (uncertainty about role changes, loss of legacy brand identity), targeted interventions (town halls, dedicated Q&A channel, 1-1 manager conversations), and a 90-day adoption tracking calendar with milestone check-ins.
npx claudepluginhub lauraflorentin/skills-marketplace --plugin management-consultingGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.