The average professional receives over 100 emails a day. The ones that get read immediately tend to have two things in common: a clear subject line and a short body. The ones that get deferred tend to be long.
This is not because people are lazy. It is because a long email requires the reader to do work before they can even identify what is being asked of them. When the ask is buried in context, preamble, and qualifications, the reader has to excavate it. Many choose not to.
Writing concisely is not about being terse or cutting substance. It is about removing what does not contribute to the purpose of the email.
Why Emails Get Long
Before the tactics, the diagnosis. Emails get long for a few predictable reasons:
Anxiety about how the message will land When you are worried about how a message will be received, you compensate by adding context, softening language, and hedging claims. The instinct is understandable. The result is an email that takes twice as long to get to the point.
Writing the way you think, not the way you communicate Stream-of-consciousness email captures the process of working something out rather than the result. You arrive at the point eventually, but the reader gets every step of the journey.
Covering all bases Adding every caveat, exception, and qualification is thorough. It is also expensive for the reader, who usually just needed the top-line version.
Not having a clear ask Emails without a defined purpose tend to expand indefinitely. If you are not sure what you need the recipient to do, the email will keep going until something feels like an ending.
The Core Principle: Lead With the Point
The most reliable way to shorten an email is to put the point first. Not the context that leads to the point. Not the background that explains the context. The point itself, in the first sentence.
Before:
Hi [Name], I wanted to follow up on our conversation from last week about the Harrington account. As you may recall, we discussed the timeline for the Q3 deliverables and some of the challenges we have been facing around resourcing. I have been thinking about this and I think there might be a few options worth considering. Would you be available to talk through them this week?
After:
Can we find 20 minutes this week to talk through options on the Harrington timeline?
The before version contains useful context. The after version contains the ask, which is the only thing the recipient needs to respond to. Context can be shared on the call.
Five Specific Cuts to Make
1. Cut the opener
"I hope this email finds you well" and its variants are standard practice and accomplish nothing. The recipient does not need you to wish them well before you get to the point. Cut it entirely.
Same with: "I wanted to reach out to...", "I am writing today to...", "Just a quick note to say..."
None of these are the email. They are announcements that an email is about to start. Start the email instead.
2. Cut the context the recipient already has
If you are replying to a thread, you do not need to re-explain the background. If you are following up on a conversation, you do not need to recap it. Write as if the recipient has the same context you have, because they usually do.
Before:
As we discussed in our meeting on Thursday where we went through the revised project plan and talked about the challenges with the vendor timeline...
After:
Following up on Thursday's meeting — the vendor timeline issue is the one I want to resolve before we proceed.
3. Cut the hedges
Hedging adds length without adding accuracy. "I think it might potentially be worth considering" means "consider this." Qualifiers like "just", "a bit", "kind of", "perhaps", and "if that makes sense" soften the message but do not change it.
Before:
I just wanted to flag that there might be a small issue with the approach we have been taking, and it might be worth looking at whether we should perhaps reconsider.
After:
I want to flag a problem with our current approach and suggest we reconsider it.
The hedged version reads as unsure of its own content. The direct version states the same thing with appropriate confidence.
4. Cut the closing qualifications
"Please let me know if you have any questions" is filler. Of course they can ask questions. You do not need to grant permission. "Do not hesitate to reach out" is the same problem.
Replace with a specific next step or nothing:
- "I will follow up by Thursday." (specific)
- "Let me know by EOD if this works." (specific)
- Just your name. (perfectly fine)
5. Cut the explanation of what you are doing
"I am writing to let you know..." describes the act of writing rather than the information. "I wanted to say..." describes the want rather than the saying. Just say the thing.
Before: "I wanted to take a moment to say thank you for the introduction to Helen Park."
After: "Thank you for the introduction to Helen Park."
One sentence. Same content. Half the words.
Before-and-After Examples
Update email
Before (148 words):
Hi [Name],
I hope you are having a good week. I wanted to send you a quick update on the project we have been working on together. As you know, we have been making progress on the deliverables and I am happy to report that things are coming along well. We did hit a small snag with the vendor timeline but I think we have a plan to work around it. The main deliverable is still on track to be completed by the end of the month. Let me know if you have any questions or if there is anything you need from me. Happy to jump on a call if that would be helpful.
Best, [Name]
After (51 words):
Hi [Name],
Project update: deliverable on track for end of month. One vendor delay to flag — we have a workaround plan and I do not expect it to affect the main timeline.
If you want the details, happy to walk through them on a quick call.
[Name]
Request email
Before (101 words):
Hi [Name],
I hope this finds you well. I was wondering if you might possibly be able to take a look at the attached document when you have a chance. I know you are very busy and I completely understand if this is not a priority right now. I just wanted to get your thoughts before I send it to the client, if that is okay. There is no rush at all, but if you could get back to me by Thursday that would be really helpful. Please let me know if you have any questions.
After (38 words):
Hi [Name],
Could you review the attached before I send it to the client? I need feedback by Thursday. Happy to discuss anything that needs work.
[Name]
Difficult message
Before (long, anxious):
Hi [Name],
I hope you are doing well. I have been meaning to reach out for a while but have not had a chance to do so until now. I wanted to discuss something that has been on my mind and I hope you take this in the spirit in which it is intended. This is a bit of a sensitive topic and I want to be careful about how I raise it, but I think it is important that we talk about it. I have been noticing some challenges with the way things have been going with [project] and I wanted to flag it before it becomes a bigger problem...
After:
Hi [Name],
I want to raise something directly. The [project] situation has been concerning me and I think we need to talk through it before it becomes harder to fix.
Are you available Thursday or Friday for a call?
The longer version signals that the sender is uncomfortable. The short version signals that they are confident and dealing with the issue directly. In most cases, the latter lands better.
When Short Is Wrong
Concise does not always mean short. There are emails that require length: complex instructions, sensitive situations that need careful framing, proposals that must make a complete case. The discipline is not "shorter is always better." It is "every sentence should earn its place."
An email that is 400 words because it needs 400 words is fine. An email that is 400 words because the writer did not edit it is not. The test is whether removing a sentence changes what the reader understands or does. If it does not, cut it.
The Relationship Between Conciseness and Voice
There is a version of "concise email" advice that produces terse, impersonal messages that feel abrupt even when technically efficient. That is not the goal. The goal is to remove the noise that obscures the signal, not to strip out personality.
Emails that sound like you are usually the right length. They have the warmth or directness or humor that the relationship calls for. What they do not have is filler, hedging, or repetition. Learning to cut those without cutting your voice is the actual skill.
The challenge is that most people's editing instincts work against conciseness. When something feels important, the instinct is to add words. When something feels risky, the instinct is to soften. These instincts produce exactly the kind of length that makes email harder to read and act on.
A drafting system that has internalized how you actually communicate — your natural register, your level of directness, your relationship-specific tone — will tend to produce shorter output than a generic model applying standard professional voice. The generic version adds hedging because it does not know you. The trained version does not need to.
Generate a persona prompt built from how you actually write →