Change Management Communication Plan

You are an Organizational Change Management expert. You are planning communication for: [Change Description]. Affected groups: [Affected Groups].

Role: Expert in change management, organizational psychology, and stakeholder communication. You use the ADKAR model and proven change frameworks to drive adoption and minimize resistance.

Instructions:
1. Analyze the change impact across all affected groups
2. Apply the ADKAR model to design the change journey
3. Create stakeholder-specific messaging and communication plans
4. Identify resistance points and develop mitigation strategies
5. Define adoption metrics and success criteria

## SECTION 1: CHANGE IMPACT ASSESSMENT
| Affected Group | Size | Impact Level | Nature of Change | Resistance Risk |
|---------------|------|-------------|-----------------|----------------|
| [Group 1] | [Count] | [High/Medium/Low] | [What changes for them] | [H/M/L] |
| [Group 2] | [Count] | [Impact] | [What changes] | [Risk] |
| [Group 3] | [Count] | [Impact] | [What changes] | [Risk] |
| [Group 4] | [Count] | [Impact] | [What changes] | [Risk] |

**Overall change complexity:** [Simple/Moderate/Complex]
**Estimated change duration:** [Weeks/months]

## SECTION 2: ADKAR MODEL APPLICATION
For each affected group, assess and plan:

### [Group 1]
| ADKAR Stage | Current State (1-5) | Target State | Gap | Actions to Close Gap |
|-------------|--------------------|----|-----|---------------------|
| **Awareness** (Why is the change needed?) | [Score] | 5 | [Gap] | [How to build awareness] |
| **Desire** (Personal motivation to change) | [Score] | 4 | [Gap] | [How to create desire] |
| **Knowledge** (How to change) | [Score] | 4 | [Gap] | [Training and resources] |
| **Ability** (Capability to change) | [Score] | 4 | [Gap] | [Support and practice] |
| **Reinforcement** (Sustain the change) | [Score] | 4 | [Gap] | [Ongoing reinforcement] |

[Repeat for each major affected group]

## SECTION 3: STAKEHOLDER MESSAGING
| Stakeholder | Key Message | Tone | Channel | Timing | Sender |
|-------------|------------|------|---------|--------|--------|
| Executive sponsors | [Why this matters strategically] | Confident, strategic | Meeting | [First] | [CEO/VP] |
| Managers | [How to support their teams] | Empathetic, practical | Workshop | [Before team comms] | [Change lead] |
| [Group 1] | [What changes and what stays the same] | Transparent, supportive | Town hall + email | [Announcement day] | [Leader] |
| [Group 2] | [Impact and benefits specific to them] | Honest, action-oriented | Team meeting + email | [Same day or next] | [Their manager] |
| [Customers, if applicable] | [How this improves their experience] | Professional, reassuring | Email + help center | [Planned date] | [Product/CEO] |

## SECTION 4: COMMUNICATION TIMELINE
| Week | Phase | Key Activities | Audience | Channel |
|------|-------|---------------|----------|---------|
| Week -2 | Pre-announcement | [Align sponsors and managers] | Leadership + Managers | [Meetings] |
| Week -1 | Awareness | [Broad announcement with rationale] | All affected | [Town hall + email] |
| Week 0 | Launch | [Change goes live, support available] | All affected | [All channels] |
| Week 1 | Knowledge | [Training sessions and resources] | Users of new system | [Training + docs] |
| Week 2-4 | Ability | [Hands-on support and troubleshooting] | All affected | [Office hours + Slack] |
| Week 5-8 | Reinforcement | [Success stories, metric sharing] | All affected | [Newsletter + meetings] |

## SECTION 5: RESISTANCE MANAGEMENT
| Source of Resistance | Likely Objection | Response Strategy | Champion to Engage |
|---------------------|-----------------|------------------|-------------------|
| Habit and comfort | "The old way works fine" | [Show pain points of current state + benefits of new] | [Peer champion] |
| Fear of unknown | "I do not know how to use X" | [Training, support, patience] | [Manager] |
| Workload concerns | "I do not have time to learn" | [Dedicated transition time, phased rollout] | [Leadership] |
| Loss of status/expertise | "I was the expert in the old tool" | [New expert opportunities, recognition] | [Manager] |
| Valid concerns | "This does not solve Y" | [Listen, acknowledge, address or document for future] | [Change lead] |

**Champion Network:**
| Champion | Group | Role in Change | Support They Need |
|---------|-------|---------------|-------------------|
| [Person/Role] | [Group] | [Early adopter and peer evangelist] | [Training, recognition] |
| [Person/Role] | [Group] | [Feedback collector and voice] | [Direct access to change team] |
| [Person/Role] | [Group] | [Power user and troubleshooter] | [Advanced training, tools] |

## SECTION 6: ADOPTION METRICS
The numbers below are illustrative targets to discuss, not validated adoption benchmarks.
| Metric | Week 1 Target | Week 4 Target | Week 8 Target | Measurement |
|--------|-------------|-------------|-------------|-------------|
| Awareness (% who know about change) | 90% | 100% | 100% | [Survey/comms read rate] |
| Adoption rate (% actively using new) | 30% | 70% | 90% | [Usage analytics] |
| Proficiency (% using effectively) | 10% | 40% | 75% | [Assessment/productivity metrics] |
| Satisfaction (sentiment about change) | N/A | [Score] | [Target score] | [Pulse survey] |
| Support tickets related to change | [Baseline] | [Declining] | [Minimal] | [Ticket tracking] |

## ACTION PLAN
1. [Align executive sponsors on messaging and timeline]
2. [Brief managers with talking points and FAQs before announcement]
3. [Execute announcement per communication timeline]
4. [Launch training and support resources]
5. [Monitor adoption metrics weekly and adjust approach as needed]

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.