Draft a Hard Team Announcement for a Reorg, Delay or Policy Change
Get a clear team announcement that states the news first, shows what changes and stays the same for each group, and answers likely questions honestly.
You getSubject line, announcement body and table with columns
Prompt
You are an internal communications lead who writes clear, honest announcements for teams facing difficult news.
Help me draft a team announcement about a hard change, such as a reorg, a project delay or a policy change. Before writing, ask me these questions in one message and wait for my answers:
1. What is the change, and when does it take effect?
2. Who is affected, and how does it change their work, manager, schedule or goals?
3. Why is it happening, and what has not been decided yet?
4. Who is sending it, and through which channel (email, Slack or a script to read in a meeting)?
Rules:
- Put the news in the first sentence. No warm-up and no "exciting times" framing.
- Give the reason in two sentences or fewer, in plain words.
- Split impact by group: what changes and what stays the same for each.
- Name every open decision and when it will be settled. Do not promise anything I did not give you.
- Keep the main message under 250 words, with no corporate filler.
Output format:
1. Subject line
2. Announcement body
3. Table with columns: Group | What changes | What stays the same
4. Likely questions: 6-8 questions with honest answers. Mark any answer that needs my confirmation.
5. Next steps with dates
End with one line flagging anything sensitive, such as legal, HR or job security points, that I should check with HR before sending.Example output
Tips and common edits
Why this works
- Leading with the news in sentence one stops people from reading between the lines of a long warm-up.
- The changes vs. stays-the-same table answers the first question everyone asks: what does this mean for me?
- Naming open decisions with dates builds trust and stops the model from inventing promises you can't keep.
Use this in ChatGPT, Claude or Gemini before you send news people won't like. Have the facts ready: what changes, the effective date, who is affected, the reason and what is still undecided.
Common edits
- Ask for a shorter Slack version under 100 words that links to the full email.
- Ask for a spoken script for an all-hands with pauses for questions.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Write a Project Kickoff Message for Your Team and Stakeholders
You get a short team kickoff message covering why, scope, roles, first deadline and questions, plus a shorter stakeholder version and a list of gaps.
Build a RACI Chart from Your Project Task List with Ownership Gaps Flagged
Turns a pasted task list into a RACI table with one Accountable per task, flags unowned or over-consulted tasks, and lists questions to confirm with your team.
Plan a Sprint Retrospective with Timed Steps, Questions and a Dot-Vote
Get a retro format matched to your team's mood and problems, with a timed agenda, warm-up, open questions, and a dot-vote that ends in at most three owned actions.
Prepare a Constructive Feedback Conversation with a Teammate Using SBI
Get a ready-to-say feedback script with an opening line, a situation-behavior-impact statement, one clear request, and calm replies to defensive reactions.
Turn Rough Notes into a Weekly Slack Team Update with Clear Blockers
Turns your messy weekly notes into a Slack-ready team update under 150 words, split into Shipped, Next and Blocked, with an owner and date for every blocker.
Build a Reusable Report or Memo Template Anyone on Your Team Can Fill In
Get a blank document template with headed sections, one-line guidance under each, a fully filled example, and a short pre-send checklist.