The task
It’s 11pm and a coworker just missed the deadline that breaks Friday’s launch (or pushed back on your design in front of the VP at 2pm, leaving you re-typing your reply three times). You have a draft in Slack that opens with “I’m sorry but…” and gets sharper from there. Before you hit send, you want a version that actually addresses what happened, names what you need next, and doesn’t make next quarter’s collaboration awkward, without softening the issue into a message that doesn’t say anything.
Where AI helps — and where it does not
AI is excellent at de-escalating tone without dropping the substance, removing accidental jabs (“as I’ve said before…”), and adding empathy framing while preserving the ask. It can also produce three tone variants (direct / professional-neutral / warm) so you can pick the one that matches your read of the relationship. What AI cannot do: know the relationship history. Whether this person needs a softer or firmer approach, whether you’ve already had this conversation twice, whether they’re going through something personal: that judgment stays with you.
The named failure mode: the softened-to-nothing message. AI takes “you missed the deadline and now we’re screwed” and produces “Hey, just wanted to check in, no rush!”, which doesn’t raise the issue at all. Force the prompt to keep the substance and only change the tone, and to highlight the sentence that does the work of asking for what you need.
What to feed the AI
- Your raw draft (write it freely, vent on purpose, the worse the better for context)
- The relationship: peer, manager, report, cross-team, contractor
- What you actually need from them: acknowledgment, action, clarification, apology, escalation
- The history: first time this happened, third time, recent reorg, new to team
- The audience: DM (just you two), thread (in front of others), email (paper trail)
- The consequence to surface: what broke, what’s at stake, who else is affected
- 2-3 things you are NOT trying to say (but the draft accidentally implies)
- The single outcome you want from this message (a date, a plan, an apology, a meeting)
Copy-ready prompt
Rewrite my message in 3 tone variants: direct, professional-neutral, and warm.
My raw draft (vent freely):
{paste}
Relationship: {peer / manager / report / cross-team / contractor}
What I actually need from them: {paste — specific outcome}
History: {first time / repeated / recent reorg / new to team}
Audience: {DM / thread / email}
Real consequence to surface: {what broke, who else is affected}
What I am NOT trying to say (but the draft might imply): {list}
The one outcome I want from this message: {a date / a plan / an apology / a meeting}
For each of the 3 variants:
1) Keep the substance. Do NOT soften the issue into silence.
2) Each version under 100 words.
3) Highlight the sentence that does the work of asking for what I need.
4) Highlight the sentence that names the consequence (so it lands).
5) Note which variant fits which relationship read: "use direct if peer trusts you, neutral if cross-team or first conflict, warm if relationship is fragile or person is having a hard quarter."
Rules:
- Remove every "I noticed", "just wondering", "no worries if not", "I'm sorry but…" — passive-aggressive tells.
- Name the issue in the first sentence, not the third.
- Separate "what happened" from "what I need next" — two short paragraphs, not one tangled one.
- Substance stays. Tone changes. If the message can be sent without saying anything, it's too soft.Shorter variant — 1-line de-escalation
Rewrite this Slack draft into a single sendable sentence.
Draft: {paste}
What I need: {paste}
Output: one sentence under 25 words, with the name-the-issue + the ask combined. Strip every hedge.Sample output
A useful 3-variant set for “you missed the deadline and now we’re screwed”:
Direct (peer who trusts you): “Hey — the design review didn’t land Tuesday, which means I’m telling marketing we slip launch by a week. What’s the realistic ship date so I can update them today?” Work sentence: “I’m telling marketing we slip launch by a week.” Consequence sentence: same.
Professional-neutral (cross-team or first conflict): “Hi — I haven’t seen the design review come through; it was on the schedule for Tuesday. Marketing is waiting on it to lock the launch announcement. Can you let me know the realistic date so I can plan around it?” Work sentence: “Can you let me know the realistic date?” Consequence sentence: “Marketing is waiting on it.”
Warm (fragile relationship or person having a hard quarter): “Hey — I know things have been packed. The design review missed Tuesday, and marketing’s waiting on it for the launch. Can we sync briefly tomorrow so I can give them a realistic date?” Work sentence: “Can we sync briefly tomorrow.” Consequence sentence: “marketing’s waiting on it.”
A useful note on which to send: “Use direct if this is a peer who can take it and the trust is high. Use neutral if it’s cross-team or your first conflict with them. Use warm if you’ve already had this conversation once and tone is fragile.”
How to refine
- Kill the passive-aggressive tells: “Delete every ‘I noticed’, ‘just wondering’, ‘no worries if not’, ‘I’m sorry but’. Those are tells; the message reads worse with them than without.”
- Name the issue first: “First sentence must name the issue, not preamble. ‘The design review didn’t land Tuesday’ beats ‘I wanted to follow up on something.’”
- Separate what-happened from what-I-need: “Two short paragraphs: paragraph 1 is what happened + the consequence. Paragraph 2 is the specific ask. Don’t tangle them.”
- Make the consequence land: “Name a specific person or thing that’s affected. ‘Marketing is waiting on it’ beats ‘this is blocking things.’ Vague consequence = no urgency.”
- Pressure-test against silence: “Could the recipient read this message and do nothing? If yes, the ask isn’t sharp enough. Rewrite the ask as a date, a meeting, or a binary answer.”
Common mistakes
- Sending the angry draft. You cannot unsend, and the receipts last forever; the cost is months of awkwardness
- Softening so much the message doesn’t raise the issue: feels safe, achieves nothing, the problem repeats
- Mixing the ask into the venting: “you missed the deadline and now we’re screwed, what’s going on with you?” is two messages glued together badly
- Sending to a public channel when DM was the right channel: public asks read as ambush
- CC-ing your manager pre-emptively on peer conflict: escalation before conversation usually damages the relationship more than the original miss
- Letting AI add empathy padding that isn’t true (“I know you’ve been under a lot lately”): false empathy reads as condescending
- Forgetting to leave a paper trail when you need one: verbal-only conversations on cross-team issues don’t survive reorgs
- Sending the message immediately after AI rewrites: read it once at full energy, sit for 10 minutes, then read again before sending
FAQ
- When should I send anything at all vs. talk in person?: Send text if you need a paper trail, an async response, or the recipient is in a different timezone. Talk in person (or video call) if you need to repair a relationship, calibrate tone in real-time, or sense the other person’s read. Avoid text for the relationship-repair conversation; text strips the tone that does the repair work.
- Should I send this to my manager first?: For cross-team escalations where you actually need them to intervene, yes; surface early. For peer conflicts, only if the peer is non-responsive or the issue has happened repeatedly. Pre-emptive CC reads as “I don’t trust you to handle this” and damages the relationship more than the original miss.
- What if the message will be re-read later in a calmer state?: Always assume yes. Slack history is forever, screenshot culture is real, and the relationship outlasts the conflict. The version you send is the version that lives.
- Should I apologize for raising the issue?: No. Apologizing for raising a legitimate issue (“sorry to bother you with this”) signals the issue isn’t legitimate. State the issue. If you’ve contributed to it, own that specifically (“I should have flagged this earlier”).
- What if I send the AI rewrite and they respond defensively?: That’s information. The defensiveness is about them, not the message. Don’t escalate via Slack; reply briefly, then move to a call. Most defensive responses dissolve in 5 minutes of voice.