Difficult Emails SKILL.md

This is the exact file agents read, including the credit header and licence notice. Save it as difficult-emails/SKILL.md.

---
name: difficult-emails
description: "Write difficult emails that stay calm, clear and fair: goal first, facts separated from feelings, a channel check, structures for complaints, bad news, refusals, pushback, apologies, boundaries and negotiation, an escalation check for blame and passive-aggressive phrases, recipient choices and a pause before sending. Use whenever someone needs to reply to an angry customer or colleague, deliver bad news, say no, push back on scope or price, apologise, set a boundary, negotiate by email or write a message they have been avoiding."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/productivity/email-inbox/difficult-emails/
  category: productivity
  subcategory: email-inbox
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-13"
---

# Difficult Emails

Some emails sit in drafts for days: replying to an angry client, telling a manager a deadline will slip, declining a friend's request, pushing back on unfair terms, apologising for a mistake or setting a boundary with a colleague. Written messages lose tone of voice and facial expression, so they are easily read as colder or harsher than intended, and a rushed reply can escalate a problem a calm one would settle.

This skill helps write difficult emails that stay calm, clear and fair. It works out the goal, separates facts from feelings, chooses whether email is even the right channel, picks a structure for the situation (complaint, bad news, refusal, pushback, apology, boundary or negotiation), drafts in a steady tone, checks for anything that could escalate, and suggests waiting before sending when emotions are high.

## Operating principles
1. **Goal first.** Decide the outcome wanted: fix, inform, decline, agree terms or repair the relationship.
2. **Facts over feelings.** State what happened and what will happen next; acknowledge feelings without arguing about them.
3. **Clear, not cold.** Kind wording with a clear message beats softened messages that confuse.
4. **Right channel.** Very sensitive news, conflict or grief often needs a call or meeting, with email as a follow-up.
5. **Pause before sending.** When angry or anxious, draft now and send after a break.

## Structures by situation
| Situation | Structure |
|---|---|
| Complaint from a customer | Thank, acknowledge the impact, own what is yours, say what you are doing and by when, offer a direct contact |
| Bad news (delay, rejection, price rise) | The news in the first line, the reason in one or two sentences, what happens next, what you can offer |
| Saying no | Appreciation, a clear no, a brief reason if helpful, an alternative or referral |
| Pushing back | Shared goal, the specific concern, evidence, a proposal, an invitation to discuss |
| Apology | What went wrong, its effect, responsibility without excuses, the fix, how it will be prevented |
| Boundary | The behaviour, its effect, the request, what will happen next time |
| Negotiation | Interest in agreement, what works, what needs to change and why, a specific counter-proposal |

## When to use, and when not to
Use it for complaints, conflict, escalations, bad news, refusals, pushback on scope or price, apologies, boundaries and messages to senior people about problems.

Don't use it for legal disputes, formal grievances, disciplinary matters or anything involving safety, harassment or discrimination without advice from HR, a lawyer or the right authority. The skill can help prepare notes for those conversations.

## Inputs
- The full thread or situation.
- The outcome the user wants.
- Facts: dates, what was agreed, what happened.
- The relationship and what must be protected.
- Constraints: what the user can and cannot offer.

## Workflow

### Step 1. Check the channel
If the issue is emotional, complex, or likely to need back-and-forth, suggest a call first and an email summary after.

### Step 2. Write the goal and the facts
One sentence for the goal; a short list of facts, separated from interpretations.

### Step 3. Read the other person's view
What do they want, what are they worried about, what is reasonable in their position?

### Step 4. Choose the structure
From the table above.

### Step 5. Draft
Short sentences, the key message early, specific next steps and dates, no sarcasm, no blame words such as "you failed to", no all-caps or exclamation marks.

### Step 6. Run the escalation check
Remove or rewrite: absolute words ("always", "never"), accusations, defensive explanations, passive-aggressive phrases ("as per my last email", "going forward, please"), and anything the user would not say face to face.

### Step 7. Decide who sees it
Keep recipients to those who need it; avoid adding managers to Cc as pressure unless escalation is the goal and stated openly.

### Step 8. Pause and send
Suggest a delay of at least an hour, or overnight for heated situations, and a final read as the recipient.

## Example: deadline will slip
**Draft:**
```
Hi Sam, the onboarding report won't be ready on Friday as planned.
The data export arrived three days late, and I'd rather not send
numbers I haven't checked. I can send the full report next Wednesday,
or a summary of the first two sections on Friday if that helps your
board prep. Which would you prefer?
```
The news comes first, the reason is short and factual, and Sam gets a choice.

## Example: angry client
```
Hi Lena, thank you for telling us, and I'm sorry the delivery
arrived damaged. That's not the experience we want for you.
We've sent a replacement by express today (tracking: [number]),
and refunded the delivery fee. I'm your direct contact for this;
if anything else isn't right, reply here and I'll sort it.
```

## Phrases to avoid and alternatives
| Avoid | Use instead |
|---|---|
| As per my last email | To recap, ... |
| You failed to send | We haven't received ... yet |
| I'm sorry you feel that way | I'm sorry this caused ... |
| That's not my job | The right person for this is ... |
| Unfortunately, there's nothing we can do | Here's what we can do ... |
| Going forward, please make sure | Could we agree that ... |

## Output format
```
1. Recommended channel (email, call first, or meeting)
2. Goal and facts
3. Draft email (and a firmer or softer alternative if useful)
4. Escalation check: phrases changed and why
5. Recipients and timing advice
```

## After sending
If the reply is still heated, do not answer point by point by email; suggest a short call and confirm agreements in writing afterwards. Note what was agreed and any follow-up dates in the task list so promises made under pressure are kept.

Keep a copy of important difficult emails and replies in the project file.

When in doubt, call first.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| User is very angry | Draft for release later; suggest waiting overnight |
| Legal or HR risk | Keep factual; suggest advice before sending |
| Message to a senior person | Lead with impact and the proposal; keep it brief |
| Cultural differences | Adjust directness; avoid idioms; stay polite and clear |
| Repeated problem with one person | Move to a conversation; email to confirm agreements |
| Public or group thread | Move the conflict to a private message |

## Handoffs to related skills
- Everyday replies: `email-reply-drafting`
- Clear structure: `email-writing-clarity`
- Chasing without friction: `follow-up-tracking`
- Reusable polite refusals: `email-templates`

## Worked example
A project lead must tell a client that a feature will be two weeks late and push back on extra work added without a budget change. The skill suggests a short call first and drafts the follow-up email: the delay in the first line with the cause, the new date and a mitigation, then the scope point framed around the shared launch goal, listing the three new requests and proposing either a change order or moving them to phase two. The escalation check removes "as we've said repeatedly" and a Cc to the client's manager. The client agrees to phase two.

## Common mistakes
- Burying the news under apologies.
- Sending while angry.
- Blame words and passive-aggressive phrases.
- Copying managers to apply pressure.
- Using email for conversations that need a call.

## Self-check before you answer
- Is the goal clear, and is the key message early?
- Are facts separated from feelings and blame?
- Was the escalation check run?
- Is email the right channel, and is there a pause before sending?

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/productivity/email-inbox/difficult-emails/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.