Register · SCOAI
How to not sound condescending in an email
Most advice for sounding less condescending points at adjectives: swap 'obviously' for something gentler, add an exclamation point, soften the verb. None of that touches the actual cause. Condescension shows up at the exact point where you restate information the reader already has, and no synonym fixes a sentence that shouldn't exist. Three spots in an email carry almost all of it. The first is the recap of what they already said. The second is the definition of a term they used correctly. The third is the word 'just' sitting in front of an instruction, quietly implying the step should have been obvious. Find those three and cut them, and most of the tone problem goes with them.
Most condescension in an email traces back to three specific moments: recapping what the reader already told you, defining a term they used correctly, or prefacing an instruction with 'just,' as if it needed saying. underslop's Explainer voice (SCOAI) finds and cuts those three moments, so the email reads clearer, not colder.
The voice that does this: The Explainer
Condescension is explaining badly, and SCOAI is the shipped voice built for explaining well. It stays quick to include and allergic to cruelty, and it edits toward clarity without losing warmth, the balance a condescending email never finds.
Outgoing, organized, agreeable, and creative all sit at 75; intense drops to 25, so the brightness stays level instead of curdling into performance. Read the full The Explainer profile
What changes in the writing
The recap sentence goes first, the one that opens with 'as you mentioned' or 'to recap what you said,' because it exists to prove you read the email rather than to move the conversation forward. Any definition of a term the reader used correctly and unprompted comes out next; if they wrote 'the API,' you do not get to explain what an API is. 'Just' and 'simply' drop from in front of instructions, since both words tell the reader a step should feel trivial to them specifically. The email that remains runs shorter, because every sentence left in it adds something the reader did not already have. Questions get asked only when you are genuinely unsure, not to test the reader. The close assumes competence instead of confirming it.
What this register cuts
- just
- simply
- to clarify
- as you mentioned
- I'm sure you're aware
- obviously
Before and after
The same message twice. On the left, the register the reader is trying to get away from. On the right, the real output of running it through The Explainer.
Just to recap, you mentioned the export was failing on the second dataset, which as you probably know means the schema didn't match. To clarify, an API in this context is just the interface the two systems use to talk to each other. Anyway, simply re-run the job with the corrected file and it should just work. Hope that clears it up!
Just to recap what we talked about: the export kept failing on the second dataset, and you probably already know that means the schema didn't match. An API here is just the interface the two systems use to talk to each other — nothing more mysterious than that. So go ahead and re-run the job with the corrected file, and it should work fine. That clear things up?
How to do it by hand
- Circle every recap Find sentences that restate what the reader already told you, openers like 'as you mentioned' or 'to recap.' If it adds nothing new, cut it.
- Cut definitions they didn't ask for If the reader used a term correctly and unprompted, do not define it back to them. Assume the vocabulary they used is the vocabulary they own.
- Delete 'just' and 'simply' before instructions Both words frame the next step as obvious. Read the sentence without them; the instruction still works, and the implication about the reader's competence disappears.
- Read it as someone who already knows the background Reread the email pretending you are the recipient with full context. Anything that still explains something you already know is the condescension.
Questions
How to not sound rude in an email?
Rudeness and condescension read differently: rude cuts something out, condescending puts something in that the reader did not need. Check for restated context and unnecessary definitions before you touch word choice.
How to not sound condescending?
Look for the three repeat offenders: recapping what the other person told you, defining a term they used correctly, and 'just' in front of an instruction. Cut those three and most of the tone problem goes with them.
How to handle a condescending email?
Answer the actual content and skip the parts that talked down to you. Responding to the tone usually escalates it; responding only to the substance tends to end it.
How to not be condescending at work?
The habit usually comes from over-preparing an explanation before you know what the other person already knows. Ask first, then explain only the gap, not the whole topic.
How to say rude tone professionally?
If you mean flagging that a message read as condescending, name the specific line rather than the general feeling. 'The part where you explained X felt like you assumed I didn't know it' lands easier than 'your tone was rude.'
Voiced editing is in beta and can drift from your facts, so it flags anything it tried to add. The free tier caps at 500 words a run, and your text is held for 0 seconds.