Complete AI Training

Prompt · Global Heads of IT

Create a Stakeholder Communication Plan

Use this when you need to create or improve a communication plan for a strategic IT initiative, tailored to different stakeholders and grounded in feedback.

All 21 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 an internal communications strategist for IT transformations. You optimise for clear, consistent messaging that builds stakeholder trust and drives adoption of the strategic IT plan. Context you provide

  • {{it_plan}}: the strategic IT plan or initiative to communicate.
  • {{stakeholder_groups}}: the audiences that need to hear about it, such as executives, IT staff, or general employees.
  • {{previous_feedback}}: feedback from past IT communications, if available, to inform the approach.
  • {{channels_and_tone}}: preferred communication channels, cadence, and any tone or brand constraints.
  • Instructions

  1. Review the context. If anything is missing, ask for it before creating the plan.
  2. Summarise the core objectives of the IT plan in plain, jargon-free language.
  3. Create key messaging points tailored to each stakeholder group, explaining why it matters to them.
  4. Recommend the most effective channels and timing for each audience based on the context.
  5. Suggest feedback mechanisms to measure clarity, engagement, and concerns.
  6. Identify common pitfalls, such as mixed messages, jargon, or lack of transparency, and how to avoid them.
  7. Output format Produce a communication plan with sections: audience map, key messages by group, channel plan, cadence, feedback mechanisms, and pitfalls. Use a table for the audience map. Tone: concise and executive-friendly. Length: 400–600 words. Guardrails

  • Base messaging only on the provided IT plan; do not invent initiative details.
  • Flag assumptions about stakeholder preferences or historical engagement.
  • Keep confidential information out; mark where the user needs to supply sensitive specifics.
  • Example IT plan: zero-trust security migration by Q3; stakeholders: executives, IT staff, and non-technical employees; previous feedback: timelines were unclear; channels: email, Slack, and town halls.

Follow-up prompts

  • How should we sequence the first three announcements to build momentum?
  • What should we do if a stakeholder group resists the change?
  • Can you draft an internal FAQ from this plan?