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

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

Example for: an engineering director merging two squads and delaying a mobile release by six weeks, sent by email to 18 people.

1. Subject line
Mobile and Web squads merge on June 3; app release moves to August 12

2. Announcement body
Starting June 3, the Mobile and Web squads will merge into one Client Apps squad, and the mobile app release moves from July 1 to August 12.

We are doing this because both squads depend on the same payments rework, and running it twice has slowed us down. One squad with one backlog removes that duplication.

Priya Nair will lead Client Apps. Tomas Reyes, who led Web, will move to a staff engineer role focused on the payments rework. No roles are being cut, and no one's pay or level changes.

Two things are not decided yet: the new on-call rotation (settled by May 29) and whether we keep separate standups (we will decide together in the first retro).

I will hold an open Q&A on Thursday at 2 pm, and my calendar is open for one-to-ones all week.

Dana

3. Impact by group

GroupWhat changesWhat stays the same
Mobile squad (9)Manager stays Priya; backlog merges with WebPay, level, current tickets
Web squad (7)Manager becomes PriyaPay, level, tech stack
Tomas ReyesMoves to staff engineer, paymentsLevel, reports to Dana
QA (2)One test plan instead of twoRelease sign-off process

4. Likely questions

  1. Is this a step toward layoffs? No roles are being cut as part of this change.
  2. Why the six-week delay? The payments rework needs to land first; shipping before it would mean redoing checkout.
  3. Will my performance review change? Reviews in July use goals set before the merge. (Needs your confirmation.)
  4. Do I need to switch teams in Jira? Yes, by June 3. Priya will move boards.
  5. Was Tomas demoted? No. His level stays the same; he asked for a hands-on role.
  6. What happens to Friday demo day? It continues as one combined demo.
  7. Can I raise concerns privately? Yes, with me or Priya, any time this week.

5. Next steps

  • May 22: Q&A session, 2 pm
  • May 29: on-call rotation shared
  • June 3: merge takes effect
  • August 12: mobile release

Check with HR before sending: the statement that no roles are being cut and the wording about Tomas's role change.

Written by AI from this prompt. Your results will vary.

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 in Productivity