Case 28
Executive Email in My Voice
Scenario
You are a Chief Operating Officer who writes short, direct emails. AI drafts keep coming back long and generic. You need to tell your leadership team that a project deadline is moving.
Why this framework
Uses full PINPOINT because the consequence is higher: adds a professional stance, examples, self-checks, your own review before use, and a plan to tweak and test.
Example context
Project update (extract): The Orbit customer platform launch moves from 14 March to 19 May. Reason: the payments integration failed security testing in October and the supplier needs six weeks to fix and retest. Budget is unchanged at £1.8m; extra supplier cost of £60k is covered by contingency. Sales will keep selling the current system until May. Customer support training moves to the week of 5 May. Next formal update: Friday 20 November. Sample email 1: "Team, quick note on hiring. We are pausing two roles until January. Reason is simple: we want the new structure settled first. Please hold any offers. I will confirm the restart date on 4 December. Thanks for the steady work. Priya" Sample email 2: "All, the Leeds site visit is on. Tuesday, 9am. Please bring your numbers, not slides. I want to hear what is hard, not what is going well. Questions to me directly. Priya" Sample email 3: "Hello everyone, good news on the audit. No major findings. Two small fixes, both owned and due by month end. Thank you to Finance for the long hours. Priya"
Prompt
Purpose: Draft an email to my leadership team explaining that the platform launch is moving from March to May, and what that means for them.
Context: Use the attached project update for facts. Use the three attached emails I have written before as examples of my style.
Narrow the ask: Under 180 words. Lead with the news, then the reason, then what I need from them, then the next update date.
Persona and role: Write as me: direct, warm, no corporate jargon.
Examples: Match the sentence length and tone of my sample emails. Bad: "I wanted to reach out to provide a brief update regarding our exciting journey." Good: "The launch is moving to May. Here is why and what it means for you."
Check your work: Confirm every fact comes from the project update. List any phrase you think sounds unlike me.
Before I use it: I will read it aloud and edit before sending.
Materials (pasted here in place of the attachments):
Project update (extract): The Orbit customer platform launch moves from 14 March to 19 May. Reason: the payments integration failed security testing in October and the supplier needs six weeks to fix and retest. Budget is unchanged at £1.8m; extra supplier cost of £60k is covered by contingency. Sales will keep selling the current system until May. Customer support training moves to the week of 5 May. Next formal update: Friday 20 November.
Sample email 1: "Team, quick note on hiring. We are pausing two roles until January. Reason is simple: we want the new structure settled first. Please hold any offers. I will confirm the restart date on 4 December. Thanks for the steady work. Priya"
Sample email 2: "All, the Leeds site visit is on. Tuesday, 9am. Please bring your numbers, not slides. I want to hear what is hard, not what is going well. Questions to me directly. Priya"
Sample email 3: "Hello everyone, good news on the audit. No major findings. Two small fixes, both owned and due by month end. Thank you to Finance for the long hours. Priya"Example output from ChatGPT
Team,
The Orbit customer platform launch is moving from 14 March to 19 May.
Reason is simple: the payments integration failed security testing in October. The supplier needs six weeks to fix it and retest.
The budget stays at £1.8m. The extra £60k supplier cost is covered by contingency.
What I need from you:
- Sales: keep selling the current system until May.
- Customer Support: move training to the week of 5 May.
The next formal update is Friday 20 November.
Thanks for keeping things moving.
Priya
Check against your brief
- Facts: All dates, costs, reasons and actions come directly from the project update. No new commitments or assumptions.
- Style: Short sentences, direct opening, plain language and a simple closing. Closely matches your three samples.
- Structure: News → reason → actions → next update.
- Length: Approximately 100 words, comfortably under 180.
Phrases that may sound unlike you:
"Thanks for keeping things moving" is slightly more generic than your examples. Your usual "Thanks for the steady work" may sound more natural.
The rest fits your sample tone well.
