The Email That Gets Read — and the One That Doesn't

Sometime around 2014, the reading habits of professional email recipients shifted in a way that most senders have still not adjusted to. The volume of email had grown to the point where the cognitive budget for each message dropped from "read and consider" to "scan for relevance." The subject line got two seconds. The first sentence got one. After that, a decision had already been made: reply, defer, or delete.

Most email is written for a world where readers read. It arrives in a world where readers scan. The result is a constant mismatch between the sender's effort and the reader's engagement — carefully composed messages that are barely glanced at, important questions buried in the third paragraph that are never seen, action requests lost in pleasantries that were meant to build rapport and instead consumed the only attention the message was going to receive.

The discipline of writing email for scanning rather than reading is not a minor adjustment to professional communication. It is a complete inversion of the implicit assumptions most people bring to the task. And it is learnable, quickly, with measurable results.

The Subject Line Is the Article

In journalism, the headline does not describe the story — it is the story, compressed. A reader who sees "Earthquake Strikes Turkey" knows the essential fact. A reader who sees "Update on Recent Events in Europe" knows nothing. Email subject lines fail for exactly the same reason as bad headlines: they describe without informing.

"Meeting follow-up" tells a recipient nothing about whether they need to act. "Action needed: approve Q3 budget by Friday" tells them everything. "Quick question" requires them to open the email to assess urgency. "Quick question about the Henderson proposal — need your answer before 3pm" gives them what they need to triage without opening it.

The most effective subject lines contain: the topic (what this is about), the action or ask if applicable (what you need from them), and the urgency if it is genuinely time-sensitive. Not every email needs all three, but every email needs the first one, and most professional emails benefit significantly from including the second.

The Bottom Line Up Front

Military communication has long used a principle called BLUF — Bottom Line Up Front — which requires that the key conclusion or request appear in the first sentence, before context, rationale, or pleasantries. The principle exists because military communication happens under time pressure and in conditions where a recipient might not finish reading. The principle applies to every email you have ever written.

The instinct in professional writing is to build toward the point — to establish context, provide background, and then, having prepared the reader, deliver the conclusion or request. This is how academic writing works. It is how speeches work. It is how persuasive essays work. It is the wrong structure for email, because email readers will often not reach the conclusion.

The correct structure: state the conclusion or request first. Then provide supporting context for those who need it. Consider this the "inverted pyramid" model from newspaper journalism — the most important information leads, the details follow, and anyone who stops reading part way through has still received the essential message.

In practice this means: "I'm recommending we delay the Henderson launch by two weeks — details below" rather than two paragraphs of context followed by the recommendation. It means "Can you review this proposal by Thursday?" before explaining why you need it reviewed. It means the reader learns what matters within the first five seconds of opening your email, and everything that follows is optional depth.

“If your email ends with the most important sentence, rewrite it to begin there.”— Tom Becker

Specificity Is Kindness

Vague requests impose a hidden cost on their recipients. "Let me know your thoughts" requires the reader to determine what kind of thoughts are wanted, at what level of depth, in what format, by when. "Can you confirm that the numbers in section 3 are current before I send this to the client on Thursday?" requires nothing to be figured out — the task is clear, the scope is defined, the deadline is explicit.

Every degree of ambiguity in a request increases the cognitive load of complying with it and creates an additional decision point where the recipient can decide to defer. Professional emails that go unanswered are frequently not ignored out of negligence — they are deferred because answering them requires more work than is immediately visible, and the recipient's attention moves on to something more tractable.

The cure is mechanical: before sending any email that contains a request, read it and ask whether the recipient could fulfill it immediately if they wanted to, without asking any clarifying questions. If the answer is no — if they would need to know more about scope, format, urgency, or what specifically you are asking them to do — add that information before you hit send.

The Tone Problem

Email strips nonverbal communication — the warmth of a facial expression, the softening of a tone of voice, the physical presence that tells someone you like them even when you're delivering difficult news. What remains is words on a screen, which default in the reader's imagination to a tone that is often more neutral or negative than the sender intended.

Research on email interpretation consistently finds that neutral emails are read as cold, and cold emails are read as hostile. The practical consequence is that the professional who writes in a crisp, unadorned style — perhaps imagining efficiency as a virtue — often creates relationship friction they are unaware of.

The calibration required is not extensive. Opening with a single genuine line of warmth — something specific to the person or situation, not a formulaic pleasantry — restores the human context that email strips away. "I saw your presentation yesterday — the framework in the second half was really useful" takes four seconds to write and changes how the rest of the email is received.

The important caveat: warmth needs to be genuine and specific to work. "Hope you're well" is not warmth — it is a reflexive phrase that signals nothing except habit. Specific acknowledgment of something real signals attention and care in a way that generic pleasantries never do.

Length as a Signal

The appropriate length of a professional email is the minimum required to communicate the necessary information clearly. This is not a preference or a style choice — it is a practical constraint that emerges from the economics of the recipient's attention.

Long emails signal one of several things to a reader: that the sender has not done the work of figuring out what actually matters; that the message contains information relevant to someone else's interests but not necessarily theirs; or that the sender has anxiety about being misunderstood and is hedging against it with volume. None of these signals are ones you want to send.

The discipline of cutting email to its essential content is, at first, uncomfortable. There is a feeling that you are withholding something — context that the reader might need, nuance that might be important, caveats that protect you if something goes wrong. Some of this feeling is legitimate: sometimes the context is necessary. More often, you are projecting your own information needs onto a recipient who has different ones.

A useful heuristic: if your email is longer than what fits on a single phone screen, consider whether it should be shorter or whether the conversation should happen in a different medium — a phone call, a meeting, a shared document with comments. Email is effective for clear, bounded communication. It is a poor medium for complex deliberation, sensitive conversations, or decisions that require back-and-forth exploration.

Using AI Without Losing Your Voice

AI writing tools have become the most visible route to a first email draft for many professionals, and they are useful — particularly for emails where the appropriate tone is difficult to calibrate, where you are avoiding writing something unpleasant, or where you know what you need to say but cannot find the right structure.

The risk is homogenization. AI-drafted emails, sent without editing, tend to share a particular texture: smooth, complete, a little formal, and indistinguishably similar to every other AI-drafted email. Recipients who receive many emails begin to recognize this texture and register it as a signal that the communication is not personal — which affects how it is received.

The effective approach is to use AI for structure and first drafts, then edit to restore your voice and remove any phrase that doesn't sound like you. The test: read the email aloud. Any sentence that you would not say in conversation with this person should be rewritten or removed. The resulting communication is faster to produce than writing from scratch and more human than sending the draft unchanged.