4.6/5 - (34 votes)

You’ve probably sent an email like this one: “I wanted to reach out regarding the project we discussed and see if there might be some updates or thoughts you’d like to share.” Three days later, still no reply.

The problem usually isn’t grammar. It’s that the email is missing one of four things a reader needs before they’ll actually act on it.

A clear reason, in the first sentence

Before you think about wording, ask what you want the reader to do after reading this. That’s the purpose, and it has to show up in sentence one, not somewhere in paragraph three.

Compare the two: “I wanted to reach out regarding the project we discussed” tells the reader nothing. “Can you confirm the budget by Friday?” tells them exactly why the email exists, in five words.

One main point, not three wrapped in context

An effective work email leads with the point, then supports it. A weak one does the opposite: paragraphs of background first, the actual ask somewhere near the sign-off.

If your request could get lost between two paragraphs of context, move it to the top. Save the backstory for after, and use short paragraphs or a short list so the message is easy to scan on a phone.

Just enough detail, and not more

A reader needs enough information to act, not everything you know about the situation. Sending a busy manager the same level of technical detail you’d send a teammate on the same project usually backfires. It slows down the exact person you need a reply from.

See also  The 4-part ending every persuasive email is missing

Ask who’s actually reading this and what they need in order to decide, then cut anything that doesn’t serve that. A vendor name, a dollar figure, and a deadline are usually enough for someone approving a budget. The full history of how you got there belongs in a call, not the email.

A specific action, not a vague hope

“See if there might be some updates or thoughts you’d like to share” isn’t a request, it’s a hope. Nobody feels obligated to reply to a hope, so it sits in the inbox until it’s forgotten.

“Can you confirm the budget by Friday? I need it to finalize the vendor contract” is a request: a deadline, a reason, and a clear answer to give. The reader doesn’t have to guess what “confirm” even means or by when.

The same email, before and after

Weak version: “Hi, I wanted to reach out regarding the vendor project we discussed last week. There have been a few developments and I thought you might want to weigh in when you get a chance. Let me know your thoughts.”

Rewritten version: “Hi, I need your approval on the vendor budget by Friday to keep the project on schedule. The number is $4,200, up from the original quote because of the shipping change we discussed. Can you confirm by end of day Thursday?”

Same situation, same sender. The second one gets a reply the same day, because it does all four things at once: a clear reason, one point, just enough detail, and a specific action.

The one-sentence check before you hit send

Before sending, reread your own email and ask one question: if the reader only had time for the first sentence, would they know what to do? If the answer is no, move your actual ask to the top and try again.

See also  Friendly is not the opposite of professional in a work email