How Executives Read — Skimming Patterns, Decision Triggers, the 30-Second Test

Executives read differently from other audiences. This is not a character assessment — it is an operational description of how people with constrained time and high decision load process written information. They skim first. They look for the headline, the recommendation, or the number that tells them what the document is asking of them. If they find it quickly, they may read deeper. If they do not find it in the first thirty seconds, they table the document or delegate it.

The thirty-second test is not a metaphor. In practice, an executive opening a memo or report will spend approximately thirty seconds orienting: reading the subject line or heading, scanning the first paragraph, and deciding whether the document requires their attention or someone else's. A document that does not surface its essential content within that window fails, regardless of the quality of its analysis. The writer who understands this does not resent it — they design for it.

The executive reading pattern works in three phases. Phase one: orientation. The executive reads the title, subject line, or heading. They look for context clues: who sent this, what decision does it require, what is the timeline? A document that provides these signals in the heading and first line has already won the first phase. Phase two: the skim. The executive scans the visual structure — section headers, bullet lists, callout boxes, bold text. In under a minute, they have formed a hypothesis about what the document is saying. Phase three: selective depth. If the hypothesis is interesting enough, they read the sections that support or challenge it. They do not read every word. They read the words that are most relevant to the decision they need to make.

1. The Thirty-Second Test Hand your document to someone and give them thirty seconds. Ask them: what is this document recommending? What action does it require? If they cannot answer both questions from a thirty-second read, the document needs restructuring before it is sent. This is not a test of the reader's attentiveness — it is a test of the document's design. A well-designed executive document passes the thirty-second test without exception.
2. Decision Triggers Executives respond to specific textual triggers that signal relevance: numbers with dollar signs or percentages, dates and deadlines, named people with clear roles, recommendations with explicit action items. Each of these triggers tells the executive that the document has a concrete relationship to their world. Abstractions do not trigger. Vague calls to action do not trigger. 'We should consider whether to proceed' does not trigger. 'We recommend approving the Q2 budget reallocation by March 15' does.
3. Designing for the Skim Visual hierarchy is not decoration in executive documents — it is the primary navigation system. Section headers should be informative, not categorical. 'Recommendation' is a category header. 'We recommend delaying the vendor transition to Q3' is an informative header. The executive who skims only headers should understand the document's essential argument from the headers alone. Design your headers as complete thoughts, not labels.

A specific note on length: executives are not rewarded for reading longer documents. They are rewarded for making good decisions. A document that requires eight pages to make a one-page argument costs the executive seven pages of time and creates seven pages of noise between the recommendation and the action. The writers who have the most influence with executive audiences are consistently the writers who are briefest — not because executives do not value detail, but because they know how to find it when they need it. Put the detail in an appendix. Put the decision in the first paragraph.