Most business emails are not read; they are skimmed, misinterpreted, and replied to with a question the email already answered. The cause is almost never the information — it's the packaging. A wall of jargon, a buried request, and no deadline produce exactly the slow, confused thread you were trying to avoid.
Here is a short system for emails that get read and acted on. If you want to clean up a draft you've already written, paste it into the Corporate BS Translator first — it strips the jargon so you can see what's actually underneath.
Put the request in the subject line
The subject is the only line guaranteed to be read. "Quick question" tells the reader nothing. "Need your approval on the Q3 budget by Thursday" tells them everything: what you want, from whom, and when. If the reader deletes the rest of the email unopened, the subject alone should have moved things forward.
Bad: Following up
Good: Approval needed: vendor contract, by Fri 5pm
Lead with the ask, not the background
The instinct is to "set context" — three paragraphs of how we got here, then the request at the bottom. By the time the reader reaches it, they've forgotten why they're reading. Flip it.
Open with the one sentence that matters: what you need and by when. Then give the background, in short. Readers who only need the ask can stop after sentence one. Readers who need context keep going. Both win.
One email, one ask
If an email contains three unrelated requests, the reader will do the easiest one and silently drop the other two. This is not laziness; it's how attention works. If you have three asks, send three emails (or three clearly numbered items, each with its own owner and deadline). The cost of three emails is lower than the cost of two forgotten decisions.
Replace jargon with the concrete word
Every piece of jargon forces the reader to translate, and translation is where meaning leaks out. "We need to leverage our synergies to move the needle on the key deliverables" could mean almost anything. "We need to use the design and engineering teams together to ship the dashboard by March" means one thing.
Common swaps:
- leverage → use
- circle back → decide by [date]
- bandwidth → time / priority
- take this offline → "Priya and I will resolve this today"
- the ask → the request (or just state it)
- move the needle → [name the metric]
Give a deadline, or accept "whenever"
"I'd love your thoughts when you have a chance" means "whenever," which in practice means never. If it matters, say when: "Can you review by Wednesday EOD? I'm sending this to the client Thursday." A deadline is not pressure; it's information that lets the other person prioritize honestly. No deadline reads as "this isn't important," and people act accordingly.
Make the next step unambiguous
End with the single action you want, and who owns it. "Let me know if you have concerns, otherwise I'll proceed Friday" is clearer than "thoughts?" The first tells the reader that silence equals assent and names the trigger date. The second asks them to invent the next step.
The 60-second self-edit
Before sending, answer four questions in your own head:
- If the reader reads only the subject, do they know what I want?
- Is the request in the first two sentences?
- Have I named a deadline?
- Is there any word a new hire wouldn't understand? (If yes, swap it.)
If all four pass, send. If you've inherited a draft full of corporate-speak and want the heavy lifting done fast, run it through the Corporate BS Translator — then apply the four checks above to the cleaned-up version.
Clear emails don't take longer to write; they take less, because you stop generating padding. And they save the hour of follow-up clarifications that the padded version always triggers.
Top comments (0)