Change management
Skill anotb/management-consulting-plugin/skills/change-management
Management consulting skills for Claude Code, Cowork, Codex, and other agents. Strategy, operations, and transformation workflows for the full engagement lifecycle.
npx -y skills add anotb/management-consulting-plugin --skill change-managementAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Designs and runs organizational change programs: transformation planning, stakeholder engagement, resistance management, communication strategy, training design, and adoption measurement. Use when planning or delivering any organizational change (digital transformation, AI adoption, merger integration, culture shift, new operating model, ERP or system rollout) and when the ask is a change approach, stakeholder map, resistance playbook, communication plan, champion network, or adoption scorecard. Diagnoses where adoption stalls and prescribes the intervention rather than issuing generic advice.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
18.0 KB, as published. Nobody here has run it
Change Management
Change is a people problem before it is a process or technology problem. The methodology below covers the full lifecycle: build the case, design the approach, manage resistance, enable adoption, and sustain the new way of working. Diagnose first, then prescribe. Most failed programs skipped the diagnosis and jumped to town halls and training decks.
How to use this skill
Ask for the real inputs before producing anything. You need the change trigger, the affected population, the timeline, the sponsor, and whatever readiness or adoption data exists. If the user has none, say so and mark every number you produce as a directional estimate that needs validation.
When you fill any table in this skill, each cell gets 2-3 sentences of specific reasoning tied to this client's situation. A cell that reads "high" or "communicate more" is a placeholder, not a deliverable. Name the stakeholder, cite the signal you saw, state the intervention and who owns it.
Do not invent adoption rates, timelines, or dollar impacts. When a number is needed to illustrate, label it as an example and flag it for validation. Benchmarks are illustrative and carry their source and context, never presented as authoritative. Use conditional framing ("organizations that reinforce change past go-live tend to hold gains longer") unless the user supplies real firm data.
Choosing the Right Approach
| Situation | Primary Approach | Supporting Elements |
|---|---|---|
| Major organizational transformation | Transformation Execution (5-phase) | Individual adoption, organizational alignment |
| Individual behavior change focus | Individual Adoption Model | Behavioral diagnosis |
| Digital transformation | Combined approach | Digital maturity assessment |
| AI adoption | Individual Adoption plus technology enablement | Agile change methods, job-security messaging |
| Merger integration | Transformation Execution plus culture alignment | Organizational diagnostics |
| Culture change | Transformation Execution | Values-based change |
Pick the row that matches the dominant challenge, then borrow from the others. A digital transformation with heavy behavior change needs the Individual Adoption Model bolted onto the 5-phase execution, not one or the other.
The Individual Adoption Model
People move through five sequential stages. Each stage depends on the one before it. A weak stage caps everything downstream: motivated people with no capability stay stuck, and capable people with no reinforcement revert. Diagnose where the population is actually stuck before prescribing. The most common mistake is prescribing training (a capability fix) when the real gap is motivation.
1. Understanding
Do people know why the change is happening?
Activities: town halls, leadership communications, cascade sessions, FAQ documents, video briefings.
If understanding is low, nothing downstream works. People cannot support what they do not comprehend. Test it directly: ask five people in the affected group to explain the change in their own words. If they cannot, you have a stage-1 problem regardless of how many emails went out.
2. Motivation
Do people want to support the change?
Activities: surface personal benefits, address fears head-on, recognize advocates, secure visible executive sponsorship, engineer early wins people care about.
Understanding without motivation produces informed cynics. They can recite the vision and still resist it. Connect the change to what the specific group actually values (job security, workload, status, mastery), not to enterprise strategy they have no stake in.
3. Capability
Do people know how to operate the new way?
Activities: training programs, job aids, coaching, documentation, role-specific learning paths.
Motivation without capability creates frustrated supporters who want to comply and cannot. Do not announce a change before the enablement is ready. The gap between announcement and capability is where goodwill leaks out.
4. Proficiency
Can people perform effectively, not just correctly?
Activities: hands-on practice, shadowing, pilots, live support, performance coaching.
Knowing how differs from being able to. Every change carries a proficiency dip where output drops before it recovers. Budget for it and tell leaders it is coming, so a temporary dip does not get read as failure and trigger a reversal.
5. Sustainability
How does the change hold once attention moves on?
Activities: recognition, metrics and dashboards, leadership modeling, consequence management, integration into performance systems.
Without reinforcement, people revert to old habits (directional: often within weeks for behaviors under stress, validate against this client's context). Sustainability is where most programs fail, because the team declares victory at go-live and redeploys before the new behavior is anchored.
Transformation Execution Framework
For large-scale transformation, work through five phases from mobilization to embedding. The framework is linear on paper and iterative in practice: expect to revisit earlier phases when resistance surfaces.
Phase 1: Mobilize
Build urgency and assemble a guiding coalition with the power and credibility to lead.
Urgency: Make the case with market pressure, competitive threats, customer data, and internal opportunity cost. Complacency is the primary barrier here. If the organization is comfortable, manufacture legitimate discomfort with real data, not manufactured crisis (people see through fake urgency and trust erodes).
Guiding coalition: Assemble people with position power, expertise, credibility, and leadership ability. The coalition needs enough combined influence to drive change without leaning on formal authority alone. Staff it with:
- Executive champion for visible sponsorship
- Change leader for operational drive
- Technical leads for feasibility credibility
- Cultural leaders who own the informal influence networks
Coalition activities: standing alignment cadence, capability building inside the coalition, shared vision development.
Phase 2: Envision and Communicate
Develop a specific vision and make sure every stakeholder can repeat it.
A useful vision guides decisions. "World-class operations" is not a vision. "Same-day order fulfillment at 99.5% accuracy" is, because a team can tell whether a given choice moves toward it.
Vision components: what is changing, why it matters, how the organization gets there, when the milestones land.
Communication principles:
- Consistent message across every channel
- Two-way dialogue, not broadcast
- Leaders model what they communicate
- Multiple formats for different audiences
- Repetition matters. People need to hear a message several times before it registers (commonly cited as 5-7, directional, treat as a planning heuristic not a law)
Phase 3: Enable and Deliver Quick Wins
Remove barriers, build capability, and generate visible early wins.
Barrier removal: Find and fix structural misalignment, skills gaps, legacy systems, leadership resistance, and incentive conflict. If the performance system still rewards old behavior, the new behavior will not hold. This is the single most overlooked barrier: teams are told to change while their bonus still pays for the old way.
Quick wins: Select wins that are visible to many, clearly caused by the change, and unambiguous. They build credibility, create momentum, and hand skeptics evidence the change is real. A weak or contested "win" does more harm than no win, because it gives resisters ammunition.
Phase 4: Accelerate
Use the credibility from early wins to expand and deepen adoption.
- Expand the change team and promote proven change agents
- Realign policies, processes, and systems to the new way of working
- Build advanced capability
- Deepen engagement across the wider organization
- Scale pilots to broader teams
This is where programs stall. Early wins create a false sense of completion, and sponsors start looking at the next initiative. The unglamorous work of systemic alignment (incentives, processes, systems) happens here and rarely gets the airtime it needs. Guard the runway.
Phase 5: Embed in Culture
Anchor the change in how the organization hires, promotes, measures, and tells its story.
Embedding activities:
- Align leadership selection and development with the new values
- Rewire systems, processes, and incentives to reinforce new behavior
- Build the change into onboarding and performance management
- Recognize sustained adoption, not just early adoption
Signals that embedding worked:
- New behavior is the default, not the exception
- Organizational stories reflect the change
- Hiring and promotion criteria reflect the new values
- Metrics track the new outcomes
Change Impact Assessment
Assess what you are dealing with before designing anything.
Change profile dimensions:
- Scope: enterprise, functional, or team
- Depth: process, tool, behavior, or culture (culture is hardest and slowest)
- Population size affected
- Urgency: how fast this must happen and why
Stakeholder readiness: For each affected group, assess impact level, change complexity, and current readiness (ready, uncertain, or resistant). A high-impact group sitting at resistant is where your program lives or dies. Weight your attention there.
Stakeholder Analysis and Management
Stakeholder Mapping
Map stakeholders on influence (ability to affect outcomes) and interest (degree to which they are affected).
| Category | Definition | Approach |
|---|---|---|
| Manage Closely | High influence, high interest | Engage deeply, co-create the solution |
| Keep Satisfied | High influence, low interest | Keep informed, do not overwhelm |
| Keep Informed | Low influence, high interest | Communicate regularly, give a voice |
| Monitor | Low influence, low interest | Minimal effort, watch for movement |
For each stakeholder or group, record current state (awareness and support level), desired state, and the specific move that closes the gap. Name the person who owns that move. A map with no owners is a diagram, not a plan.
Change Champion Network
Champions are the force multiplier. They operate at peer level, which gives them a credibility senior leaders cannot buy: a colleague saying "this actually works" outperforms any executive email.
Champion responsibilities:
- Model the new behavior in daily work
- Coach and support peers
- Surface concerns and resistance early, before it hardens
- Celebrate wins inside their own teams
Champions need real investment: training, materials, protected time, and visible recognition from leadership. A champion network with no time allocation is a volunteer scheme that dies in the first busy week.
Resistance Management
Resistance is information. It tells you what you have not addressed yet. Treat it as a diagnostic signal, not an obstacle to overpower. The teams pushing back hardest often understand the operational reality better than the program does.
Common Sources of Resistance
| Source | Signs | Response |
|---|---|---|
| Fear of job loss | Withdrawal, negativity, rumor | Transparent communication, concrete reskilling commitments |
| Lack of skills | Reluctance, anxiety, avoidance | Training, coaching, hands-on support |
| Habit and comfort | Old behaviors persist quietly | Practice opportunities, reminders, nudges |
| Loss of status or influence | Undermining, territorial behavior | New roles, recognition, genuine involvement |
| Lack of trust | Cynicism, "this too shall pass" | Consistent follow-through, visible credibility building |
Resistance Response Playbook
| Signal | Indicator | Response | Escalation |
|---|---|---|---|
| Vocal opposition | Direct pushback in meetings | Acknowledge the concern, move it to a 1:1, address the root cause | If persistent: sponsor intervention |
| Passive non-compliance | Low adoption metrics, quiet non-use | Targeted coaching, peer support, find the real barrier | If systemic: adjust the approach itself |
| Shadow processes | Teams running the old method in parallel | Understand why, fix the gap in the new process | If widespread: pause and fix before pushing |
| Influencer resistance | A key voice undermining the change | Private conversation, address concerns, co-create the fix | If unresolved: sponsor engagement |
When you apply this table, name the actual person or group, quote the signal you observed, and commit to a next step with an owner and a date. Passive non-compliance in a 40-person operations team is a different problem from one influential director going quiet, and the response differs.
Communication Strategy
Communication Planning
Design by audience, not by channel. Each audience needs a core message, the right channel, a defined frequency, and a named owner.
Communication timeline:
- Announce: the why and the vision (all staff, town hall)
- Educate: the detail and what it means for each group (affected teams, working sessions)
- Reinforce: progress, course corrections, sustained visibility (all staff, ongoing)
Principles:
- Over-communicate. If you think you have communicated enough, you have not.
- Two-way channels beat broadcast.
- Managers are the most trusted channel for their own teams. Equip them first.
- Connect every message to "what this means for me." Strategy language does not move a frontline team.
AI and Digital Change Communication
AI and digital transformations carry a specific fear (my job) and demand direct messaging on it:
- Address job security proactively, before the rumor mill does
- Show how AI augments the role rather than replacing the person, with concrete examples from their work
- Commit visibly to learning and development
- Show how employee input shapes the strategy
- Be transparent about where AI is used and where it fails
- Keep human judgment explicitly central to decisions
Vague reassurance backfires here. If you cannot promise no job losses, do not imply it. State what you can commit to and be specific about it.
Training and Enablement
Training Design
Assess current versus target proficiency for each skill area and each affected group. Prioritize by gap size times business impact, so a large gap on a low-stakes skill does not crowd out a moderate gap on a critical one.
Approaches:
- Role-based learning paths keyed to current skill level
- Microlearning for just-in-time application
- Hands-on practice in a sandbox, essential for technology change
- Peer learning networks and communities of practice
- Coaching for leaders who have to role-model the new behavior
Training Timing
Do not train too early (people forget) or too late (people feel abandoned at go-live). The window is close enough to go-live that skills transfer straight into the work, with refreshers in the weeks after. Front-load nothing that the population cannot practice within a week or two.
Adoption Measurement
Measure leading indicators to steer and lagging indicators to confirm. Leading indicators buy you time to correct before the lagging numbers go bad.
Leading Indicators
- Share of employees aware of the change
- Share of managers prepared to lead it
- Training completion rate
- Change saturation: are people absorbing too many concurrent changes to absorb this one?
Lagging Indicators
- Adoption rate: actual usage of the new tool, process, or behavior
- Proficiency: quality of performance in the new way
- Business outcome: the reason the change was funded
- Stakeholder satisfaction
Tie the business outcome back to the original case for change. If the program cannot show movement on the metric that justified it, adoption of the tool is activity, not success.
Pulse Survey Questions
Short, frequent surveys take the temperature between formal checkpoints:
- I understand why this change is happening.
- I have the tools and training I need to succeed.
- My manager supports me through this change.
- I can see the benefits of the new way of working.
- I know where to go for help.
Each maps to a stage of the Individual Adoption Model. A low score on question 1 is an understanding gap. A low score on 4 is motivation. Read the pattern, not just the average.
Reinforcement Mechanisms
| Mechanism | Timing (directional, adjust to program pace) |
|---|---|
| Quick-wins celebration | Weeks 2-4 |
| Public recognition of adopters | Ongoing |
| KPI alignment to new behaviors | Month 2+ |
| Coaching for struggling teams | Months 2-6 |
| Integration into standard operating procedures | Month 3+ |
Treat the timing column as a starting template, not a schedule. A 12-week rollout compresses all of it. Anchor the actual dates to this program's go-live.
Principles
- Change management is a discipline, not an afterthought. Budget it, staff it, track it.
- Every change is a people change first, then a process or technology change.
- Resistance is natural and useful. Plan for it. Do not be surprised by it.
- Executive sponsorship must be visible and consistent. A sponsor who delegates everything is not sponsoring.
- Communication alone is not enough. Training alone is not enough. Both without reinforcement still fail.
- You cannot change people. You can only build the conditions for them to change themselves.
- Start early. Change takes longer than the project plan assumes.
- Celebrate wins. Do not declare victory before the behavior is embedded.