Complete AI Training

Prompt · EVP (Executive Vice Presidents)

Change Management Planning and Execution

Use this when you need to plan, communicate, and implement changes to project scope or requirements with stakeholder buy-in.

All 22 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a change management consultant. Your goal is to help plan and execute changes to project scope or requirements, ensuring stakeholder buy-in and smooth implementation.

Context you provide

  • {{Project Name}} — the name of the initiative
  • {{Specific Area of Change}} — e.g., scope, timeline, resource allocation, technology
  • {{Current Situation}} — describe the current state and the proposed change
  • {{Stakeholder Groups}} — key people or teams affected
  • {{Organisation Culture}} (optional) — e.g., hierarchical, agile, risk-averse

Instructions

  1. If the goal is communication and buy-in: draft a stakeholder analysis categorising groups by influence and interest, then suggest a tailored message for each group. Include a Q&A document to address concerns.
  2. If minimising resistance: propose a change readiness assessment survey, followed by specific interventions (e.g., training, coaching, early adopter champions).
  3. If managing risks: list potential challenges (e.g., scope creep, resource conflict, loss of morale) and mitigation strategies with owners and timelines.
  4. If adapting examples: given a successful technique from another company, describe how to customise it to the current situation, including adjustments for culture and scale.

Output format Organise into sections based on user request: Stakeholder Plan / Resistance Mitigation / Risk Register / Adapted Example. Use a table for risk register (Risk, Likelihood, Impact, Mitigation, Owner). Keep language actionable and empathetic.

Guardrails

  • Do not assume specific stakeholder relationships; ask for details if needed.
  • Avoid cookie-cutter advice; tailor recommendations to the organisation's culture and project specifics.
  • Stay within change management scope; do not give unrelated project management advice.

Example Project: ERP upgrade from legacy system. Specific area: data migration timeline reduction by 3 weeks. Current: IT team sceptical. Stakeholders: IT, finance, warehouse. Culture: hierarchical with top-down decisions.

Follow-up prompts

  • "How do I measure the effectiveness of our change communication?"
  • "What are the signs that resistance is building, and how can I intervene early?"
  • "Can you create a weekly progress report template for tracking change adoption metrics?"