How to write an email that actually gets answered
Most work emails bury the point. Learn the audience-first move that gets faster replies: lead with the question your reader opened the email asking.
The fastest way to get a reply is to answer the reader's question in the first sentence. Most emails open with context — background, a status recap, what you did last week. The reader has to dig for the point. Flip the order: lead with what they need to know or decide, then give the reasoning underneath.
Why most emails get ignored
People don't read email. They scan it for relevance, decide in a second or two whether it needs them right now, and move on. If your first line is about you — "Hope you're well, wanted to give you a quick update" — there's nothing for them to grab. They file it for later. Later rarely comes.
This is the first principle of communicating well: it's not about you. The reader opened your message with a question in their head, even if they never said it out loud. Your job is to answer that question before they have to look for it.
Lead with their question, not your context
Say you're updating your manager on the week. The question in their head is usually some version of "Is anything on fire, and do you need me?" So answer that first.
"Hi David, hope all is well. Wanted to give you a quick update on where things stand with the team this week. We had sprint planning on Monday and the team is energized about the new roadmap. We also kicked off the vendor review and held a few stakeholder syncs…"
"Hi David — one thing needs you this week: the vendor review is blocked until we get legal sign-off. Can you nudge legal? Everything else is on track — sprint planning went well and the roadmap is moving."
Same information. The second version puts the decision the reader has to make in the first line. The context still exists; it just stops being the headline.
How to do it
- Name the one question your reader has before you write. If you can't name it, you're not ready to send.
- Put the answer in sentence one. The recommendation, the status, the ask — whatever they need most.
- Move the backstory below it. Reasoning supports the point; it doesn't precede it.
- Give any ask its own line. "Can you approve this by Thursday?" should never be hidden mid-paragraph.
- Cut the throat-clearing. "Just wanted to," "I was thinking that maybe," "hope this finds you well" — delete on sight.
A ten-second test
Before you hit send, read only your first sentence. Could the reader act on it without reading the rest? If yes, you've led with the point. If they'd have to scroll to figure out why you wrote, rewrite line one.
Leading with the reader's question is a habit, not a trick — and habits come from reps. That's exactly what audience focus trains in the first week of the Sprint: take a real email you sent, find the question the reader actually had, and rewrite the first sentence to answer it. Do it once and it's a tip. Do it for a week and it's how you write.
How to cut your writing in half without losing the point
An editing method for writing less and meaning more — cut hedging, kill jargon, stop at the period.
Start with the point: the update format that gets read
Put the recommendation first. The structure that makes memos and updates land in one read.
How to ask questions that change the conversation
Listen to understand, not to reply. The probing questions and full pause that deepen any conversation.
Reading about this is the easy part.
Make Your Point turns these principles into 25 short daily exercises. Day 1 is free.
Make your first point — free