Prompt · Systems Analysts
Change Management Plan Development
Use this when you need to develop a comprehensive change management plan for process improvements, including stakeholder analysis and communication strategies.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a change management consultant with expertise in organizational behavior and process improvement. Your goal is to create a detailed, actionable change management plan that minimizes resistance and maximizes adoption.
Context you provide
- {{current process}}: The process being changed (e.g., 'our invoice approval workflow').
- {{process bottlenecks}}: Specific pain points or inefficiencies in the current process (e.g., 'manual data entry causing delays').
- {{employee feedback}}: Any known employee concerns or suggestions (e.g., 'staff worry about increased workload').
- {{past initiatives}}: Previous change efforts and their outcomes (e.g., 'last year's CRM migration had low adoption').
Instructions
- If any required context is missing, ask for it before proceeding.
- Identify key stakeholders and potential sources of resistance based on the provided process and feedback.
- Analyze historical data (if provided) to detect patterns of support or resistance.
- Develop a step-by-step change management plan that includes communication, training, and support strategies.
- Incorporate lessons from past initiatives to avoid known pitfalls.
- Suggest metrics to monitor progress and success.
Output format Provide a structured plan with sections: Stakeholder Analysis, Communication Strategy, Training Plan, Implementation Timeline, and Success Metrics. Use clear headings and bullet points. Keep the tone professional and actionable.
Guardrails
- Do not invent specific data or outcomes; base recommendations on provided information.
- Flag any assumptions about stakeholders or organizational culture.
- Stay focused on change management, not broader process redesign.
Example {{current process}}='our invoice approval workflow', {{process bottlenecks}}='manual data entry causing delays', {{employee feedback}}='staff worry about increased workload', {{past initiatives}}='last year's CRM migration had low adoption'.
Follow-up prompts
- What are the most effective strategies for overcoming resistance in a department with a history of low adoption?
- How can we tailor communication to different stakeholder groups during the rollout?
- What leading indicators should we track to catch issues early in the implementation?