How to Handle Difficult Conversations Over Email
That email you've been avoiding for 3 days is still sitting there. The confrontation, the price increase, the scope pushback: they don't go away. They just get harder the longer you wait. Here's a framework for writing difficult emails that are direct, professional, and take 10 minutes instead of 3 days.
The Emails You're Probably Avoiding Right Now
The Confrontation
"Hey, I noticed the deliverable was different from what we agreed on." — 3 — You rewrote the message 7 times, each version getting longer and more defensive. Finally sent a version so diplomatic it didn't actually say anything.
The Bad News
"I need to push the timeline back by two weeks." — 5 — You waited until the last possible moment, which made the delay feel like a surprise instead of proactive communication.
The Price Increase
"Starting next quarter, my rate will be $275/hr." — 8 — You drafted it in Notes, never sent it, and worked 3 more months at the old rate, costing yourself $4,500.
The Scope Pushback
"That's outside our current agreement. Happy to scope it separately." — 2 — Instead of saying no, you did the extra work for free. Again. The client now expects it.
The Difficult Feedback
"The design direction isn't working. Here's what I'd recommend instead." — 4 — You softened the feedback so much the client didn't realize you were saying "start over." Two more rounds of revisions followed.
5 Avoidance Patterns That Make It Worse
The Over-Explainer
You write 8 paragraphs of context before getting to the point. The recipient has to decode your actual message from a wall of justification. — Your message gets skimmed and the key point gets missed
The Endless Drafter
You write, delete, rewrite, soften, strengthen, soften again. The email takes 45 minutes and reads like a committee wrote it. — 45 minutes of productive time, plus the mental weight of having it "in progress"
The Delay-Until-Urgent
You wait until the situation gets worse, then send a frantic email that creates more drama than the original issue. — A small problem becomes a big one. You look reactive instead of proactive.
The Channel Switcher
"I'll just bring it up on our next call." But you don't. Or you do, and it comes out poorly because you didn't prepare. — The conversation either never happens or happens worse than email would have been
The Passive Approach
You hint at the issue without stating it directly. "Just wanted to check in on the timeline..." when you mean "You're a week late." — Nothing changes because the other person doesn't know there's a problem
The 4-Part Framework for Any Difficult Email
The Direct Open (1 sentence)
State the topic in the first sentence. No warm-up, no "Hope you're well." The recipient should know exactly what this email is about in 5 seconds. — [object Object],[object Object]
The Facts (2-4 sentences)
State what happened, what changed, or what you observed. No opinions yet. Just facts. This creates shared reality before you introduce your perspective. — [object Object],[object Object]
Your Position (1-2 sentences)
State what you think, recommend, or need. Use "I" statements. Be direct without being aggressive. The word "because" is your friend: it connects your position to the facts. — [object Object],[object Object]
The Clean Close (1 sentence)
End with a specific next step and timeline. Don't leave it open-ended. The recipient should know exactly what you need from them and by when. — [object Object],[object Object]
5 Templates for the Hardest Emails
Pushing Back a Timeline
[Name]: The [project] timeline needs to shift. Here's why and my plan. [Fact]: We discovered [specific issue] during [phase], which adds approximately [X hours/days] to the [specific part]. [Position]: I'm recommending we move the delivery date to [new date]. This gives us time to [benefit] without rushing [important thing]. [Close]: I've already adjusted [what you've done]. Can you confirm the new timeline works by [date]? — Lead with the plan, not just the problem. Show you've already started solving it.
Raising Your Rate
[Name]: I want to give you advance notice: starting [date], my rate will be [new rate]/hr (currently [old rate]). [Fact]: This reflects [reason, e.g. market rates, expanded capabilities, demand]. I've kept the rate stable for [period] and this adjustment brings it in line with [benchmark]. [Position]: For our current engagement, I'd like to honor the existing rate through [end of current scope/date], then transition to the new rate for future work. [Close]: No action needed now. Just wanted you to have this information early. Happy to discuss if you have questions. — Give notice, not permission. You're informing, not asking.
Addressing Scope Creep
[Name]: Quick flag on scope. The [additional items] you mentioned are outside our current agreement. [Fact]: Our SOW covers [what's included]. The [new requests] would add approximately [X hours] of work. [Position]: Happy to take these on. I can either add them to the current project at [rate] or scope them as a separate phase. [Close]: Which approach works best? I can send a quick addendum by [date] either way. — Frame it as helpful, not adversarial. You're clarifying, not complaining.
Giving Honest Feedback
[Name]: I reviewed the [deliverable] and have some direct feedback. [Fact]: The current version [specific observation, e.g. "doesn't address the user's main objection" or "buries the key message in paragraph 4"]. [Position]: I'd recommend [specific change] because [reason tied to their goal]. This would [expected improvement]. [Close]: Want me to take a pass at revising, or would you prefer to adjust based on these notes? Either way, I can turn around feedback by [date]. — Connect your feedback to their goals. "This won't hit your conversion target" > "I don't like this."
Following Up After Being Ignored
[Name]: Following up on my [date] email about [topic]. I know things get buried. [Fact]: I need [specific thing] by [date] to keep [project] on track. Without it, [consequence, e.g. "the next phase will be delayed by approximately a week"]. [Close]: Can you get me [what you need] by [realistic date]? If [date] doesn't work, let me know what does and I'll adjust the timeline. — Name the consequence without making it a threat. You're being professional, not passive-aggressive.
The 60-Second Pre-Writing Checklist
What's the one thing I need the recipient to know or do?
This becomes your first sentence.
What are the facts? (Not feelings, not interpretations. Facts.)
This becomes your second paragraph.
What do I recommend or need?
This becomes your position statement.
What's the specific next step and deadline?
This becomes your closing line.
Am I over-explaining? (If it's more than 8 sentences, cut it in half.)
Shorter emails get read. Longer emails get skimmed or postponed.
Stop drafting. Start sending.
alfred_ gives you AI-drafted starting points for every email, including the ones you
Try alfred_ FreeFrequently Asked Questions
How do I handle a difficult email when I'm angry?
Don't send it while you're angry. Write a draft, save it, and come back in 2-4 hours (or the next morning for anything emotionally charged). When you return, you'll cut 60% of the defensive language and the email will be twice as effective. The pre-writing checklist above works especially well here because it forces you to separate facts from feelings before you start composing.
What if the person responds badly to my direct email?
Direct communication occasionally creates short-term discomfort, but it almost always creates better long-term relationships. If someone responds negatively to a factual, professional email, that tells you something about the relationship, not about your communication style. Most people actually prefer directness because it respects their time and treats them like an adult.
Should I deliver bad news over email or schedule a call?
Email first, call second, in most cases. An email gives the recipient time to process before responding. A surprise call puts them on the spot. The exception: if the news is deeply personal, affects someone's employment, or could be easily misinterpreted, start with "I'd like to discuss [topic]. Can we find 15 minutes today?" Then follow up the call with an email summarizing what was agreed.
How do I push back on a client without damaging the relationship?
Frame pushback around their goals, not your preferences. Instead of "I don't think we should do this," try "I don't think this approach will get you [their stated goal]. Here's what I'd recommend instead." When your pushback is clearly in service of their success, it builds trust rather than damaging it. The key is leading with facts, not opinions.
My emails keep getting too long. How do I shorten them?
Write the email, then delete the first paragraph. In 80% of cases, the second paragraph is where the actual message starts. The first paragraph is usually throat-clearing: context the recipient already has. Then apply the 8-sentence rule: if it's longer than 8 sentences, you're over-explaining. Cut every sentence that doesn't advance the message. If you need to share detailed information, put it in an attachment or linked document.
How do I follow up without seeming pushy or passive-aggressive?
Name what you need and why, with a deadline. "Following up: I need [X] by [date] to keep [project] on track" is professional, not pushy. What's actually passive-aggressive is hinting: "Just checking in..." or "Per my last email..." Be direct about what you need and give them a realistic deadline. If they still don't respond, escalate by naming the consequence: "Without [X] by Friday, I'll need to [pause the project / adjust the timeline]."