✉ Draft a sensitive message you can stand behind

الـ workflow

1. 01

   Brief Claude on the situation and the guardrails — including what NOT to say

   Sensitive messages go wrong by saying too much, not too little. Set the guardrails before any drafting: what's confirmed, what's off-limits, and that nobody gets named — so the draft starts inside the lines.

   أنت تطلب انسخ

   I need to write a sensitive [reorg / feedback / org-change] message. Here's the situation: [brief]. Before drafting, read it back to me: who this is for, the one thing they most need to know, what is actually decided vs still open, and what I must NOT say or promise yet. Keep all individual names out — use roles or [placeholders]. Don't write the message yet.

   ما تحصل عليه A short read-back — audience, the core message, decided-vs-open, and an explicit "won't say" list — that catches a wrong assumption now, before it's wrapped in three careful paragraphs.

   The 'read it back to me first' move matters most here: confirm Claude has the situation right before it writes a word, because the cost of a wrong sensitive message is high.

2. 02

   Draft for honest and kind — not upbeat

   Ask for the hard balance explicitly. The failure modes are corporate-cold and falsely cheerful; name both so the draft is direct about the difficulty and still human.

   أنت تطلب انسخ

   Now draft the message: honest about the hard part, kind and respectful, plain English, no corporate euphemism and no false cheer. Don't over-promise — where I can't commit, say what we can and can't say yet. Lead with the thing they most need to know. Keep it short. Use [placeholders] for any date, name, or number I still have to confirm.

   ما تحصل عليه A tight draft that names the hard thing directly, stays warm without sugarcoating, makes no promise you flagged as off-limits, and carries visible [placeholders] exactly where you still owe a confirmed detail.

3. 03

   Pressure-test how it will land

   Before you touch a word, have Claude read it as the recipient. The gap between what you meant and what they'll hear is where sensitive messages do damage.

   أنت تطلب انسخ

   Read this back as the person receiving it. What's the first feeling it creates? What question will they immediately have that the message doesn't answer? Where might it sound like a promise I didn't mean to make, or where am I burying the real point? Flag anything that could read as cold, evasive, or over-promising.

   ما تحصل عليه A recipient's-eye read — "opens warm but the 'what happens to my role' question is unanswered until paragraph 3", "'we'll take care of everyone' reads as a guarantee" — pointing you at the exact lines to fix.

   This is the step that prevents the 11pm rewrite after it's already sent. Spend the time here, not in the reply thread.

4. 04

   Tighten, then leave it ready for your word-for-word read

   Do a final pass on the flagged lines, then deliberately stop — the draft is a shape you own, and the last act is always a human reading every word before send.

   أنت تطلب انسخ

   Tighten the lines you flagged: answer the immediate question earlier, soften nothing that should stay honest, and remove any accidental promise. Give me the final draft with every [placeholder] clearly marked, and a one-line checklist of what I personally need to confirm before sending.

   ما تحصل عليه A clean final draft with the flagged issues fixed, [placeholders] clearly marked, and a short confirm-before-send checklist — ready for you to read aloud, fill in, and own.

   Read every word yourself, out loud if you can. Claude gives you a shape; you own what actually ships and what it promises.

ستحصل في النهاية على A sensitive message you can stand behind — honest about the hard part, kind without over-promising, names kept out and details left as placeholders — pressure-tested for how it lands and ready for the word-for-word read that only you can do.