This is not about grammar. It is about speed, clarity, and judgment.
We write emails so the reader can understand the point in seconds, decide quickly, and forward the message without extra explanation.
1. Start with the point
The first sentence should say the ask, decision, risk, or update.
Do not warm up. Do not build suspense. Do not tell a story.
2. Put bad news first
If something is wrong, say it early.
Do not hide the problem behind context or politeness.
3. Use as few words as possible
Every sentence should earn its place.
Delete filler, repetition, and softening language.
4. Be literal
Say exactly what you mean.
Do not use sarcasm, hints, irony, or coded language.
Do not make the reader guess.
5. Be specific
Use names, numbers, dates, and facts.
Bad: There were some delays.
Good: Vendor X missed the March 12 deadline. Launch now moves to March 19 unless we reduce scope.
6. One email should do one job
An email should mainly do one thing: ask, decide, update, escalate, or confirm.
If you have three unrelated topics, send three emails.
7. Make the next step obvious
Say who needs to do what by when.
If you want a decision, say the deadline.
If you want feedback, say what kind of feedback.
8. Separate facts, judgment, and recommendation
Facts are what happened.
Judgment is what you think it means.
Recommendation is what you think we should do.
Keep those distinct.
If something is uncertain, say that clearly. Do not present a guess as a fact.
9. Write for forwarding
The email should still make sense if someone forwards it to another person with no extra context.
That means the topic, names, dates, and decision should all be clear inside the email itself.
10. AI is fine. Generic language is not.
It is fine to use AI to draft or review an email.
But edit it until it sounds specific and human.
If a sentence could be pasted into any company, it is too generic.
Avoid phrases like: I hope this email finds you well I wanted to reach out Please be informed Kindly Just circling back Revert to me
Use normal words instead.
11. Respect time
Aim for an email that can be read on one screen.
If it must be longer, put the punchline first and then add short sections underneath.
12. Do not save face at the expense of clarity
Be respectful, but do not hide the truth.
Direct is better than vague.
Clear is better than polite but useless.
13. Keep threads clean
Reply on the same thread only if the topic is still the same.
If the topic changes, start a new email with a new subject line.
CC only people who need to act or know.
14. Subject lines help triage
The subject line should help the reader triage the email fast.
Good: Action needed today: approve revised offer Decision needed: pricing for Client X Update: contract signed with Acme Risk: launch delayed by one week
Weak: Quick question Following up Hi Update
15. Default structure
Subject: [Action, Decision, Update, Risk]: [topic]
[First sentence: the ask or punchline.]
[Two to five lines of facts, with names, numbers, and dates.]
[Recommendation or next step.]
[Owner and deadline.]
16. Examples
Weak:
Hi John, hope you are well. I wanted to reach out regarding the vendor situation. As you know, we have been discussing timelines internally and there have been a few complications on their side, so I thought I would share some context before getting your thoughts. Please let me know what you think.
Better:
Subject: Decision needed: vendor delay on onboarding
Vendor X missed the March 12 deadline. If we keep the current scope, onboarding moves to March 19.
My recommendation is to remove feature Y and keep the March 15 launch.
Please reply by 3 pm today so we can confirm with the client.
Weak:
Just wanted to flag that there may possibly be some issues with the campaign performance and we may need to revisit the targeting.
Better:
Subject: Risk: campaign under target this week
The campaign is 18 percent below target after four days.
Likely cause is narrow audience targeting.
Recommendation: expand targeting today and review performance again tomorrow at 2 pm.
17. When not to use email
Do not use email for long back and forth, unresolved debate, or high emotion.
Use a call or chat when speed matters more than record keeping.
Then send a short email summary with the decision.
18. Final rule
A good email does not try to sound smart, warm, or impressive.
It makes the reader understand the point fast.
Instagram Engineering
Shopify Engineering