Comparison
Five workplace email rewrites — before, after, why
May 9, 2026 · 3 min read
Five common workplace email scenarios, each with the version most people send, the version that works, and why the difference matters. Sketches, not templates — for the worked-out versions of each, see the parent post.
Disagreeing with your boss
Situation: You see a problem with your manager’s plan.
Most people send: Vague worry (“I’m a little concerned about the timeline”) or flat critique (“This won’t work”).
Why it misfires: Vague worry is easy to dismiss; flat critique reads as undermining.
Better: Lead with the shared goal. Raise the concern as a question. Cite specific precedent. Close with what you both want.
Why it works: Frames the disagreement as defense of a shared outcome, not personal opposition.
Related: How to disagree with your boss in an email.
Flagging an unbalanced peer load
Situation: A peer has been quietly offloading work onto you.
Most people send: Either nothing (you absorb it) or a frustrated all-at-once email naming the problem in vague terms.
Why it misfires: Saying nothing is unsustainable; vague framing reads as an attack on the peer rather than a solvable distribution problem.
Better: Be specific (X tasks over Y weeks). Name the impact. Reference the original arrangement if there was one. Propose a concrete next step (re-divide the task list together).
Why it works: It’s a logistics conversation, not a character indictment. Specificity is hard to argue with; the proposal turns the email into something actionable.
Responding to a passive-aggressive email
Situation: A coworker writes “per my last email” or some other coded jab.
Most people send: A counter-jab dressed as professionalism (“happy to discuss expectations going forward”).
Why it misfires: Matching the tone perpetuates the cycle; both parties leave with the dynamic intact.
Better: Be direct where they were oblique. Own any legitimate part of the miss. Skip the meta-debate about tone. Close with what they actually wanted.
Why it works: Both sides need a participant for the dynamic to continue. Without a counter-jab to feed it, the loop loses its energy.
Related: How to respond to a passive-aggressive email at work.
Saying no to more work
Situation: You’re being asked to take on something on top of an already-full plate.
Most people send: A reluctant yes (“sure, I’ll make it work”) or a defensive no (“I’m slammed, I can’t”).
Why it misfires: The reluctant yes promises something you can’t deliver; the defensive no reads as resistance without context.
Better: Yes contingent on a tradeoff. List your current load with deadlines. Hand the prioritization decision back to your manager.
Why it works: Reframes the conversation as a resource calculation, not a willingness check. The list shifts the cost from invisible to visible, and putting the priority decision back where it belongs is what your manager is paid to do.
Related: How to say no to more work without burning bridges.
Addressing being talked over in meetings
Situation: Your input keeps getting cut off when meetings move fast.
Most people send: A vague frustration email after the fact (“I’d appreciate it if you could let me finish”).
Why it misfires: Vague enough to be denied (“I don’t think I do that”). Emotionally loaded enough to make the listener defensive.
Better: Cite a specific instance. Don’t name the pattern as the focus — let the specific instance demonstrate it. Propose a structural fix (a round-the-table check before agenda close), not a behavioral one.
Why it works: Specifics are hard to deny. A structural change works whether or not anyone remembers their good intentions.
The pattern across all five: emails that misfire tend to leave the substance vague while the emotional charge stays loud. Emails that work flip that — they make the substance specific and let the emotion stay implicit.
For the full worked-out version of each scenario, see the parent post: The Email You Should Have Sent.
From the essay: Read the full piece →
Want more like this? Subscribe to the newsletter.