change-management-skill
Organisational change management with stakeholder analysis, communication planning, and adoption tracking. Use when rolling out a new process, a tool migration, or an organisational restructure. Trigger with "manage change for", "change management plan", "how do we roll out [change]".
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- change-management-skill
- description
- Organisational change management with stakeholder analysis, communication planning, and adoption tracking. Use when rolling out a new process, a tool migration, or an organisational restructure. Trigger with "manage change for", "change management plan", "how do we roll out [change]".
03 SKILL.md 正文
Change Management Skill
Plan and run organisational change — stakeholder analysis, communication planning, training design, and adoption measurement. The skill carries people and process through the transition, from first announcement to durable embedding.
Where the Data Comes From
| Source | What It Adds |
|---|---|
| HR / org system via MCP (e.g. HubSpot, Workday, BambooHR) | Team structures, reporting lines, affected roles, contact details |
| Project tracker via MCP (e.g. Asana, Monday, Jira, Notion) | Rollout tasks, milestone status, owner assignments |
| companyRAG collections / file upload | Stakeholder lists, prior change plans, survey results, training materials |
No connected source? Provide the data in chat or upload the relevant files — the skill works the same way.
Change Impact Assessment
Before planning, assess the scope and nature of the change. This determines the intensity of the change management effort.
Impact Dimensions
Score each dimension from the user's description of the change:
| Dimension | Low Impact | Medium Impact | High Impact |
|---|---|---|---|
| People affected | Single team | Multiple teams or department | Cross-functional or organisation-wide |
| Process change | Minor adjustment to existing workflow | New workflow replacing existing one | Fundamental redesign of how work is done |
| Technology change | Update within existing tool | New tool for existing process | New platform changing multiple workflows |
| Organisational structure | Role adjustments within team | Team restructure | Departmental or reporting line changes |
| Skills required | Existing skills sufficient | Moderate upskilling needed | Significant reskilling or new capabilities |
| Timeline pressure | Flexible timeline | Fixed deadline with buffer | Hard deadline, regulatory, or contractual |
Change Intensity Classification
| Classification | Criteria | Change Management Effort |
|---|---|---|
| Incremental | Low impact across most dimensions | Lightweight — communication + quick-reference guide |
| Transitional | Medium impact on 2+ dimensions | Moderate — full stakeholder analysis, training plan, adoption tracking |
| Transformational | High impact on 3+ dimensions | Intensive — dedicated change lead, phased rollout, sustained reinforcement |
The intensity classification determines how deeply to apply each section of this skill. Incremental changes do not require the full methodology; transformational changes require every element.
Stakeholder Analysis
Stakeholder Identification
Map all individuals and groups affected by or influencing the change:
| Stakeholder | Role in Change | Impact Level | Influence Level | Current Stance | Desired Stance |
|---|---|---|---|---|---|
| [Name/Group] | Sponsor / Champion / Affected / Blocker | High / Medium / Low | High / Medium / Low | Advocate / Supportive / Neutral / Resistant / Hostile | [target stance] |
Influence-Impact Matrix
Plot stakeholders on two axes to determine engagement strategy:
| High Influence | Low Influence | |
|---|---|---|
| High Impact | Manage closely — regular 1:1 engagement, early involvement in design, address concerns proactively | Keep informed — regular communication, feedback channels, training priority |
| Low Impact | Keep satisfied — periodic updates, consult on decisions within their domain | Monitor — general communication, available support |
Stakeholder Engagement Plan
For each stakeholder in the "Manage closely" and "Keep informed" quadrants:
STAKEHOLDER ENGAGEMENT:
Stakeholder: [name or group]
Current stance: [from identification table]
Desired stance: [target]
Key concerns: [what they stand to lose or fear about the change]
Key benefits: [what they stand to gain — framed in THEIR terms, not the organisation's]
Engagement tactic: [specific action — meeting cadence, involvement in design, early access]
Owner: [who is responsible for this stakeholder relationship]
Success indicator: [observable behaviour showing stance shift]
Resistance Diagnosis
Resistance is information, not an obstacle. Diagnose the source before designing the response.
Resistance Source Framework
| Source | Manifestation | Root Cause | Response Strategy |
|---|---|---|---|
| Lack of awareness | "I didn't know this was happening" | Insufficient communication | Increase visibility — direct communication from sponsor |
| Lack of understanding | "I don't see why we need this" | Unclear rationale or business case | Explain the WHY — connect to problems they experience |
| Lack of capability | "I don't know how to do this" | Insufficient training or support | Build skills — hands-on training, coaching, job aids |
| Lack of willingness | "I don't want to do this" | Personal impact concerns (status, workload, job security) | Address concerns — listen, involve, adapt where possible |
| Lack of reinforcement | "We tried this before and went back" | No consequences or incentives for adoption | Sustain — management accountability, recognition, metrics |
Resistance Response Principles
- Investigate before responding — the presenting objection is rarely the actual concern
- Never dismiss resistance as irrational — it is rational from the stakeholder's perspective
- Distinguish between resistance to the change itself and resistance to how the change is being managed
- Track resistance themes across stakeholders — recurring themes signal systemic issues to address at the programme level, not individual conversations
Communication Planning
Communication Architecture
Design communication by audience, timing, and channel:
| Phase | Timing | Audience | Message Focus | Channel | Owner |
|---|---|---|---|---|---|
| Announce | Before change begins | All affected | WHY — business case, vision, what's changing | Town hall, email from sponsor | Change sponsor |
| Prepare | Weeks before go-live | Directly affected teams | WHAT — specific impacts, timeline, what to expect | Team meetings, detailed guide | Team leads + change team |
| Enable | At go-live | Users transitioning | HOW — step-by-step guidance, where to get help | Training sessions, quick-reference, helpdesk | Change team + trainers |
| Reinforce | Post go-live | All affected | PROGRESS — wins, feedback incorporation, next steps | Updates, dashboards, recognition | Change team + managers |
Message Design Principles
For every communication, answer these questions from the recipient's perspective:
- What is changing? — concrete description, not abstract vision
- Why is it changing? — business rationale connected to a problem they recognise
- What does it mean for me? — specific impact on their daily work
- What do I need to do? — clear, actionable next steps with dates
- Where do I get help? — support channels, contacts, resources
- What if I have concerns? — feedback mechanism with genuine response commitment
Communication Anti-Patterns
| Anti-Pattern | Problem | Better Approach |
|---|---|---|
| Leading with technology features | Sounds like a sales pitch, not addressing their concerns | Lead with the problem being solved and the benefit to them |
| "Exciting transformation" language | Feels dismissive of the disruption they experience | Acknowledge the difficulty honestly alongside the rationale |
| Information-only communication | Tells but doesn't listen — kills trust | Two-way: include feedback mechanisms and respond to input |
| Communicating too late | Change feels imposed rather than co-created | Front-load awareness; involve early even if details are incomplete |
| Single-channel broadcast | Misses audiences, feels impersonal | Multi-channel with tailored messaging per audience segment |
| Silence after launch | Signals abandonment; resistance fills the vacuum | Sustained reinforcement cadence for at least 3-6 months |
Training Design
Training Needs Assessment
For each affected group, assess the gap between current and required capability:
TRAINING NEEDS:
Group: [team or role]
Current capability: [what they can do today]
Required capability: [what the change requires them to do]
Gap: [specific skills or knowledge to build]
Learning preference: [hands-on, documentation, coaching — from org knowledge]
Constraint: [time available, location, language, accessibility needs]
Training method: [workshop, e-learning, job aid, peer coaching, shadowing]
Timeline: [when training must complete relative to go-live]
Training Delivery Principles
- Train as close to go-live as possible — skills decay rapidly if not applied immediately
- Provide job aids (quick-reference cards, checklists) alongside training — people forget 70%+ within a week without reinforcement
- Include practice with realistic scenarios, not just feature walkthroughs
- Designate super-users or floor-walkers for the first weeks post go-live
- Plan for stragglers — not everyone can attend the initial sessions
Adoption Tracking
Adoption Metrics Framework
Measure adoption across four dimensions:
| Dimension | What It Measures | Example Metrics | Data Source |
|---|---|---|---|
| Awareness | Do people know about the change? | Communication reach, survey awareness score | Email analytics, pulse surveys |
| Adoption | Are people using the new way? | System login rates, process compliance rate, old-system usage decline | System analytics, audit data |
| Proficiency | Are people using it correctly? | Error rates, support ticket volume, time-to-complete | System analytics, helpdesk data |
| Sustainability | Is it sticking? | Adoption trend over time, reversion rate, manager reinforcement | Longitudinal tracking |
Adoption Dashboard Structure
ADOPTION DASHBOARD — [Change Name] — [Date]
Awareness: [metric] — [current value] — [target] — [trend ↑↓→]
Adoption: [metric] — [current value] — [target] — [trend ↑↓→]
Proficiency: [metric] — [current value] — [target] — [trend ↑↓→]
Sustainability: [metric] — [current value] — [target] — [trend ↑↓→]
Key risks: [top adoption risks with mitigation status]
Actions: [current and next planned interventions]
Adoption Stall Diagnosis
When adoption plateaus or declines, diagnose by checking each dimension:
- Awareness stable but adoption low → people know but aren't doing → investigate willingness or capability barriers
- Adoption initially high then declining → novelty wore off, reinforcement failing → check manager accountability and incentives
- Adoption high but proficiency low → using it but incorrectly → training gap, provide coaching or revised job aids
- All dimensions low → fundamental change approach issue → revisit stakeholder analysis and communication plan
Output Template
Structure the final change management plan as follows:
# Change Management Plan — [Change Name]
## Change Overview
- Description: [what is changing]
- Business case: [why, connected to organisational strategy]
- Scope: [who, what, where]
- Timeline: [key milestones]
- Change intensity: [Incremental / Transitional / Transformational]
## Stakeholder Analysis
[Stakeholder map, influence-impact matrix, engagement plans]
## Resistance Assessment
[Diagnosed resistance sources, response strategies]
## Communication Plan
[Communication architecture table, key messages by phase]
## Training Plan
[Training needs per group, delivery schedule, job aids]
## Adoption Metrics
[Metrics framework, targets, tracking cadence, dashboard]
## Risks and Mitigations
[Change-specific risks with owners and response plans]
## Governance
- Change sponsor: [name and role]
- Change lead: [name]
- Review cadence: [how often the plan is reviewed and adapted]
- Escalation path: [how issues are raised and resolved]
Guardrails
- Never generate organisation-specific culture, politics, or stakeholder dispositions from training data. All organisational context comes from the user.
- Never fabricate stakeholder names, roles, or relationships. All stakeholder data comes from the user.
- Never claim "best practice" adoption rates or resistance percentages. These vary dramatically by organisation and context.
- Label generated content:
[From org data],[Framework methodology],[AI suggestion — verify].
Tip: Ask for DOCX or Markdown output via companyFILES to get a formatted plan ready to share.
04 同仓库更多 Skills
sales-asset-skill
Produce tailored one-pagers, landing pages, case study drafts, and demo narratives personalised to a specific deal and buyer persona. Use when preparing collateral for a specific deal, building leave-behind materials, or customising standard assets for a prospect. Trigger with "create a one-pager for", "sales deck for [deal]", "customise this asset for".
pipeline-review-skill
Analyse deal health, surface stale or at-risk opportunities, and produce a prioritised weekly action plan. Use when preparing for a pipeline review meeting, assessing forecast accuracy, or identifying stuck deals. Trigger with "review my pipeline", "pipeline health check", "deal risk analysis".
outreach-skill
Research a prospect then draft personalised outreach with research-backed hooks, subject-line variants, and follow-up sequences. Use when cold-emailing a prospect, writing LinkedIn outreach, or building a multi-touch sequence. Trigger with "draft outreach to [person/company]", "write cold email to", "outreach sequence for".
forecast-skill
Build a weighted revenue forecast with risk flags, commit recommendations, and gap-to-quota analysis. Use when preparing for a forecast call, evaluating end-of-quarter projections, or assessing pipeline coverage. Trigger with "build forecast", "forecast for this quarter", "where do I stand against quota".
deal-strategy-skill
Map stakeholder power dynamics, surface deal risks, and recommend a step-by-step engagement strategy. Use when entering a complex deal, preparing for an executive sponsor meeting, or diagnosing a stuck opportunity. Trigger with "plan deal strategy for", "stakeholder map", "how do I advance this deal".
call-summary-skill
Extract action items, key topics, and objections from call notes or transcripts and draft a customer-facing follow-up email. Use after a sales call, demo, or discovery session. Trigger with "summarise this call", "call notes from", "write follow-up for this meeting".