How to Write a Difficult Professional Email

DIRECT PROFESSIONAL EMAILS: A PRACTICAL GUIDE CORE PRINCIPLE Directness is about clarity, not cruelty. The goal is to make the message impossible to misread while keeping it professional. You state the decision, the reason, and the consequence in as few words as possible. Hostility creeps in when you add judgment ("you clearly didn't read this"), sarcasm, or emotional language. Evasiveness creeps in when you bury the point in hedging and apology. REUSABLE STRUCTURE (the SBI-D pattern) 1. Subject line that states the outcome, not the topic. Weak: "Regarding the project" Strong: "We are not extending the contract" 2. One-sentence context. Restate the situation briefly so there's no confusion about what you're responding to. 3. The decision or position, stated plainly. This is the core sentence. Write it so it survives being quoted out of context. 4. The reason, in one or two sentences. Reasons prevent the message from reading as arbitrary. 5. The consequence or next step, with a concrete action and deadline. This closes the loop and shows you're managing the situation, not venting. 6. A short, non-apologetic close. Offer a path forward or a point of contact. No "sorry for the inconvenience" if you're not actually sorry. Keep the whole thing under six sentences when possible. Every extra sentence is a place to get tangled. THREE EXAMPLES 1. DECLINING A REQUEST (saying no) Subject: Cannot take on the migration this quarter Hi Dana, You asked whether we can move the data migration to Q3. We cannot. Our team is fully committed to the compliance audit through September, and taking on the migration would put both deadlines at risk. I can revisit this in October, or connect you with two vendors who handle migrations if you need it sooner. Let me know which you prefer. Why it works: the decision is in the first line, the reason is a fact not a complaint, and it offers alternatives so it doesn't end in a dead end. 2. PUSHING BACK ON AN UNREALISTIC DEADLINE Subject: Delivery date for the reporting module is not feasible Hi Marcus, I've reviewed the request to deliver the reporting module by Friday. That date is not feasible. The module depends on the data pipeline, which isn't finished until next Tuesday, and we have no way to compress that dependency. The earliest realistic date is Thursday of next week. If the Friday date is firm on your end, I need you to tell me which of the current scope items I should drop to make it possible. Why it works: it names the dependency (so the pushback is grounded in fact, not attitude), gives a concrete alternative, and forces the other person to make the tradeoff decision instead of you absorbing it silently. 3. GIVING NEGATIVE FEEDBACK / ENDING A RELATIONSHIP (vendor) Subject: Ending the retainer, effective end of month Hi Priya, I'm writing to confirm that we will not renew the retainer when it ends on August 31. Over the past six months we've had three missed delivery dates and two incidents where incorrect data reached our clients, and we've lost confidence in the arrangement. Please send a final invoice and a handover of all open files by August 28. I'm happy to brief your replacement if you recommend one. Why it works: it documents the factual basis (specific incidents, not vague dissatisfaction), sets a concrete cutoff, and stays cooperative about the transition. COMMON PHRASES THAT WEAKEN YOUR MESSAGE Hedging that invites negotiation - "I was wondering if maybe we could..." (you're not wondering; you're deciding) - "It might be better if..." (it is better, or it isn't) - "Just checking in to see if..." (you're not checking in; you're making a demand) Apology stacking - "I'm sorry, but I hate to ask, and I apologize for the trouble..." (three apologies before the request reads as fear, not politeness) - "Sorry to bother you, but..." (if it's a legitimate ask, don't apologize for it) Vague escalation - "We need to discuss this further." (discuss what? with whom? by when?) - "I'm not sure this is working out." (either it isn't, or it is — say which) - "There have been some concerns raised..." (by whom? about what? this invites the reader to guess and deflect) Passive voice that hides the actor - "Mistakes were made." (by whom? if you won't own it, the reader will assume the worst) - "It was decided that..." (by whom? this reads as evasive) Emotional leakage - "I'm extremely frustrated that..." (your feelings are not a reason; state the fact instead) - "As I already said..." (this is a fight-starter; restate the point once, cleanly, and stop) Jargon that pads - "Going forward, we need to circle back and touch base on the ask." (say: "We need a decision on X by Friday") THE RULE OF THUMB Before sending, delete every sentence that doesn't do one of these three jobs: state the decision, give the reason, or specify the next step. Whatever remains is direct. If a sentence is only there to soften the blow or protect your ego, cut it. Directness reads as confidence; softening reads as either evasion or hostility in disguise.