Write for a reader in a hurry
Writing Guide >
The principle
Picture the person your report is actually written for. It is half past ten at night. They have nine other papers to read before tomorrow's meeting and yours is somewhere in the pile. They are tired, reading on a screen, and they will give your document a few minutes at most before deciding whether it deserves more. That is your reader. Write for them.
Most writing is built for a different reader: one who starts at the top, reads every line in order, holds the whole argument in mind, and arrives at your conclusion having followed each step. That reader does not exist. Writing for them produces a document that works only if it is read in a way nobody reads it.
So assume, every time, that the reader is rushed and half-attentive, and build the document to survive that. This is not a concession to lazy readers. It is the condition every real reader is in.
Why it fails in practice
We write for the attentive reader because we are the attentive reader. We have lived with the material for weeks. We know why the background matters, where the argument is heading, which number is the one that counts. Reading our own draft, we supply all the attention it needs, because we already have it. The tired reader at half past ten has none of that, and the document offers them no help, because it was written by the one person who could not feel its absence.
There is a quiet vanity in it as well. The attentive reader is the one who appreciates our thoroughness, follows our careful sequence, and is rewarded at the end. Writing for the hurried reader means giving that up: accepting that most of what we wrote will be skimmed or skipped, and that the paragraphs we laboured over may never be reached. That is not how we like to imagine our work being read, so we imagine it otherwise.
An example
Watch what a hurried reader does to a document, because it is not reading in any order you wrote for.
They read the title. They read the first line, perhaps the first paragraph. Their eye drops down the page and stops at whatever stands out: a heading, a bold figure, a short paragraph, a recommendation. If one of those gives them the answer, they have what they came for and they stop. If none of them does, they do not return to the top and read properly. They form a vague impression, decide the paper is heavy going, and move to the next one in the pile. Your document has been read, in the only sense that counts, in about ninety seconds.
The document that survives this is not shorter or simpler. It is built so that the ninety-second reading lands the main point anyway: the answer where the eye first falls, as 'Put the answer at the top' sets out, headings that tell rather than name, as in 'Write headings that say something', and the one figure that matters given the room to stand out.
What to do instead
Write the document, then read it as the hurried reader will. Give it ninety seconds. Look at the title, the first paragraph, the headings and whatever catches the eye, and nothing else. Then ask whether you have the answer and the decision. If you do, it will survive the pile. If you do not, the reader will not have them either, and no amount of careful argument further down will reach someone who has already moved on.
This is the premise the rest of the guide rests on. Everything in the chapters that follow, from the answer at the top to the first page that earns its lines, is a way of writing for the reader in a hurry.