Why shorter tends to work
Long emails are not wrong, but they raise the cost of replying. A reader who sees six paragraphs may decide to come back later, and later often turns into never. Brief emails are easier to start, easier to answer and easier to find again. They also force the writer to clarify what they actually want, which is half the battle.
There is a catch: shorter is not automatically better. A message trimmed so far that it becomes a bare command can feel cold, and a message that leaves out essential context leads to a string of clarifying questions. The aim is not the fewest words; it is the fewest words that still give the reader everything needed to act.
Build the message around one request
The most useful rule is one email, one request. When a message asks three different things, the reader may answer the easiest and forget the rest. If you truly have three unrelated requests, consider three separate emails with separate subject lines, which also makes each one easier to track and file. If they are related, number them.
A quick test: can you state what you want in a single sentence? If not, the email may need more thought, or a conversation may suit the topic better.
Add a clear deadline, and the reason if it helps
A request without a time frame invites delay, because there is no signal for when it matters. Name a date and, when sensible, a time: “by Thursday at noon.” A deadline is more persuasive and less pushy when it comes with a reason: “so I can confirm the booking before prices change.” People are generally more willing to help when they understand why.
Be realistic with deadlines. Asking for a complex review by tomorrow when you sent it at 4 p.m. may produce resentment, not speed. If something is genuinely urgent, say so plainly and consider a phone call or message instead. Otherwise, give people reasonable time.
If there is no real deadline, you can say that too: “No rush; sometime next week is fine.” That helps the reader prioritize and removes unnecessary pressure.
A before-and-after example
Here is a typical rambling email:
Hi Priya, I hope you had a good weekend. I was looking at the schedule for the quarterly review and I noticed there might be some issues with the dates, because a few people are traveling at the start of the month, and I think Marcus mentioned something about a conference too. Anyway, I was wondering whether you could possibly have a look and let me know what you think about maybe moving it?
The same message, shortened:
Hi Priya, could you check whether we can move the quarterly review from March 3 to March 10? Several people are traveling that week, and I need to confirm the room by Wednesday. Thanks!
The second version is about a third as long. It names the request (check whether the review can move), the specific dates, the reason and the deadline. It is still polite because it opens with a greeting and closes with thanks.
Cut the right things
When trimming, remove:
- Filler openings. Lines like “I hope this email finds you well” can be replaced with a plain greeting. A real, short personal note is fine when you know the person.
- Hedging stacks. “I was wondering whether maybe you could possibly” can become “Could you.”
- Backstory the reader already knows. If they were in the meeting, you do not need to retell it.
- Repeated points. Say it once, in the place a reader will see it.
Keep:
- The specific ask and the deadline.
- Any detail the reader needs and could not easily guess: dates, names, amounts, the file they should open.
- A greeting and a thank-you, because they cost a few words and shape how the message is received.
Keep short from sounding curt
Curtness comes from missing warmth, not from missing words. Several small touches keep a brief message friendly:
- Use the person’s name.
- Say “please” or “could you” rather than a bare command.
- Add a one-clause reason for the request.
- End with a thank-you or a short offer such as “Happy to talk it through if easier.”
Basic email etiquette also differs between workplaces, so match the local style. What reads as efficient in one team can feel brusque in another.
Use the subject line and first line as part of the brevity
If the subject line already states the request, such as “Can we move the Q1 review to March 10? Reply by Wednesday,” the body can be two short sentences. Putting the ask in your email subject lines and the first line is one of the strongest ways to keep the rest short.
When a short email is not the right tool
Sensitive topics, complex decisions with trade-offs, and multi-step instructions usually need more words or a different channel. In those cases aim for clear structure rather than minimal length: a one-line summary at the top, numbers for the parts, and the request restated at the end.
Send, then follow up kindly
Even a well-made email may go unanswered. People get busy, and messages slip. If the deadline passes without a reply, a polite nudge a day or so later is normal: “Following up on my note below; could you let me know by tomorrow?” Reply to your original message so the context travels with it. If you often need to nudge, check whether your messages could carry a clearer ask or a more realistic deadline, or whether the person simply prefers another channel.