Every workplace runs on written messages, and yet almost nobody is ever taught how to write them. The result sits in your inbox right now: rambling emails that bury the question in paragraph four, subject lines that say “Quick question,” reply-all threads that spiral for days, and requests that die quietly because nobody could tell who was supposed to act. Learning to write clear, answerable messages is one of the highest-leverage professional skills there is — it makes projects move faster, makes you easier to work with, and quietly builds your reputation with every send. The techniques are not complicated. They mostly amount to doing the reader's work for them before you hit send.

Write the Subject Line Like a Headline

The subject line is not a label; it is a decision-making tool. Busy people use it to triage — open now, open later, or ignore — so it should carry the message's purpose and urgency on its own. “Quick question” and “Follow-up” force the reader to open the message just to find out whether it matters. Compare that with “Approval needed by Friday: vendor contract” or “FYI only: notes from the planning meeting.” One glance tells the reader what it is, what is expected, and when.

A useful habit is to start subjects with a category word: Action needed, Decision, Question, FYI, Heads-up. It feels mechanical at first, but recipients quickly learn that your messages sort themselves, and messages that sort themselves get answered first. If the thread's topic drifts, change the subject line to match — replying about budget under a subject about scheduling is how information gets lost forever.

Put the Ask in the First Two Sentences

The single biggest email mistake is structuring the message like a mystery novel: background first, context second, request at the very end. Readers skim, and skimmers who do not find a point in the first few lines defer the message “for later,” which often means never. Invert the structure. State the request or the key information first, then provide supporting context below for whoever needs it. “Could you approve the attached budget by Thursday? Details below” respects the reader's time and dramatically raises the odds of a same-day answer.

If you find yourself unable to write the first sentence, that is diagnostic: you are not yet sure what you are asking for. Decide before you write. An email without a clear purpose produces a reply without a clear answer, if it produces one at all.

Format for Skimming, Not for Reading

Nobody reads work email the way they read a book; they scan it in a few seconds looking for what concerns them. Dense paragraphs defeat scanning, so shape the message visually:

  • Keep paragraphs to three lines or fewer. A wall of text signals effort and gets postponed.
  • Use lists for anything with more than two items. Steps, options, and questions all read better as bullets.
  • Bold the key line. One bolded deadline or decision point guides the skimming eye; ten bolded phrases guide it nowhere.
  • One topic per message. Two unrelated requests in one email means the easier one gets answered and the harder one evaporates.
  • Name the owner. If three people receive a request, address the action to one of them by name. Requests addressed to everyone belong to no one.

Before sending anything longer than a few paragraphs, scan it yourself as if you had ten seconds. If the ask, the deadline, and the owner do not jump out, revise until they do.

Get the Tone Right Without Overthinking It

Written words arrive stripped of facial expression and vocal warmth, which means neutral sentences can read as cold and brisk ones as hostile. You do not need emoji or exclamation points to fix this — you need a line of human acknowledgment and careful phrasing of requests. Opening with a brief “Thanks for turning this around so quickly” or “I know this week is packed” costs five seconds and changes how everything after it lands. Phrase requests as requests, not verdicts: “Could you take a look at the numbers in section two?” reads very differently from “The numbers in section two are wrong.”

Above all, never send frustration. Email freezes your worst moment and forwards it indefinitely. If a message makes you angry, draft your reply if you must — with the recipient field empty — and revisit it after an hour or a walk. Nearly every veteran of office life has one story about the heated reply they wish they could unsend, and none about the measured one they regret. A useful test for anything sensitive: imagine it read aloud in a meeting with everyone mentioned present. If that makes you wince, rewrite it or pick up the phone.

Know When Not to Send an Email at All

Part of writing good email is recognizing what email is bad at. It is excellent for requests with clear owners, status updates, confirmations, and anything that benefits from a written record. It is terrible for disagreement, ambiguity, and emotion. If a thread has gone three rounds without converging, if you are explaining the same point a second time, or if the topic involves criticism, conflict, or bad news, stop typing and talk — a five-minute call resolves what fifteen messages inflame. Afterward, send a short summary email so the record still exists: “Thanks for the call — confirming we agreed to X by Friday.”

Similarly, respect the difference between channels. Instant messages suit quick, low-stakes questions; email suits anything someone may need to find next month; documents suit anything long-lived. Sending the right message in the wrong channel is how decisions get lost.

Follow Up Without Being a Pest

Unanswered email is usually not rejection — it is burial. People mean to reply, get interrupted, and your message slides below the fold. A polite follow-up after two or three business days is not nagging; it is a service. Keep it short, keep it friendly, and crucially, make replying even easier than the original message did: restate the ask in one line, offer a default (“If I don't hear back by Thursday I'll proceed with option A”), or convert an open question into a yes/no. Defaults are especially powerful, because silence becomes agreement instead of a dead end.

When you are the one who owes answers, adopt the two-minute rule: if a reply takes under two minutes, send it immediately rather than letting it queue. For everything else, a brief holding reply — “Got it, I'll have an answer Thursday” — keeps trust intact while you do the real work. People forgive slow answers; they remember silence. Over time, a reputation for reliable responses becomes its own advantage: colleagues route important work toward the person whose inbox is not a black hole, and that routing is how opportunities quietly accumulate.

Final Thoughts

Good workplace writing is not about eloquence. It is about transferring a request or a piece of information into another busy person's head with the least possible friction — a subject line that triages itself, an ask in the first breath, formatting that welcomes a skim, a tone that assumes goodwill, and a follow-up system that keeps things from dying in silence. Pick your next real email and apply just two of these moves: rewrite the subject as a headline and move the ask to the top. The reply will probably come back faster, and that small proof is how a lasting habit — and a reputation for clarity — begins.