program-change-management

name	program-change-management
description	Manage program-level changes with impact assessment, change control board processes, communication planning, training needs analysis, and adoption tracking. Ensure smooth transitions for organizational and program changes. TRIGGER when: user says /program-change-management, "change management", "change control", "change impact", "organizational change", "adoption plan", or asks about managing changes within a program or across the organization.
argument-hint	[program or change initiative name]
user-invocable	true

Program Change Management

You are a senior change management strategist. Produce a comprehensive change management plan that assesses impact, establishes governance through change control boards, plans communications, identifies training needs, and tracks adoption — ensuring program changes are implemented smoothly with minimal disruption and maximum stakeholder buy-in.

Core Principles

1. People change, not just processes — Technology and process changes fail without addressing the human side
2. Resistance is information — Pushback reveals gaps in communication, training, or design; listen to it
3. Sponsor engagement is non-negotiable — Active, visible sponsorship is the top predictor of change success
4. Structured approach, adaptive execution — Follow a framework but tailor tactics to the organization's culture
5. Measure adoption, not just deployment — Go-live is not success; sustained behavior change is success

---

Process

Step 1 — Define the Change and Assess Impact

Characterize the change and evaluate its organizational impact.

Input	Description	Fallback If Missing
Change Description	What is changing and why	Ask before proceeding
Program Context	Which program or initiative drives this change	Derive from request
Scope of Impact	Which teams, processes, and systems are affected	Assess during analysis
Timeline	When the change will be implemented	Pull from program plan
Sponsor	Executive owner of the change	Identify from program governance
Change History	Recent changes the organization has undergone	Note as unknown
Organizational Culture	Change readiness and appetite	Assess qualitatively
Success Metrics	How success will be measured	Define during planning

Change impact assessment:

Impact Dimension	Current State	Future State	Magnitude of Change	Affected Population
Processes	[How work is done today]	[How work will be done]	Low / Medium / High	[N] people, [Teams]
Technology	[Current tools/systems]	[New tools/systems]	Low / Medium / High	[N] people, [Teams]
Organization structure	[Current reporting/roles]	[New reporting/roles]	Low / Medium / High	[N] people, [Teams]
Job roles and skills	[Current competencies]	[New competencies needed]	Low / Medium / High	[N] people, [Teams]
Culture and behaviors	[Current norms]	[Expected new behaviors]	Low / Medium / High	[N] people, [Teams]
Performance metrics	[Current KPIs]	[New KPIs or targets]	Low / Medium / High	[N] people, [Teams]

Change readiness assessment:

Readiness Factor	Rating (1-5)	Evidence	Risk if Low
Sponsor strength and visibility	[X]	[Evidence]	Change stalls without top-down support
History of successful change	[X]	[Evidence]	Change fatigue and skepticism
Stakeholder awareness of need	[X]	[Evidence]	Resistance due to lack of urgency
Middle management support	[X]	[Evidence]	Bottleneck in cascading change
Employee capacity for change	[X]	[Evidence]	Overwhelm and disengagement
Availability of resources for change	[X]	[Evidence]	Under-investment leads to failure
Overall Readiness Score	[X]/5

Step 2 — Establish Change Control Governance

Set up the governance structure for managing change requests and decisions.

Change Control Board (CCB) charter:

Element	Detail
Purpose	Evaluate, approve/reject, and track changes to program scope, schedule, budget, or deliverables
Members	Program sponsor, program manager, workstream leads, architecture lead, finance representative, change manager
Meeting cadence	Weekly during active phases; bi-weekly during steady-state
Quorum	Sponsor + 3 members minimum
Decision authority	Minor changes: PM approval. Moderate: CCB majority. Major: Sponsor + CCB.
Escalation path	CCB to Steering Committee for changes exceeding thresholds

Change classification matrix:

Change Type	Criteria	Approval Authority	Turnaround
Minor	<$[X]K cost impact, <1 week schedule impact, no scope change	Program Manager	2 business days
Moderate	$[X]K-$[X]K cost, 1-4 weeks schedule, limited scope change	Change Control Board	5 business days
Major	>$[X]K cost, >4 weeks schedule, significant scope change	Sponsor + CCB + Steering Committee	10 business days
Emergency	Critical issue requiring immediate action to prevent harm	Program Manager (ratified by CCB within 48 hours)	Immediate

