You need to tell someone something difficult. Maybe it’s that their deliverable isn’t good enough. Maybe it’s that you need to push back on a deadline. Maybe it’s that you’re escalating a problem. The conversation feels too heavy for a quick Slack message, but scheduling a meeting for it feels like overkill.
The answer is usually a well-written email. But writing it feels impossible.
Here’s how to get it right.
—
## Why Email Works for Hard Conversations
A hard conversation over email gives both parties something synchronous communication doesn’t: time to think.
The recipient can read it when they’re calm, process it without the pressure of an immediate response, and formulate a thoughtful reply. Done right, email is more humane than a live conversation for anything that’s not purely emotional.
The key is writing it in a way that doesn’t read as passive-aggressive, cold, or aggressive. That’s the challenge.
—
## The Structure That Works
Every hard conversation email should have three parts:
**1. The opener — name what you’re doing**
Don’t bury the lead. Open with context so the reader knows exactly what the email is about before they read the rest.
“I’m writing to flag an issue with the [project] timeline. I want to be direct about where we stand and what I think we should do next.”
**2. The body — facts first, frame second**
State the situation as plainly as possible. Then offer your read on it. Then what you need.
Don’t mix the three. Facts → your interpretation → requested action. In that order.
“The design files you sent on Friday have [specific gap]. This matters because [consequence]. I need [specific thing] by [specific time] to keep the project on schedule.”
**3. The close — what you want from them**
End with a clear, specific ask. Don’t leave it open.
“Can you send updated files by Tuesday EOD? Happy to jump on a call if you want to talk through the feedback before then.”
—
## Tone Guide: What to Do and What to Avoid
**Do:**
- Write in short sentences when the message is hard
- Use “I” statements (“I need” not “you failed to”)
- Be specific — vague criticism is harder to receive than specific feedback
- Acknowledge difficulty if it’s a sensitive topic (“I know this isn’t easy to hear”)
**Avoid:**
- Passive voice to obscure responsibility (“Mistakes were made” — who made them?)
- Walls of text for emotionally charged topics
- Sarcasm or irony
- Over-apologizing (“I’m so sorry to bother you but…”)
- Vague language that makes the recipient guess what you mean
—
## Examples by Situation
Pushing back on a deadline:
“I need to flag something on the timeline for the [project] deliverable. The current deadline of Friday doesn’t give enough buffer for review and revisions — if we ship on Friday, we’ll be submitting without adequate QA.
I’d like to propose moving the deadline to Wednesday of next week. I know that affects the downstream timeline, so I wanted to flag it now rather than surprise anyone closer to the date.
Can you let me know if that works, or if there’s a constraint I’m not seeing?”
Telling someone their deliverable needs significant work:
“I reviewed the draft you sent over and I want to give you direct feedback before you spend more time on it.
The structure works well, but there are a few areas where the content needs more specificity to be useful: [specific point 1], [specific point 2], [specific point 3].
Rather than revise the whole thing, I’d suggest we hop on a 20-minute call to walk through the feedback together. Does Tuesday work?”
Escalating a problem upward:
“I want to flag an issue with the [project] that I think needs your attention. [Brief factual description of the problem]. This is affecting [specific impact].
I’ve tried [what you’ve attempted], and the blocker remains. I’m not sure I have the authority to unstick it on my own.
I’d appreciate a conversation about how to move this forward. I can have a clearer picture put together by tomorrow if that would be helpful.”
—
## What to Do Before You Hit Send
Read your email out loud before you send it. If you wouldn’t say those words to someone’s face, reconsider. Email removes tone — so you have to put it in the words themselves.
Count the number of times you say “I” vs “you.” Hard conversation emails tend to go better when the ratio favors “I” statements.
Finally, ask: is email the right medium? If the relationship is already strained, or if the topic is deeply emotional, a 10-minute call is almost always better than a written exchange that can be misread.
—
## The Templates That Help
Deadline pushback emails, feedback delivery templates, escalation emails, and the full Office Email Templates Bundle — ready-to-use scripts for the hard conversations you can’t avoid.