ChatGPT Prompts for Work

Write a professional email for me.

Context:
- Purpose: [request / follow-up / introduction / thank you / apology / announcement]
- Recipient: [their name, role, and relationship to me]
- My role: [your title and department]
- Tone: [formal / friendly-professional / assertive / empathetic / urgent]
- Key message: [the main point you need to communicate]
- Background: [any relevant context the recipient needs]
- Desired outcome: [what you want the recipient to do after reading this]

Write the email with:
1. A subject line that gets opened (specific, not vague — never "Quick Question" or "Touching Base")
2. An opening line that establishes context without wasting time
3. The core message in 2-3 concise paragraphs
4. A clear, specific call-to-action (not "let me know your thoughts" — tell them exactly what you need)
5. A professional sign-off appropriate for the tone

Then write 2 alternative versions:
- **Shorter version**: Same message in half the words, for busy executives
- **Softer version**: Same message but more diplomatically phrased, for sensitive situations

Flag if any part of my message could be misinterpreted or sound passive-aggressive.

Write my weekly status report.

My role: [title and team]
Reporting period: [this week's dates]
Manager/audience: [who reads this]

What I accomplished this week:
[List your completed tasks, wins, and progress — even rough notes are fine]

What I'm working on next week:
[List planned tasks and priorities]

Blockers or concerns:
[Anything slowing you down, or "none"]

Generate a polished status report with:
1. **Highlights** (3-5 bullet points): Accomplishments framed as outcomes, not tasks. "Shipped the onboarding flow redesign, reducing drop-off by 15%" beats "Worked on onboarding."
2. **In Progress**: Current work items with estimated completion dates
3. **Upcoming**: Next week's priorities, ranked
4. **Blockers & Risks**: Anything that needs my manager's attention or help
5. **Metrics** (if applicable): Key numbers that show progress
6. **Wins & Shoutouts**: Credit teammates who helped

Keep the total length under 200 words. My manager should be able to read this in under 60 seconds.

Create a focused meeting agenda.

Meeting details:
- Purpose: [what needs to be accomplished — be specific]
- Type: [decision-making / brainstorm / alignment / planning / review]
- Duration: [X minutes]
- Attendees: [list names and roles]
- Context: [what's happening that makes this meeting necessary right now]
- Pre-read materials: [any docs, data, or context attendees should review beforehand]

Generate:
1. **Meeting title**: Specific and outcome-oriented (not "Sync" or "Check-in")
2. **Pre-meeting prep**: What each attendee should review or prepare (keep under 10 minutes)
3. **Agenda with strict time-boxing**:
   | Time | Topic | Owner | Type (Inform/Discuss/Decide) | Expected Output |
   |------|-------|-------|------------------------------|-----------------|
4. **Opening question**: One question to focus the group immediately
5. **Decision framework**: How decisions will be made if consensus isn't reached
6. **Last 5 minutes**: Recap decisions, assign action items with owners and deadlines
7. **"Could this be an email?" check**: Honestly assess if this meeting is necessary

Also include a post-meeting template:
- Decisions made
- Action items (who, what, by when)
- Open questions for follow-up
- Next meeting needed? (yes/no, and why)

Help me prioritize my workload using a structured framework.

My role: [title]
Time horizon: [this week / this sprint / this quarter]

Current tasks and projects:
[List everything on your plate — don't filter, dump it all here]

For each item, I'll note (if I know):
- Deadline: [hard deadline / soft deadline / no deadline]
- Stakeholder: [who's waiting on this]
- Estimated effort: [hours or t-shirt size]
- Impact: [what happens if this gets done vs. doesn't]

Now help me:
1. **Eisenhower Matrix**: Sort everything into Urgent+Important, Important+Not Urgent, Urgent+Not Important, Neither
2. **Stack rank**: Give me a numbered priority list with rationale for each ranking
3. **Time blocks**: Suggest how to structure my day/week around these priorities
4. **Delegation candidates**: Which tasks could someone else handle?
5. **Kill list**: Which tasks should I drop entirely or push to next quarter?
6. **Quick wins**: Which items take under 30 minutes and would clear mental space?
7. **Energy mapping**: Match high-effort tasks to my peak energy hours and low-effort tasks to energy dips

Be honest — if I have more work than hours, tell me what to cut. Don't pretend everything fits.

Help me prepare for my one-on-one meeting.

Meeting with: [manager / direct report / skip-level]
Frequency: [weekly / biweekly / monthly]
Current situation:
- My role: [title and tenure in role]
- Current projects: [what I'm working on]
- Mood/energy: [how I'm feeling about work honestly]
- Topics I want to discuss: [list anything on your mind]
- Recent wins: [things that went well]
- Recent frustrations: [things that didn't go well]

Generate a prep sheet:

**If meeting with my manager:**
1. 3 updates to share (outcome-focused, under 30 seconds each)
2. 1 specific ask or blocker I need help with
3. 1 career development topic to raise
4. 2-3 questions to ask my manager about team/company direction
5. A way to bring up [frustration/concern] constructively

**If meeting with my direct report:**
1. 3 coaching questions to understand their current state
2. 1 piece of specific, actionable feedback (positive or constructive)
3. Questions about their career goals and growth areas
4. A check on workload and well-being
5. Follow-up on action items from our last 1:1

**For either:**
- Suggested talking points ordered by priority
- Time allocation (don't spend 25 minutes on updates and 5 on what matters)
- One question I should ask that I'm probably avoiding

Help me write a compelling performance self-review.

Context:
- Review period: [dates]
- My role: [title, level, department]
- Company values or competencies I'm evaluated on: [list them if you know]
- Promotion consideration: [yes / no / maybe]

My accomplishments this period:
[List everything you did — projects, wins, improvements, even small ones. Brain dump.]

Challenges I faced:
[What was hard, what didn't go perfectly]

Growth areas:
[Skills I developed or want to develop]

Write a self-review that:
1. **Impact summary** (2-3 sentences): My biggest contribution this period, framed as business impact
2. **Key accomplishments** (5-7 bullets): Each with the STAR format — Situation, Task, Action, Result. Quantify results wherever possible (%, $, time saved)
3. **Challenges & learnings**: 2-3 honest reflections on what was difficult and what I learned. Frame these as growth, not excuses
4. **Collaboration & leadership**: Examples of how I helped others succeed, mentored, or influenced without authority
5. **Goals achieved**: Map back to goals set at the beginning of the period
6. **Development areas**: 2 specific skills I want to grow, with a plan for each
7. **Goals for next period**: 3-4 measurable goals for the upcoming review cycle

Tone: confident but not arrogant. Data-driven. Show impact, not just activity. Avoid corporate buzzwords.

Help me write a Slack or Teams message for a work situation.

Context:
- Channel/audience: [#channel-name, DM, or group chat]
- Situation: [what's happening — be honest about the full picture]
- My goal: [what I want to achieve with this message]
- Tone needed: [casual / professional / urgent / diplomatic / celebratory]
- Sensitivity level: [low / medium / high — could this be screenshot'd or forwarded?]

Write the message with:
1. **The message itself**: Concise, scannable, appropriate for the platform. Use bullet points or numbered lists for anything over 3 sentences.
2. **Threading strategy**: Should follow-up details go in a thread? What should the top-level message contain vs. thread replies?
3. **Emoji/reaction guidance**: Appropriate emoji usage for the tone (or none)
4. **Timing suggestion**: When to send this for maximum visibility and minimal disruption

Write 3 versions:
- **Direct**: Gets to the point fast
- **Diplomatic**: Same message but softer for sensitive situations
- **With context**: Includes more background for people who need it

Also flag if this message:
- Should be a DM instead of a channel post
- Needs a follow-up message or reminder
- Could be misread without tone (and how to prevent that)

Write a project update for stakeholders.

Project: [name]
Stakeholder group: [executives / clients / cross-functional partners / board]
Update type: [milestone reached / progress check-in / risk escalation / pivot announcement]

Current status:
- Timeline: [on track / at risk / delayed] — explain why
- Budget: [on track / over / under] — explain why
- Scope: [unchanged / expanded / reduced] — explain why
- Team health: [strong / stretched / concerned]

Key developments since last update:
[List what happened]

Decisions needed from stakeholders:
[What you need them to approve, fund, or unblock]

Write the update in two formats:

**Email version** (under 300 words):
1. One-line status summary with RAG indicator
2. 3 key bullets: biggest win, biggest risk, biggest ask
3. Detailed progress by workstream
4. Next milestones and dates
5. Clear ask: what you need from them and by when

**Presentation slide version** (3 slides):
- Slide 1: Executive summary dashboard
- Slide 2: Progress details with key metrics
- Slide 3: Risks, asks, and next steps

Use data and specifics. Avoid vague phrases like "making good progress" — quantify everything.

Write an out-of-office auto-reply for me.

Details:
- Dates away: [start date] to [return date]
- Reason: [vacation / parental leave / conference / medical / sabbatical — or just "personal time"]
- Urgency coverage: [who handles urgent issues while I'm out]
- Backup contact: [name and email/Slack of my backup]
- Projects in flight: [any active projects and their status/point of contact]
- Email check frequency: [not at all / once daily / emergencies only]
- Tone: [professional / warm / casual-fun / minimal]

Write:
1. **External OOO** (for clients, vendors, external contacts):
   - Professional, reassuring, includes backup contact
   - Sets clear expectations on response time
   - Doesn't over-share why I'm away

2. **Internal OOO** (for colleagues):
   - Slightly more casual
   - Lists who to contact for specific topics
   - Links to any handoff docs or coverage plans

3. **Slack status**: A one-liner with return date and backup contact

4. **Pre-departure message**: A proactive Slack/email I can send to my team and key stakeholders 2-3 days before I leave, covering:
   - What's wrapped up
   - What's handed off and to whom
   - What can wait until I'm back
   - How to reach me in a true emergency (or that you can't be reached)

Help me write a professional request for a deadline extension.

Context:
- What's the deliverable: [project, report, feature, etc.]
- Original deadline: [date]
- Requested new deadline: [date]
- Why the extension is needed: [be honest — scope change, underestimation, blockers, competing priorities, resource issues]
- Who I'm asking: [manager / client / stakeholder — their role and our relationship]
- What I've already done: [work completed so far, effort invested]
- Impact of missing the original deadline: [what happens if we don't extend]
- Impact of the extension: [what happens to downstream work or dependencies]

Write a request that:
1. **Acknowledges the commitment**: Don't pretend the original deadline didn't exist
2. **Explains the why clearly**: Not excuses — legitimate reasons framed as factors that affected the timeline
3. **Shows what's been done**: Demonstrate progress so it's clear you're not starting from scratch
4. **Proposes a specific new timeline**: Not "soon" — an actual date with a brief plan to hit it
5. **Offers a partial delivery option**: Can you ship a subset by the original date and the rest later?
6. **Prevents recurrence**: What you'll do differently to avoid this happening again
7. **Gives them options**: Let the stakeholder choose between 2-3 paths forward

Write two versions:
- **For your manager**: More transparent, includes the full context
- **For a client**: More polished, focuses on solutions not problems

Help me write a proposal for cross-team collaboration.

Context:
- My team: [name, what we do, size]
- Their team: [name, what they do, size]
- The opportunity: [what could we accomplish together that neither team can do alone]
- Current pain point: [what's broken or suboptimal without collaboration]
- My relationship with their team: [new / existing / previous friction]

Write a collaboration proposal that:
1. **Hook** (2 sentences): Frame the problem from THEIR team's perspective, not yours. What's in it for them?
2. **The opportunity**: What we could build, improve, or solve together — with estimated impact
3. **Current state**: What each team is doing independently and where efforts overlap or conflict
4. **Proposed model**:
   - Shared goal with measurable success metrics
   - Roles and responsibilities (who owns what)
   - Communication cadence (weekly sync? shared Slack channel? joint standup?)
   - Decision-making framework for disagreements
   - Resource commitment from each team (be specific — hours/week, not "support")
5. **Pilot proposal**: Start small — a 4-6 week pilot with clear success criteria before committing long-term
6. **Risk mitigation**: Address the common concerns:
   - "We don't have bandwidth" — show this saves time, not adds it
   - "Our priorities are different" — show the aligned interest
   - "Who gets credit?" — propose shared OKRs or dual-reporting
7. **Next step**: A specific ask — "Can we have a 30-minute call to explore this?"

Also write a brief Slack message I can send to their team lead to introduce the idea before the formal proposal.

Help me optimize my work-from-home schedule for maximum productivity.

My situation:
- Role: [title and type of work — creative, analytical, meetings-heavy, etc.]
- Work hours: [required hours and any flexibility]
- Hybrid schedule: [which days office vs. home, or fully remote]
- Peak energy hours: [when I do my best deep work — morning, afternoon, etc.]
- Meeting load: [average meetings per day/week]
- Biggest productivity killers: [Slack notifications, back-to-back meetings, context switching, etc.]
- Home environment: [dedicated office, shared space, kids at home, etc.]
- Tools I use: [Slack, Zoom, email, project management tools, etc.]

Design an optimized schedule:

1. **Daily time blocks**:
   | Time | Activity Type | Environment Setup | Communication Mode |
   |------|--------------|-------------------|-------------------|
   Map deep work to peak energy. Map meetings to low-energy windows. Include breaks.

2. **Communication boundaries**:
   - When I'm available for instant responses (Slack/Teams)
   - When I'm in focus mode (notifications off, status set)
   - Expected response times by channel type
   - How to signal urgent vs. non-urgent to my team

3. **Meeting optimization**:
   - Which meetings to batch on specific days
   - Suggested "no meeting" blocks to protect
   - How to handle the "quick call?" requests that fragment focus time

4. **Environment setup**:
   - Physical workspace optimization tips
   - Digital environment (which apps open when, notification settings)
   - Transition rituals between work and personal time

5. **Weekly rhythm**:
   - Monday: [planning/alignment]
   - Tuesday-Thursday: [execution]
   - Friday: [review/admin/learning]
   Customize this based on my specific work patterns.

6. **Accountability system**: How to track whether this schedule actually works and iterate.