Create a change-management plan for [CHANGE DESCRIPTION] affecting [AFFECTED GROUPS]. The change is being made because [BUSINESS RATIONALE], and the target date or phases are [TIMELINE]. Use only the facts in [CURRENT CONTEXT]; do not assume the change is popular, inevitable, or fully designed. Build the plan around the practical question each group will have: what changes in my work, when, what support will I receive, who decides unresolved issues, and how can I raise problems safely. Produce these sections: 1. A one-paragraph change narrative separating confirmed decisions, open decisions, and assumptions.
2. A stakeholder map with each group’s likely impact, influence, concerns, preferred channel, sponsor, and needed action. 3. A phased plan for prepare, launch, stabilize, and reinforce, with owners, dates or triggers, training, manager actions, and feedback loops. 4. A communications plan with audience-specific messages; include a manager briefing and employee FAQ topics. 5. Adoption measures: leading indicators, outcome measures, data source, baseline needed, review cadence, and corrective action if adoption stalls. 6. The five biggest risks, including workload, capability, equity, trust, and operational continuity where relevant. Recommend the next three actions in priority order. Do not promise outcomes without evidence, use vague claims of “buy-in,” or frame legitimate concerns as resistance to overcome. Self-check that every affected group has a two-way feedback path and that managers are given concrete responsibilities. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [CHANGE DESCRIPTION] | Describe the operational, technology, policy, or organizational change being introduced. | Replacing emailed weekly inventory reports with a shared planning dashboard. |
| [AFFECTED GROUPS] | List teams, roles, locations, customers, or partners affected by the change. | Store managers, regional planners, warehouse leads, and the finance reporting team. |
| [BUSINESS RATIONALE] | Explain the verified reason for the change and the intended outcome. | Reduce conflicting inventory numbers and give stores a daily view of replenishment status. |
| [TIMELINE] | Enter key dates, phases, deadlines, or decision gates. | Pilot in 12 stores on November 3; regional rollout begins December 1. |
| [CURRENT CONTEXT] | Paste known constraints, prior feedback, leadership decisions, training capacity, and open questions. | Managers currently spend 45 minutes compiling reports each Monday. Some stores have limited tablet access. The dashboard is ready for pilot but finance definitions are still being finalized. |
How to use
- Describe what has been decided separately from what remains open; the plan needs both.
- Include affected frontline roles, not only executive sponsors and project-team members.
- Check that each communication has a named owner, a channel, and a way for people to respond.
- Follow up with: “Draft the manager briefing for the pilot launch, including what managers should say when they do not yet know an answer.”
Variations
Manager briefing
Use when managers need to explain a change consistently and honestly.
Create a manager briefing for [CHANGE] affecting [TEAM]. Based on [CONFIRMED FACTS] and [OPEN QUESTIONS], produce a 5-minute talk track, five anticipated employee questions with truthful answers, three actions managers must take this week, and an escalation route. Clearly distinguish confirmed information from unknowns. Do not promise job, workload, or timeline outcomes not approved by leadership.
Employee FAQ
Use when employees need plain answers before or during rollout.
Write an employee FAQ about [CHANGE] for [AUDIENCE] using [VERIFIED DETAILS]. Include what is changing, why, timing, what people need to do, training and support, privacy or job-impact information if known, and where to raise concerns. Use plain language and label unanswered questions as pending. Do not minimize disruption or invent assurances.
Adoption review
Use after launch to diagnose weak adoption without blaming people.
Analyze adoption of [CHANGE] using [ADOPTION DATA] and [USER FEEDBACK]. Produce a one-page review with observed patterns, likely causes separated from proven causes, groups needing support, operational risks, and a 30-day corrective-action plan with owners and measures. Treat feedback as evidence, not resistance. Flag data that is missing before drawing conclusions.
Tips
- Measure behaviors that happen before the final business result, such as training completion, first-use rates, error types, and manager check-ins.
- Give managers scripts, escalation routes, and time to support the change; an announcement alone shifts the burden to them without preparation.
- Track impact by role and location so a successful average does not hide a group with inadequate access or training.
- Keep an open-questions log visible to affected people and update it on a stated cadence.
FAQ
Is change management just communications?
No. Communication explains the change, but adoption also needs role-specific workflow support, manager actions, training, feedback, and decisions on issues discovered after launch.
How should AI handle employee concerns?
Use it to organize and summarize concerns, then validate themes with people closest to the work. Do not use it to dismiss concerns or invent reassurance.
What if the change details are still incomplete?
Plan around confirmed decisions and clearly label the open ones. A credible plan says who will decide, by when, and how affected people will be updated.