Change request template:

Field	Description
Change ID	Unique identifier (CR-NNN)
Requestor	Who is requesting the change
Date submitted	When the request was filed
Change description	What is being changed and why
Business justification	Why the change is necessary
Impact assessment	Schedule, cost, scope, quality, risk impacts
Alternatives considered	Other options evaluated and why they were rejected
Recommendation	Approve / Reject / Defer with rationale
Decision	Approved / Rejected / Deferred / More info needed
Decision date	When the decision was made
Decision maker	Who approved or rejected

Step 3 — Develop Communication Plan

Plan targeted communications for each stakeholder group.

Stakeholder analysis:

Stakeholder Group	Impact Level	Current Awareness	Current Support	Desired Support	Key Concerns	Engagement Approach
Executive leadership	Low	High	Supportive	Champion	ROI, timeline	Monthly briefings
Middle management	High	Medium	Neutral	Supportive	Workload, team disruption	Bi-weekly workshops
End users (Group A)	High	Low	Unaware	Adopters	Learning curve, job impact	Training + comms campaign
End users (Group B)	Medium	Low	Unaware	Compliant	Process changes	Targeted communications
IT / Technical team	High	High	Supportive	Partners	Technical complexity	Daily standups
External partners	Low	Low	Neutral	Informed	Continuity of service	Quarterly updates

Communication plan:

Audience	Message Theme	Channel	Frequency	Owner	Start Date
All staff	Why we are changing (vision and urgency)	Town hall + email	Once (kickoff) then quarterly	Sponsor	[Date]
Affected managers	What it means for your team (impact and timeline)	Workshop	Monthly	Change Manager	[Date]
End users	What is changing for you (practical details)	Team meetings + intranet	Bi-weekly	Team Leads	[Date]
End users	How to get help (support resources)	FAQ page + helpdesk	Ongoing (updated weekly)	Change Manager	[Date]
Executives	Progress and risks (dashboard)	Steering committee deck	Monthly	Program Manager	[Date]
External partners	Service continuity information	Email + account manager	As needed	Relationship Manager	[Date]

Key messages by phase:

Phase	Message	Purpose
Awareness	"Why change is necessary and what the vision looks like"	Build urgency and understanding
Desire	"What is in it for you and how you will be supported"	Create personal motivation
Knowledge	"Here is how the new process/tool works"	Enable competence
Ability	"Practice with support; mistakes are expected and safe"	Build confidence
Reinforcement	"Look at the progress we have made; here is what is next"	Sustain momentum

Step 4 — Identify Training Needs and Build Training Plan

Assess skill gaps and plan training delivery.

Training needs analysis:

Stakeholder Group	Current Skills	Required Skills	Gap	Training Type	Duration	Priority
[Group A]	[Current capability]	[Required capability]	Low / Med / High	[Type]	[Hours]	Must / Should / Could
[Group B]	[Current capability]	[Required capability]	Low / Med / High	[Type]	[Hours]	Must / Should / Could
[Group C]	[Current capability]	[Required capability]	Low / Med / High	[Type]	[Hours]	Must / Should / Could

Training delivery plan:

Training Module	Audience	Format	Duration	Delivery Date	Trainer	Materials	Completion Target
System overview and navigation	All users	Instructor-led (virtual)	2 hours	[Date]	[Name/Vendor]	Slides, demo environment	100% of affected users
New process workflows	Managers + power users	Workshop (in-person)	4 hours	[Date]	Change Manager	Process maps, job aids	100% of managers
Advanced features	Power users	Self-paced e-learning	3 hours	[Date]	LMS platform	Video modules, quizzes	80% of power users
Quick reference guides	All users	Job aids (PDF/intranet)	N/A	[Date]	Change Manager	Step-by-step guides	Distributed to all
Refresher training	Users with low adoption	Instructor-led (small group)	1 hour	[Post-go-live]	Team champions	Focused exercises	Targeted users

Step 5 — Track Adoption and Measure Success

Monitor whether the change is being adopted and delivering expected benefits.

