Playbook, writing
Rewrite hard emails without losing your point
The blunt draft is your friend. Our routine keeps the point, fixes the tone, and gets the hard email out the door.
The short version
- Write the blunt draft first; you own the message, the model owns the manners.
- Give it the reader, the stakes, and the relationship in one line.
- Freeze the ask, the date, and the no before any rewrite.
- Ask for a warm version and a direct version, then blend.
- Rewrite one sentence by hand so the email still sounds like you.
The hardest emails carry a no. Declining a project, chasing a late invoice, telling a client the date slipped. We write those backwards now: first a blunt draft that says exactly what we mean with zero softening, then a handoff where the model fixes the tone. The split is the trick. We own the message. The model owns the manners.1
Tone control works when you name three things: who is reading, what relationship you are protecting, and what cannot change. Anthropic's docs call this giving the model a role, and OpenAI's prompting guide pushes the same idea from the other side: specific instructions with real context beat vague asks every single time.1 2
Any current chat model handles this well, so use whichever tab is already open. The routine is the asset, not the brand. It's also the first move in learning to write with AI: separate what you say from how you say it, and never let a rewrite touch the what.
Here's the five-step routine we run on every hard email.
- Write the blunt version first. Say the true thing in plain words: we can't take this on, the invoice is 60 days late, the launch moved. No softening yet. This draft is for you, not for them.
- Give the model the scene. Paste the draft with one line of context: who the reader is, what you need them to do, and how much the relationship matters. A rewrite for your manager and a rewrite for a vendor are different emails.
- Freeze what cannot change. Tell it the ask, the date, and the no are fixed. Everything else is negotiable. Without that rule, polite rewrites quietly drop the deadline.
- Ask for two versions, one warm and one direct. Reading them side by side shows you the dial, and the best email is usually a sentence from each.
- Read the winner out loud, then rewrite one sentence in your own words. A message that is all model sounds like a press release, and nobody believes a press release that says sorry.
The routine earns its keep on the worst messages. A refund refusal, a missed commitment, an apology that might get forwarded. For those we add one question: what could a hostile reader lift out of context? The model finds the screenshot sentence with unsettling reliability. We rewrite that sentence by hand.
We own the message. The model owns the manners.
One warning. Models over-soften by default, and a hard message wrapped in three paragraphs of appreciation reads as evasive, which lands worse than blunt ever would. The vendor guides push specificity for exactly this reason: vague prompts produce padded prose. If the rewrite buries your ask below the fold, cut the cushion and send the short one.2
Use it this week
- Save this rewrite prompt and paste your blunt draft under it whenever an email is hard to send.Rewrite the email below the line. Reader: [who they are and what they are to me]. Goal: they should [action] by [date]. These are fixed and must survive the rewrite: the ask, the date, and anything I decline. Give me two versions, one warm and one direct, each under 150 words. No corporate filler. --- [paste blunt draft]
- Before sending a high-stakes message, run the hostile-reader check on your final draft.Read this email as a hostile reader who might forward or screenshot it. Quote the single sentence most likely to be taken out of context and explain the bad reading. Then suggest a safer wording that keeps the same meaning. --- [paste final draft]