Key Takeaways — Chapter 19: Emails That Get Read and Get Results

The summary card. Read this to re-ground before the next chapter or before you write a hard email.

The one idea

An email is a tool for getting one specific action from one specific reader — not a record of everything you know. The novice writes to discharge their knowledge (the "info-dump"); the effective writer asks "what do I need this person to do, and what's the least I can give them so they'll do it?" — writes the ask first, and prunes the rest. Every technique below follows from this shift.

🚪 Threshold concept: Stop asking "what do I know about this?" Start asking "what one action do I need, and how do I make it unmissable and easy?" More information is not more communication.

Why email matters most

You write hundreds of emails for every report, so skill here compounds (frequency); email is saved, searchable, forwardable, and discoverable (permanence — never send what you'd regret being read aloud); and colleagues judge your competence by the writing they actually read, which is your email (reputation).

The four-part anatomy

Part Its job
Subject line Win triage — state the topic and the action/deadline; the only guaranteed-read part.
Opening (first sentence) State your purpose. Warmth rides alongside, never in front.
Body Only what the reader needs to act; scannable; passes the "so what?" test.
Close (the ask) One clear action + a deadline. No doubt what happens next.

This is Chapter 4's inverted pyramid and Chapter 3's "so what?" test, applied to the writing you do fifty times a day.

Channel: talk to decide, write to record

Choose by speed, permanence, and emotional load. Email for records and decisions; chat for quick questions; a call for anything sensitive or going in circles (if a thread hasn't converged after three rounds, stop typing and call); a meeting for group decisions (agenda email before, decisions email after).

Etiquette is risk management

Choose recipients consciously (reply-all is a decision, not a reflex); CC = for awareness, BCC rarely and never to secretly watch; calibrate tone warmer than feels natural (text reads colder than you intend); never send angry (draft it, wait an hour); acknowledge even when you can't fully answer yet.

The three hard emails are structural

  • Request: ask first and specific → brief why → real deadline with a reason → remove friction → easy out. Could they say yes in 30 seconds with no follow-up question?
  • Bad news: news early and framed → own your part in one sentence → lead with the plan and a date → say what you need. Bad news + a credible plan = manageable; bad news alone = a crisis.
  • The "no": acknowledge → decline clearly and early → one brief reason → leave a door open (an alternative, a later date). Never go silent; never bury it in apology.

If you remember three things

  1. Write the ask first, and cut everything that doesn't serve it.
  2. The subject line is the most important text — could the reader triage from it alone?
  3. For bad news and the "no," lead with the plan or the path forward — structure carries hard news better than soft words do.

Themes this chapter surfaced: #2 audience-is-everything · #5 structure-serves-the-reader · #6 every-sentence-earns-its-place.

Threshold concept: An email is a tool for getting one specific action, not a record of everything you know.


Back to: Chapter 19 · Exercises · Quiz · Further Reading