change-management
Change Management for 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.
Change Management Frameworks
ADKAR Model (Prosci)
Best for: Individual and organizational change, managing resistance, tracking adoption
- Awareness: Do people understand why change is needed?
- Desire: Do they want to participate and support it?
- Knowledge: Do they know how to make the change?
- Ability: Can they demonstrate the new behaviors/processes?
- Reinforcement: Will the change stick and become the new normal?
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.
Kotter's 8-Step Change Model
Best for: Large-scale enterprise transformation, strategic change programs
- Create sense of urgency (external threats, competitive pressure)
- Build guiding coalition (leadership team, influencers, credible skeptics)
- Form strategic vision and initiatives
- Enlist volunteer army (empower change agents across organization)
- Remove obstacles (policy, governance, resource constraints)
- Generate short-term wins (visible successes that validate direction)
- Sustain acceleration (continuously reinforce, accelerate momentum)
- Institute change (embed in culture, reinforce through systems)
Kotter is most effective when executive alignment is strong and you have 2-3 year implementation horizons.
Prosci's 3 Pillars
- Sponsorship: Executive leadership driving and modeling change
- Communication: Audience-specific messaging, frequent and consistent
- Coaching: One-on-one support, manager enablement, peer support networks
Use Prosci when designing the OCM workstream. Every change initiative should address all three pillars.
Satir Change Model
Best for: Understanding emotional dynamics and resistance
- Late status quo: things are stable
- Foreign element: disruption introduced
- Chaos: confusion, resistance, emotional dip (performance may temporarily worsen)
- Integration: new dynamics understood, confidence building
- New status quo: change embedded, often with higher performance
This framework helps teams understand that resistance and chaos are expected and normal, not failures. Manage expectations accordingly.
Stakeholder Analysis and Mapping
Stakeholder Mapping Framework
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 |
Stakeholder Assessment Template
For each stakeholder group, document:
- Role: Who are they? What functions do they lead?
- Current State: What do they currently do? What systems do they use?
- Future State Impact: What will change for them? What new skills/processes required?
- Influence Level: Can they derail the change? Accelerate it?
- Interest Level: Do they care about this change? Is it a threat or opportunity?
- Baseline Position: Champion, supporter, fence-sitter, skeptic, or active resistor?
- Key Concerns: What are their primary fears/objections?
- Motivators: What matters most to them? (career growth, team stability, customer impact, efficiency, autonomy)
- Engagement Plan: How will you involve them? What's their role in implementation?
Identifying Champions and Resistors
Champions (cultivate and empower):
- Credible within their peer group
- Understand the business case
- Have something to gain (career growth, efficiency, improved capability)
- Willing to model new behaviors publicly
- Can articulate the "why" to skeptics
Resistors (understand, engage, or isolate):
- Fear loss: status, control, competence, relationships
- Question the business case or approach
- Have influence over others
- Resistant to past changes or cynical about consulting
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.
References
For detailed templates and guidance: references/change-management-reference.md
- Impact Assessment
- Communication Planning
- Training Design
- Resistance Management
- Adoption Tracking
- Readiness Assessment
Examples
Input: "Our company is migrating from Salesforce to HubSpot. Help us manage the change."
Change management plan output:
- Stakeholder map: 3 sponsors (C-suite), 12 champions (sales managers), 120 affected users
- Impact assessment: High impact on Sales (daily tool), Medium on Marketing (reporting), Low on Finance
- Communication plan: All-hands announcement → Team lead briefings → User training invites → Go-live FAQ
- Training design: 4-hour hands-on workshop + 30-min quick-start video + reference card
- Adoption KPIs: 90% login rate by Week 2, <5 help desk tickets/day by Week 4
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.
More from lauraflorentin/skills-marketplace
multi-agent-collaboration
A structural pattern where multiple specialized agents communicate and coordinate to solve a problem that is too complex for a single agent. Use when user asks to "build a multi-agent system", "agents working together", "agent collaboration", or mentions team of agents, distributed agents, or swarm.
21reflection
A recursive pattern where an agent evaluates and critiques its own output to iteratively improve quality and catch errors. Use when user asks to "add self-reflection", "agent introspection", "self-critique", or mentions self-evaluation, meta-cognition, or quality self-assessment.
18human-in-the-loop
A hybrid pattern where the system pauses execution to request human approval, input, or disambiguation before proceeding with critical actions. Use when user asks to "add human approval", "require human review", "human-in-the-loop", or mentions approval workflows, human oversight, or escalation.
16planning
A high-level cognitive pattern where an agent formulates a structured sequence of actions (a plan) before executing any of them, ensuring goal-directed behavior. Use when user asks to "add planning to my agent", "task planning", "agent planning", or mentions plan generation, plan execution, or step-by-step planning.
14parallelization
A concurrency pattern where multiple agent tasks are executed at the same time to speed up processing or gather diverse perspectives. Use when user asks to "run agents in parallel", "parallelize tasks", "concurrent execution", or mentions parallel processing, fan-out, or batch execution.
13routing
A control flow pattern where a central component classifies an input request and directs it to the most appropriate specialized agent or tool. Use when user asks to "route between agents", "agent routing", "task dispatch", or mentions classifier routing, intent detection, or agent selection.
12