Email is one of those skills that nobody teaches you formally, yet it's something you do dozens of times a day. A poorly written email wastes time, creates confusion, and can damage relationships. A well-written one does the opposite.
Here's what I've learned after years of collaborating across teams, timezones, and cultures.
Lead with the ask
The biggest mistake people make is burying the point. Your reader shouldn't have to scroll through three paragraphs of context before understanding what you need. State the purpose in the first sentence.
Instead of: "Hi, hope you're well! I wanted to follow up on our conversation last week about the deployment timeline and was wondering if you had a chance to check with the infrastructure team..."
Try: "Can you confirm the deployment date by Thursday? Background below."
One email, one ask
If you need three things, send three emails — or use a numbered list with clear ownership. Combining multiple requests in one email almost guarantees that only one of them gets addressed.
Subject lines are headlines
Your subject line determines whether the email gets opened and how quickly. Be specific. "Question" is terrible. "Decision needed: API versioning approach by Friday" is good.
Context is a gift, not a burden
Include just enough background so the reader can act without having to ask follow-up questions. But trim anything that isn't necessary for them to do what you're asking. Respect their time.
Read it out loud before sending
If it sounds weird when you say it, it'll read weird too. This catches tone issues, run-on sentences, and missing context faster than re-reading silently.
Good email isn't about being formal — it's about being clear, respectful of the reader's time, and easy to act on.
Continue reading