Plan change management and user adoption for a rollout
A people-side change plan covering impact by group, readiness, training, communications, and adoption measures.
The prompt
Help me plan change management and adoption for a project rollout.
What is changing: [NEW system, process, policy, or structure]
Who is affected: [GROUPS - roles, teams, locations, number of people]
What changes for each group: [what they will do differently]
Go-live date: [DATE]
Sponsor and their visibility: [WHO, and how active they will be]
Known resistance or concerns: [WHAT you have heard]
Past change history: [how similar changes went here]
Use a structured approach (such as ADKAR: awareness, desire, knowledge, ability, reinforcement) and build:
1. Change impact assessment: group | what changes | impact level (high/medium/low) | likely concerns | what they need.
2. Sponsor and manager roles: what the sponsor must visibly do, and what line managers need to say and do with their teams (managers are often the most important channel).
3. Communication plan: message, audience, channel, sender, timing - sequenced from "why" through to "how" and "what's next."
4. Training plan: by group, format, timing (close to go-live, not months before), and support after training.
5. Change champions: how to pick them and what they do.
6. Resistance management: likely sources and responses for each.
7. Adoption measures: usage, proficiency, and outcome metrics with targets, and how to reinforce the change after go-live.
Use [CONFIRM] for numbers or dates I have not given. Flag any group with high impact and no clear support plan.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Leadership & Management prompts
What to fill in
- NEW system, process, policy, or structure
- GROUPS - roles, teams, locations, number of people
- what they will do differently
- DATE
- WHO, and how active they will be
- WHAT you have heard
- how similar changes went here
- CONFIRM
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Turn my observations of a manager or leader into development actionsConverts your notes on a leader's behavior into patterns, development priorities, and on-the-job actions to discuss with them.
- Anticipate resistance to my proposal and plan how to win alignmentPredicts who will push back on your proposal and why, and builds a step-by-step plan to get stakeholders aligned.
- Plan my first one-on-ones with a team I've just inheritedAn announcement, conversation guide, and note template for your first one-on-ones with a team you've taken over.
- Map stakeholders and plan how to influence themWho matters, what they care about, and how to engage each one.