What problem it solves
The numbers on reading from screens have repeated since 1997:
- 79% of participants in a Nielsen Norman Group study scanned every new page, and only 16% read word by word (1997).
- In an average visit to a 593-word page, people have time to read at most 28% of the words, realistically about 20%. Each extra 100 words adds 4.4 s to the visit, roughly 18 words read (2008).
- The same page rewritten shorter, with headings and lists and without promotional language, scored 124% better on a combined measure (task time, errors, recall): concise +58%, scannable +47%, objective +27% (1997).
The reader arrives with a question and looks for where it’s answered. Presentation decides whether they find the answer in seconds or leave, deciding it isn’t here.
Without presentation
- a 12-line paragraph with the answer in its middle
- headings “Description”, “Setup”, “Other”
- steps separated by commas inside a sentence
- half the text in bold, plus three colored “Important” panels
- a line across the whole monitor, 140 characters
With presentation
- the answer in the first sentence, details below
- headings “Where the backups live”, “Restore in 4 steps”
- steps as a numbered list, commands as code blocks
- one highlighted spot — the thing you can’t miss
- a 65–80 character column, white space around groups
How the eye moves over a page
In 2019 NN/g described four ways of scanning text. Which one kicks in depends on the page as much as on the reader:
the page opened
- The first screen
heading · leadDeciding whether this is the right place. What’s visible without scrolling gets 57% of viewing time, the first two screens 74% (NN/g, 2018). - Layer cake
h2 · h3The gaze jumps between headings and reads the text under the right one. The fastest way to find yours — but it only works if the headings say what’s under them. - Spotted
**bold** · `code` · 42The gaze catches on what stands out: links, bold, numbers, code, a word from the reader’s question. - Commitment
paragraphThe section found, it’s read in full. People read this way when the text is clearly about their task: best understanding, most time spent.
the answer found
When there’s nothing to hold on to — no headings, lists or highlights — you get the F-pattern: the first lines are read in full, then less and less, and toward the bottom only the first words of lines. The F-pattern says more about the page than the reader: that’s how unstructured text gets scanned.
Five techniques, and what to add to them
Scannable text
The page makes sense from its headings and first sentences, without reading straight through (Scannable text).
Chunking
A paragraph is one thought, a section one question, a step one action (Chunking text).
White space
Spacing shows what belongs with what: smaller inside a group than between groups (White space in CSS).
Visual anchors
Headings, numbers, code, tags — the gaze catches on them while scanning (Visual anchors).
One screen, one idea
What’s visible without scrolling answers one question (One screen, one idea).
The five techniques rest on a few simpler rules:
| Rule | Why | Details |
|---|---|---|
| the answer first | the inverted pyramid: the conclusion at the start, details in decreasing importance | Answer first |
| a heading says what’s inside | “Where the backups live” gets found, “General information” doesn’t | Headings say what’s inside |
| the key word at the start of the line | the eye takes the first two words of a list item, about 11 characters | Key word first |
| three levels of importance | main, normal, secondary — by size, weight, color | Three levels of importance |
| a line of 45–80 characters | longer, and the eye loses the start of the next line | Line length |
| text contrast of at least 4.5:1 | light gray #999 on white is 2.85:1 |
Text contrast |
Typeface, size and typesetting rules are covered in Typography, the palette and dark mode in Color.
Which form fits the content
Part of presentation is choosing the form. Telling in a paragraph what asks to be a table is like reading a table out loud.
| If the information is… | Use |
|---|---|
| actions in order: a step is one action plus what should happen | a numbered list |
| uniform items with no order: requirements, files, reasons | a bulleted list |
| two or three things across several attributes: things in rows, attributes in columns | a table |
| “if… — do…” more than twice | an “If… — Do” table |
| the path of a request, packet or data through several links | a labelled diagram |
| an argument with “because” and “so”: the connections are the content | a paragraph |
| a command, a path, a config fragment — things people copy (Code as text) | a code block |
| where to click in an interface | an annotated screenshot |
| one warning without which something breaks | a warning block |
Where it’s used
Documentation and READMEs
People come back to it with a specific question: “how do I restart”, “where’s the config”. It’s read by headings.
An incident runbook
The reader is in a hurry and nervous — and reads even less. Steps, commands as blocks, a check after each step.
A chat message
The first line shows in the notification and the chat list. The question or the conclusion goes there, details below.
Interfaces and dashboards
The same rules: one screen, one question; three levels of importance; a label on every number.
Slides
A slide’s title is the conclusion as a sentence, not the topic: “Latency grew after the update”, not “Latency”.
What you get and what it costs
What you get
- The answer is found in seconds. Headings work as a table of contents: the right section is visible before reading.
- What’s needed gets read to the end. A three-paragraph section is read in full; a twelve-paragraph wall is skipped.
- The text is easier to edit. An outdated step changes on its own, without rewriting the paragraph around it.
- Gaps in the content show. An empty section or a step without a result catches the eye; in solid text it hides.
- Pieces get copied. A step or a table is forwarded to a chat whole, without retelling.
What it costs
- Chunking breaks an argument. A list of fragments loses “because” and “so”. Edward Tufte analyzed this on a NASA slide during the 2003 Columbia flight: the caveat that the tests didn’t cover debris of that size ended up in the bottom item of a nested list.
- White space lengthens the page. More scrolling and less visible at once; for a cheat sheet kept open, density matters more.
- Writing takes longer. First a plan around the reader’s questions, then the text, then a check by headings.
- Structure masks emptiness. Headings and lists look solid even with nothing under them.
- Cutting loses caveats. “Not tested on ARM” and the version are the first candidates for cutting, and without them the text can’t be trusted.
Where to start
- Presenting information: how people read a screen and what follows from it
- Scannable text: reworking a wall of paragraphs step by stepRework a wall of paragraphs step by step: the answer to the top, sections by question, steps as a list, a check by headings.
- Chunking text: where to cut and how much goes in one chunkWhere to cut text and how much goes in one chunk: a paragraph, a list, a section, a table, a screen.
- White space in CSS: column width, line height and spacing line by lineColumn width, line height and spacing line by line in CSS: which values and why.
- Visual anchors: what the eye catches on, and when it stopsWhat the eye catches on — headings, numbers, code, tags — and when an anchor stops working.
- There are three levels of importance: primary, normal, secondaryThree levels of importance through size, weight and color — and why nobody can tell a fourth apart.
- One screen, one ideaWhat fits without scrolling answers one question: the first screen, a slide, a dashboard, a message.
- What spoils a layout: the sign, why it hurts, what to use insteadThe sign, why it hurts, what to use instead: text, emphasis, color, spacing, tables, images.
- Checking presentation before publishing: six checks in the browserSix checks before publishing: headings in a row, the blur test, a phone, dark mode, five seconds.
If it doesn’t work
The answer is on the page, but people still ask
- Cause
- The answer sits in the middle of the third paragraph. When scanning, the eye takes the heading and the starts of paragraphs and doesn’t touch the middle.
- Fix
- Put the answer in the section’s first sentence, and a word from the question in the heading (Answer first).
People scroll to the end of the page and leave
- Cause
- The headings are generic: “Introduction”, “Details”, “Other” — they don’t tell you which section holds what you need.
- Fix
- Rewrite the headings so that they alone show the page’s plan (Headings say what’s inside).
Lots is highlighted, and the main thing is invisible
- Cause
- Bold, color and boxes in every paragraph. Emphasis works while it differs from its surroundings; when everything is highlighted, the eye stops trusting it.
- Fix
- One or two highlights per screen, the rest in plain text (Bold: one or two spots).
The text was broken into bullets, and it didn’t get clearer
- Cause
- An argument was chopped into fragments: “because” and “so” are gone, and the reader has to rebuild the links between bullets.
- Fix
- Uniform items go in a list, an argument in a paragraph (Chunking text).
Neat on a computer, a mess on a phone
- Cause
- A six-column table, with spacing and width tuned for a wide screen. At 360 px a paragraph line holds about 35 characters instead of 76.
- Fix
- Look at the page at 360 px wide before publishing (Checking presentation).
Nobody notices the warning
- Cause
- Five colored “Important” boxes per page. Bright panels look like ads and get skipped — banner blindness.
- Fix
- One warning per page; the rest as plain text next to the step it belongs to.