How HR & People Teams Use AI Prompts for Better Employee Communication

You are an HR communications lead writing a company-wide announcement about a significant change to our work policy.

CONTEXT:
Our company (450 employees, Series C SaaS startup) is transitioning from fully remote to a hybrid model requiring 3 days in-office per week, effective September 1. This decision was made by the executive team based on collaboration data showing declining cross-team project velocity. Approximately 30% of employees were hired as fully remote during 2020-2022 and may have relocated. We have offices in San Francisco, Austin, and London. Employees who relocated beyond commuting distance will be offered relocation assistance or a 6-month transition period to find a remote-compatible role internally.

AUDIENCE:
All employees globally. The message should primarily address:
1. Employees in commuting distance (majority) -- what changes, when, and why
2. Fully remote employees who relocated -- their specific options and timeline
3. Managers -- how to handle team conversations about the transition

TONE:
Direct and honest, not defensive. Acknowledge that this is a significant change and some employees will be disappointed. Avoid corporate euphemisms like "evolving our work model" -- call it what it is: a shift from remote to hybrid. Be empathetic but confident in the reasoning.

OBJECTIVE:
Write a company-wide email from our CEO (Sarah Chen) that:
- Explains the change clearly in the first two paragraphs
- Provides the specific rationale with data, not just "collaboration"
- Addresses the three audience segments with specific next steps
- Includes an FAQ section covering: effective date, exceptions process, relocation support details, impact on current remote roles, how to request accommodation
- Ends with an invitation to a live Q&A session (date TBD)

CONSTRAINTS:
- Do not use the phrase "return to office" -- frame as "hybrid transition"
- Include a note about ADA accommodations process
- Keep the main email under 600 words; FAQ can be longer
- Must work for all three office locations (SF, Austin, London)

FORMAT:
Email format with subject line. FAQ section after the main body with collapsible-style Q&A formatting.

You are a People Operations specialist creating a 5-email onboarding communication sequence for new engineering hires at a mid-size B2B SaaS company.

CONTEXT:
We are a 200-person company with a product-led growth model. Engineering is our largest team (70 people across 8 squads). Our onboarding has been informal and varies by manager. We want to standardize the communication touchpoints while keeping the tone warm and personal. Our culture values ownership, curiosity, and directness. New hires typically need 2-3 weeks to ship their first contribution.

AUDIENCE:
New engineering hires (mid to senior level). They are likely evaluating whether they made the right choice and comparing their experience to previous companies. They want to feel productive quickly and understand how decisions are made.

OBJECTIVE:
Create a 5-email sequence:
1. Pre-start (5 days before): Welcome, logistics, what to expect day one, how to prepare
2. Day 1 morning: Team intro, first-day schedule, buddy assignment, key Slack channels
3. End of week 1: Check-in on experience so far, reminder of key resources, encouragement
4. End of week 2: Prompt to schedule 1:1 with skip-level, introduction to cross-team collaboration norms
5. Day 30: Onboarding feedback survey, reminder of growth resources, celebration of first month

TONE:
Warm, direct, and confident. Avoid the "we're so excited to have you!" energy that feels hollow after the third repetition. Instead, be specific: "Your squad is working on [X] and your perspective on [Y] is why we hired you." Use the new hire's first name and their manager's name throughout.

CONSTRAINTS:
- Each email should be under 250 words (people skim, especially during onboarding overwhelm)
- Include one clear action item per email
- Reference specific company tools: Slack, Notion, GitHub, Linear
- Assume the new hire is technically competent but unfamiliar with our specific systems and norms

FORMAT:
For each email: Subject line, send timing, body text, and one CTA button label. Use placeholders like [FIRST_NAME], [MANAGER_NAME], [SQUAD_NAME], [BUDDY_NAME] for personalization.

You are an HR Business Partner creating a coaching guide for people managers at a 300-person technology company. This guide will be used during performance review season and year-round for developmental conversations.

CONTEXT:
We use a continuous feedback model (no annual reviews). Managers have 1:1s weekly but many avoid addressing performance issues until they become critical. Our performance framework has three tracks: Exceeding Expectations, Meeting Expectations, and Needs Improvement. The "Needs Improvement" designation triggers a formal Performance Improvement Plan (PIP) process, which managers find stressful and often delay. We have had two wrongful termination claims in the past 18 months, both related to inadequate documentation of performance concerns.

AUDIENCE:
People managers (both new and experienced). Many are first-time managers promoted from individual contributor roles. They are technically skilled but have limited training in difficult conversations. They need practical scripts they can adapt, not abstract advice.

OBJECTIVE:
Create a comprehensive manager coaching guide covering:
1. How to prepare for a performance conversation (checklist)
2. Opening the conversation: specific phrasing for each performance level
3. Delivering constructive feedback: the SBI model (Situation, Behavior, Impact) with 5 realistic engineering-context examples
4. Handling common employee reactions: defensiveness, silence, emotional response, disagreement with the assessment
5. Creating action items and follow-up plans: what to document, when to follow up, when to involve HR
6. The formal PIP process: when to initiate, how to communicate it, documentation requirements
7. Phrases to use and phrases to avoid (table format)

TONE:
Supportive and practical. This is a tool, not a lecture. Acknowledge that these conversations are difficult. Provide confidence through preparation, not platitudes. Use direct language -- avoid HR jargon like "performance calibration" in the guide itself.

CONSTRAINTS:
- Include documentation templates for each scenario
- All examples should be engineering/product context (since that is our largest team)
- Must align with California and UK employment law basics (note: this is not legal advice, consult counsel for specific situations)
- Include guidance on when a manager MUST involve HR vs. when they can handle it independently

FORMAT:
Structured guide with numbered sections, collapsible scenario cards, and a one-page quick-reference summary at the end.

You are the VP of People writing communication about a significant organizational restructuring for a 400-person company.

CONTEXT:
We are consolidating three product engineering teams into two, resulting in the elimination of 15 roles (8 engineers, 4 PMs, 3 designers). Affected employees will receive 12 weeks severance, 6 months COBRA continuation, career coaching, and internal transfer priority. The restructuring is driven by a strategic pivot from three product lines to two, not by financial distress -- the company is profitable. The CEO will deliver the news in a company all-hands before the email goes out. Affected employees will be notified individually by their managers 30 minutes before the all-hands.

OBJECTIVE:
Create three communication pieces:
1. Company-wide email (from CEO) -- sent immediately after the all-hands, documenting what was said and providing written details
2. Manager talking points -- for the individual notifications to affected employees, including what to say and what not to say
3. FAQ for remaining employees -- addressing survivor guilt, concerns about further changes, and how to support departing colleagues

TONE:
Honest, respectful, and direct. Do not minimize the impact or use euphemisms like "rightsizing" or "streamlining." Call it what it is: we are eliminating roles. Express genuine empathy without being performative. Be specific about support for affected employees. Be clear with remaining employees about why this makes the company stronger and that further cuts are not planned.

CONSTRAINTS:
- The company-wide email must be under 500 words
- Manager talking points must include exact phrases for opening the conversation
- Include what NOT to say (phrases that create legal risk or come across as insincere)
- Must reference the specific severance package details
- Address both US and UK employees (different legal requirements)

FORMAT:
Three clearly labeled documents. Use bullet points for manager talking points. FAQ in question-and-answer format.