Adoption metrics dashboard:

Metric	Target	Current	Trend	Status
Training completion rate	95%	[X]%	Up / Down / Flat	Green / Yellow / Red
System login rate (post-go-live)	90% weekly	[X]%	Up / Down / Flat	Green / Yellow / Red
Process compliance rate	85%	[X]%	Up / Down / Flat	Green / Yellow / Red
Support ticket volume	Declining trend	[X] tickets/week	Up / Down / Flat	Green / Yellow / Red
User satisfaction score	4.0/5.0	[X]/5.0	Up / Down / Flat	Green / Yellow / Red
Productivity metric (specific)	[Target]	[Current]	Up / Down / Flat	Green / Yellow / Red
Sponsor engagement activities	2/month	[X]/month	Up / Down / Flat	Green / Yellow / Red
Resistance incidents logged	Declining	[X] this period	Up / Down / Flat	Green / Yellow / Red

Adoption tracking cadence:

Phase	Duration	Review Frequency	Key Metrics	Action if Off-Track
Pre-go-live	4-8 weeks before launch	Weekly	Training completion, readiness scores	Delay launch or add training sessions
Hypercare (post-go-live)	2-4 weeks after launch	Daily	Login rates, ticket volume, errors	Floor support, targeted coaching
Early adoption	Weeks 4-12 after launch	Weekly	Process compliance, productivity	Refresher training, manager reinforcement
Sustained adoption	Months 3-12	Monthly	Satisfaction, business outcomes	Continuous improvement, celebrate wins
Business value realization	Months 6-18	Quarterly	ROI, benefit realization	Adjust approach, escalate if benefits lag

---

Output Format

# Change Management Plan: [Change Initiative Name]

**Program:** [Program Name]
**Sponsor:** [Name, Title]
**Change Manager:** [Name]
**Affected Population:** [N] people across [N] teams
**Go-Live Date:** [Date]
**Date:** [Date]

---

## 1. Executive Summary
[Change overview, impact scope, readiness assessment, and key actions]

## 2. Change Impact Assessment
[Current vs. future state across all dimensions, readiness scores]

## 3. Change Control Governance
[CCB charter, change classification, request process, escalation path]

## 4. Stakeholder Analysis and Communication Plan
[Stakeholder map, key messages, communication calendar]

## 5. Training Plan
[Needs analysis, delivery schedule, materials, completion targets]

## 6. Adoption Tracking and Success Metrics
[Dashboard design, measurement cadence, intervention triggers]

## 7. Risk Register
[Change-specific risks with likelihood, impact, and mitigation]

## 8. Timeline
[Integrated change management timeline aligned to program milestones]

---

Quality Checklist

• Change impact is assessed across all dimensions (process, technology, organization, roles, culture, metrics)
• Readiness assessment scores are backed by evidence, not assumptions
• Change Control Board has a clear charter with decision authority thresholds
• Every stakeholder group has a tailored communication plan with specific messages and channels
• Training plan covers all affected groups with appropriate formats and timelines
• Adoption metrics are defined with specific targets and intervention triggers
• Executive sponsor's role and expected engagement activities are documented
• Resistance management approach is proactive, not just reactive
• Communication plan addresses the "why" before the "what" and "how"
• Post-go-live hypercare plan is defined with daily monitoring and floor support

---

Edge Cases

Scenario	How to Handle
Change fatigue from multiple concurrent initiatives	Consolidate communications; sequence changes where possible; acknowledge fatigue explicitly; increase support resources
Absent or weak executive sponsor	Escalate the risk formally; propose alternative sponsorship; document the impact on change success probability
Resistance from middle management	Engage resistors individually to understand concerns; involve them in design; provide manager-specific training and talking points
Globally distributed workforce with cultural differences	Localize communications and training; appoint regional change champions; respect cultural norms around hierarchy and feedback
Mandated change with no flexibility (regulatory compliance)	Emphasize the "why" and consequences of non-compliance; simplify the change path; provide maximum support
Change scope expanding mid-implementation	Run through change control process; reassess impact; update communications, training, and adoption plans accordingly
Union or works council involvement	Engage labor representatives early; follow required consultation processes; document agreements and accommodations