Write the hard emails (bad news, saying no, complaints, corrections) so they are clear, kind, and preserve the relationship. Use when an email must deliver something unwelcome without making it worse.
Scanned 9/5/2026
Install to Claude Code
npx -y skills add Amey-Thakur/AI-SKILLS --skill difficult-emails --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Difficult Emails?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/amey-thakur-difficult-emails)More formats (shields.io, HTML) on the badges page.
---
name: difficult-emails
description: Write the hard emails (bad news, saying no, complaints, corrections) so they are clear, kind, and preserve the relationship. Use when an email must deliver something unwelcome without making it worse.
---
# Difficult emails
The hard emails (delivering bad news, declining, raising a complaint,
correcting a mistake) are where email skill matters most and where it most
often fails: people either soften into vagueness or harden into
aggression. The craft is being clear about the hard thing while staying
kind and constructive.
## Method
1. **Be clear about the hard part; do not bury it.** The temptation is to
pad, hedge, or hide the bad news so deep the reader misses it. Say it
plainly and reasonably early. A decline dressed as a "maybe", or a
problem never quite stated, wastes everyone's time and reads as evasive
(see decline-politely prompt).
2. **Lead with enough warmth and context to land it.** A brief, genuine
acknowledgment (of their work, the situation, the relationship) before
the hard part cushions it without burying it. Not a fake compliment
sandwich; a real, short human framing so the reader is not blindsided
(see email-tone).
3. **Explain briefly, do not over-justify.** Give the reason if it helps
(why the no, what went wrong), in a sentence or two. A pile of excuses
reads as guilt and invites argument; you are allowed to deliver bad news
without an exhaustive defense. State it, reason once, move on.
4. **Focus on the situation, not the person.** For complaints and
corrections, address the problem and the fix, not blame ("the report had
three errors, here they are" not "you are careless"). Depersonalizing
keeps the reader able to respond constructively rather than
defensively (see giving-feedback's situation-behavior-impact).
5. **Offer a path forward.** Where you can, give the next step: an
alternative, a way to fix it, a smaller yes, a solution to the complaint.
Ending on what can be done rather than only the problem preserves the
relationship and moves it toward resolution.
6. **Cool down before sending, and reread as the reader.** Never send a
difficult email while angry; draft it, wait, and reread imagining you
are receiving it. Cut anything sarcastic, blaming, or passive-aggressive.
For the hardest cases, ask whether it should be a conversation instead
(see the medium boundary below).
## Boundaries
- The hardest conversations should not be emails: firing, serious conflict,
deeply sensitive feedback, or anything that will spiral over text belongs
in a call or in person, where tone and back-and-forth exist (see
giving-feedback, async-communication).
- Kindness is not vagueness: the failure mode of trying to be nice is
burying the message until the reader does not realize what was decided.
Clear and kind together, never one at the cost of the other.
- Email is permanent and forwardable; a difficult email may be read by
others later, so keep it professional and factual, never something you
would regret being seen (see email-etiquette).
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!