Prepare an organizational change plan and team Q&A

Announce organizational redesigns and reporting shifts with clarity, empathy, and prepared answers to tough team questions.

You getAll-Hands Announcement Script, anticipated Difficult Q&A and manager 1:1 Talking Points

Prompt

Prompt
Act as an organizational design and executive leadership advisor. Review the restructuring details below to build an empathetic, unambiguous change communication package.

- Articulate the business rationale clearly without corporate jargon or buzzwords.
- Minimize team anxiety by stating what changes immediately, what stays the same, and when changes take effect.
- Draft tough, candid questions employees will ask about job security, career growth, and workload, providing grounded answers.
- Outline explicit next steps for managers holding follow-up one-on-one meetings.

Output format:
1. All-Hands Announcement Script (opening context, the business driver, what is changing, what remains unchanged)
2. Anticipated Difficult Q&A (4 realistic, difficult questions with direct, transparent answers)
3. Manager 1:1 Talking Points (3 critical topics managers must cover in day-one check-ins)
4. 30-Day Transition Timeline (key dates and communication touchpoints)

Here are the details of the team restructuring:

Example output

Example for: merging two product engineering squads into a single core platform group

  1. All-Hands Announcement Script
    "Team, effective November 1st, we are uniting the Core Infrastructure and Developer Tooling teams into a single Platform Services division. Over the past year, these teams frequently stepped on each other's codebases, leading to fragmented internal tools and duplicated operational overhead. By combining our platform work under one reporting line led by Marcus Vance, we can eliminate conflicting backlogs and set unified standards. Your immediate compensation, core daily tools, and current sprint goals for this quarter will not change. Our goal with this move is not headcount reduction; it is clearer ownership."
  2. Anticipated Difficult Q&A
  • Q: Are layoffs planned as part of this merger?
    A: No. Every individual in both teams retains their role. This change is entirely focused on architectural ownership and reporting clarity.
  • Q: Does this eliminate promotion opportunities now that teams are combined?
    A: No. A larger platform organization creates clearer Staff and Principal engineering tracks that were previously constrained within smaller squads.
  • Q: Will my manager change?
    A: Half of the team will transition to a new direct reporting manager starting November 1st. You will have a 1:1 conversation with your new manager by Friday.
  • Q: Will current project deadlines be adjusted for the transition?
    A: Yes. All current deadlines are receiving a one-week buffer to account for administrative adjustments and workflow harmonization.
  1. Manager 1:1 Talking Points
  • Reassure individual role continuity and confirm immediate compensation remains unaffected.
  • Confirm new reporting lines and review day-to-day communication channels.
  • Solicit initial concerns about active workload shifts and capture feedback on backlog prioritization.
  1. 30-Day Transition Timeline
  • Day 1: All-Hands announcement followed by managerial 1:1s.
  • Day 7: New combined backlog grooming and leadership sync.
  • Day 14: Mid-point retrospective on workflow and team ceremonies.
  • Day 30: Division review on delivery velocity and team health check.
Written by AI from this prompt. Your results will vary.

Paste your organization's restructuring details, headcounts, reporting line changes, and business motives into ChatGPT, Claude, or Gemini. Follow up by asking the model for guidance on managing team members whose roles are significantly downgraded.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Leadership & Management