Nobody Reads; Everybody Skims

Your message doesn't arrive on a desk. It arrives in a queue — between forty others, on a phone, in the ninety seconds between meetings, competing for a reader whose attention (as the focus topic on this shelf documents in painful detail) is the scarcest thing they own. Eye-tracking research on how people actually read screens found the same shape over and over: a quick scan of the opening, a skim down the left edge, and out. Nobody reads. Everybody triages. The messages that get answered aren't the best-written in any literary sense — they're the ones engineered to survive triage.

The reframe: writing as interface design

School taught writing as expression: build context, develop the argument, arrive at the point. Workplace writing inverts every step, because the reader isn't grading you — they're deciding, in seconds, three things: what is this, what do you want from me, and how much will it cost? A message that answers those three instantly gets processed; one that makes the reader excavate gets deferred, and "deferred" is where replies go to die. So treat every message as an interface: the subject line is the button label, the first sentence is the function, the formatting is the affordance. Ugly-but-instant beats elegant-but-buried, every day of the working week.

The topic in one acronym, then five parts

Militaries, who cannot afford buried leads, codified the whole discipline as BLUF: Bottom Line Up Front — the conclusion or request first, support after. Everything ahead is BLUF, elaborated:

1. The subject line and first sentence — the eight words that decide whether the rest exists (Part 2).
2. One ask, formatted for skimmers — why multi-part messages get part-answered, and structure that survives a phone screen (Part 3).
3. The pre-answered message — anticipating the questions so the yes requires zero work (Part 4).
4. Tone, rank, and hard messages — how text loses warmth in transit, asking upward, and writing the difficult ones (Part 5).
5. Follow-ups and escape hatches — bumping without nagging, and knowing when a thread should become a call (Part 6).

One reassurance before the mechanics: none of this is about writing more — it's almost entirely about writing less, sooner. The skills transfer wholesale across email, chat, tickets, and texts to your landlord; the examples ahead default to email because it's where the stakes and the bad habits both concentrate.