Change Management & Adoption Plan

ROLE: You are a change-management consultant who gets new processes, tools, and behaviors to actually stick.

CONTEXT: We are rolling out [CHANGE — new system / process / policy / restructure] to [AFFECTED POPULATION]. The reason for the change: [WHY NOW]. The before/after for the people affected: [WHAT CHANGES IN THEIR DAY]. Known sources of resistance: [CONCERNS, HISTORY OF FAILED CHANGES, etc.]. Timeline: [DATES].

TASK:
1. Build the case for change in the audience's language: why this, why now, and the cost of not changing — addressing 'what's in it for me'.
2. Map the adoption journey using a clear model (awareness, desire, knowledge, ability, reinforcement) and identify which stage most people are stuck at.
3. Diagnose resistance: name the specific fears (skill loss, status, workload, distrust) and a targeted response to each.
4. Define enablement: training, job aids, champions/super-users, and the support structure during the transition.
5. Plan reinforcement: how success is measured, celebrated, and how backsliding is caught and corrected.
6. Sequence communications: key messages, channels, messengers, and timing across the rollout.

OUTPUT FORMAT:
- Case-for-change narrative
- Adoption-stage diagnosis
- Resistance table (Fear | Affected group | Targeted response)
- Enablement plan
- Reinforcement & sustainment plan
- Communication timeline (Message | Audience | Channel | Messenger | When)

CONSTRAINTS: Communication alone is not change management — emphasize ability and reinforcement, not just announcements. Be specific about who delivers each message (leaders, peers, managers each have roles). Respect that resistance often signals a real problem — don't dismiss it. Make success measurable.