DOCUMENT DESIGN AND READABILITY

A document does not begin to be read at the first word. It begins at the first glance, and in that glance a reader decides whether to engage, skim, or postpone. Chapter 3 taught you to make sentences plain. This chapter is about everything around the sentence — the headings, the chunks, the lists and tables, the white space, the type, the contrast — because a clear sentence buried in a grey slab of unbroken text is functionally invisible. The people you write for at work read standing up, between tasks, on a phone, with someone talking to them. Design is how you meet them there. You will learn to build a page a hurried person can navigate, to convert dense prose into a table that answers a question in three seconds, to spend emphasis like money, and to check that your document still works for a reader using a screen reader or a five-inch screen.

Section 1Design Is Not Decoration

What readers actually do with a page

Writers imagine a reader starting at the top left and proceeding, word by word, to the end. Almost nobody does that at work. The realistic reader arrives with a question — do I have to do something, by when, and is this about me? — and hunts for the answer. If the page gives that hunt no handholds, the eye falls back on a default sweep: across the top, down the left edge, a shorter sweep further down, then out. Practitioner research on web reading calls this an F-shaped pattern, but the useful lesson is not the letter of the alphabet. It is that the F-shape is what happens when a page offers nothing better. Good design interrupts it on purpose.

Two consequences follow, and they govern everything else in this chapter. First, the top-left of every block is expensive real estate, because that is where the eye lands. Put the load-bearing word there: not “Please note that the deadline is Friday,” but “Deadline: Friday, March 14.” Second, anything visually uniform is invisible. A reader cannot find the important sentence in a paragraph where every sentence looks identical, any more than you can find one grey stone in a driveway of grey stones. Difference is what the eye detects. Design is the deliberate creation of useful difference.

It also helps to separate two words that get used interchangeably. Legibility is whether a reader can distinguish the characters — a function of type size, contrast, and print quality. Readability is whether a reader can get the meaning without undue effort — a function of sentence construction, structure, and page layout together. A document can be perfectly legible and terribly unreadable. That is, in fact, the normal condition of workplace policy.

The four moves that do most of the work

You do not need a design degree to produce a clean professional document. Four principles — long taught in design instruction as proximity, alignment, contrast, and repetition — will carry you through nearly every memo, report, and handout you will ever build. They are not aesthetic preferences. Each one exploits something the visual system does automatically.

Proximity. Things close together read as one group; things far apart read as separate. This is why a heading pressed tight against the paragraph it introduces, with a larger gap above it, is instantly understood, while a heading floating equidistant between two paragraphs is ambiguous. Practical rule: the space above a heading should be visibly larger than the space below it. The same logic applies to a caption and its figure, a label and its field, a subtotal and its column.

Alignment. Every element on the page should line up with something else on the page. Centered headings over left-aligned text, bullets indented to three different depths, and a signature block wandering toward the middle all create a low-grade sense of disorder that readers feel without being able to name. Pick a left edge and defend it. Contrast. If two things are different, make them clearly different — a heading two full steps larger than body text, not one point larger. Timid contrast looks like a mistake. Repetition. Whatever you do once, do the same way every time: same heading style at the same level, same bullet character, same spacing before tables, same date format. Consistency is what lets a reader learn your document in the first thirty seconds and then navigate it without thinking.

A worked rebuild

Here is a real shape of workplace writing — accurate, complete, and nearly unusable. Before: “All staff are reminded that under the revised attendance policy effective March 1, absences must be reported to the charge nurse no later than two hours before the start of the scheduled shift, except for night shift, where the notification window is three hours, and documentation for absences exceeding two consecutive shifts must be submitted to Employee Health within seventy-two hours of return to work, and failure to comply with either requirement may result in the absence being recorded as unexcused, which affects eligibility for shift differential and may be considered in the annual review.”

That is one 95-word sentence containing four separate rules, an exception, and three deadlines. Nothing is wrong with the information. Everything is wrong with its delivery: a night-shift nurse looking for her own deadline must parse the entire sentence, hold two clauses in memory, and hope she did not misread the exception. After: a heading that names the topic (“Reporting an absence — effective March 1”), then three short chunks, each with its own bold label: Call in by, Send documentation when, If you miss the window. Under “Call in by,” two lines — day shift, two hours; night shift, three hours. Same words. Same policy. A ten-second read instead of a ninety-second one, and far fewer honest mistakes.

Notice what the rebuild did not do. It did not simplify the policy, soften the consequence, or drop a requirement. Document design is not a way of saying less; it is a way of making the same content findable. That distinction matters in regulated environments, where people sometimes resist formatting on the grounds that the text is legally exact. Legally exact and physically unreadable is not a defensible combination — a rule nobody can locate is a rule nobody follows.

Section 2Chunking, Headings and Hierarchy

Chunking: one idea per block

Chunking means dividing content into pieces small enough for a reader to take in and label as a unit. In practice this means a paragraph carries one idea, a section carries one topic, and each block opens with the sentence that states its point. Everything after that first sentence is support: evidence, exception, example, qualification. Readers who are skimming will read only the first sentence of each paragraph, and a well-chunked document rewards exactly that behavior. This is sometimes called topic-first or lead sentence structure, and it is the single highest-yield habit in professional prose.

How big should a chunk be? There is no sacred number, and anyone who gives you one is overselling. A workable convention for workplace documents is three to six sentences on paper, and fewer on screen — two or three sentences reads comfortably on a phone where a five-sentence paragraph becomes a scrolling wall. Procedural content chunks tighter still: one action per numbered step. Analytical writing can and should run longer, because an argument that keeps stopping every two lines never builds. Match the chunk to the work the reader must do, not to a rule.

The opposite failure is worth naming, because it is fashionable. Text broken into one-sentence paragraphs, every line floating in its own island of white space, does not read as clear; it reads as fragmented, and it destroys the writer’s ability to show that idea B follows from idea A. Chunking is about grouping related sentences together as much as it is about separating unrelated ones. A page of confetti is as hard to use as a page of concrete.

Headings that carry content

Most workplace headings are labels: Introduction, Background, Discussion, Findings, Conclusion. They tell the reader what kind of text follows but nothing about what it says. An informative heading — sometimes called a talking heading — states the content itself, so a reader who reads nothing else still leaves with the substance. The difference costs you five extra words and buys enormous comprehension.

Three practical constraints. Keep headings short enough to scan, roughly three to eight words. Front-load the distinctive word, because a column of headings that all begin “Recommendation regarding…” defeats the purpose. And make headings honest: a heading is a promise about the section beneath it, and a reader who follows a heading to content that does not match it stops trusting your headings altogether — which means they must now read everything, which is exactly what you were trying to prevent.

One caveat about house style. Some organizations, journals, and regulatory formats require fixed heading names, and grant proposals in particular often mandate the reviewer’s own outline word for word. When a template governs, follow the template — but you can still put an informative first sentence directly under a mandated label, which recovers most of the benefit. Where you have freedom, use it.

Levels, parallelism, and the outline test

A heading hierarchy is a claim about structure: a level-two heading says “this is a major division,” and a level-three says “this is a part of the division above.” Two rules keep it honest. First, never skip a level — do not jump from a level two to a level four because you liked the size of the type. Second, never create a lone subheading. If a section has only one subsection, that subsection is the section; either merge it upward or find its sibling.

Keep headings at the same level grammatically parallel. If one level-three heading is a noun phrase (“Consent requirements”), the others at that level should be noun phrases too, not a mix of questions, commands, and sentences. Parallelism is not fussiness; it is a signal that these items are the same kind of thing, and the eye reads that signal faster than the mind reads the words.

Then apply the outline test. Copy your headings alone into a blank page, in order, with nothing else. Read them straight through. Do they tell a coherent story? Does the sequence have a logic — problem, options, recommendation, cost — or is it a pile? Is anything missing that a reader would expect between two adjacent headings? Most structural problems in a report are visible in the heading list within ten seconds and invisible in the full draft for days. If your word processor builds a navigation pane or an automatic table of contents from your styles, you already have this view; open it and read it as a document.

Section 3Lists, Tables and White Space

Choosing the form: prose, list, or table

Every piece of content has a natural shape, and most readability complaints are really shape errors. Prose is for reasoning — ideas that connect to each other with because, therefore, however. A list is for a set of items that do not need those connectors. A table is for items compared along two or more dimensions. Force reasoning into bullets and you strip out the logic; force a comparison into prose and you make the reader build the table in their head.

Watch for the tell. When a paragraph starts stacking conditions — “if you are on days, then two hours; if nights, three hours; if you are per diem, contact staffing directly” — you are describing a table in sentences. When a paragraph contains a series of “first, next, then, finally,” you are describing a numbered list. When a paragraph contains three or more items joined by commas and the word and, and each item is more than a few words, you are describing a bulleted list. Convert.

List mechanics that keep lists honest

Lists fail in predictable ways. Fix them with four mechanics. Give the list a stem. The line before the list should say what the list contains and, if the reader must act, what they must do: “Bring all four items to the credentialing appointment:” is a stem; “Below are some things:” is not. A stem also tells the reader whether the list is all-of, any-of, or one-of — a distinction that matters enormously in policy and that bullets alone cannot express.

Keep the items parallel. Every item should start with the same part of speech and complete the stem grammatically. Weak: “Photo ID / You will need your immunization record / Signing the attestation form / License.” Stronger: “Photo ID / Immunization record / Signed attestation form / Current license.” Read the stem plus any single item aloud; if it does not make a sentence, the item is broken.

Control length and depth. A list of more than about seven items stops functioning as a scannable set and becomes a wall with dots; group it into two labeled lists or promote it to a table. Nesting beyond one sublevel is almost always a sign that you have a table or a set of sections. And punctuate consistently: fragments take no terminal punctuation, full sentences take periods, and you use one convention throughout the document. The specific convention is a house-style choice on which respected style guides genuinely differ — what is not optional is picking one and holding it.

Tables: the highest-value move in workplace writing

If you learn one design skill from this chapter, make it converting condition-heavy prose into a table. Consider the attendance policy from Section 1, with the per diem case above folded in. In prose it was a 95-word sentence. As a table it becomes something a reader solves rather than reads — find your row, read across, stop.

Four design rules make a table work. Put the thing the reader knows in the first column — they arrive knowing their own shift, not the deadline, so shift is the entry point. Give every column a header that carries the unit, so the cells can stay bare: heading the column “Call in by (hours before shift)” lets each cell read simply 2 or 3, instead of repeating hours before start down the column. Align text left and numbers right, with decimals lined up, because a ragged number column cannot be compared at a glance. And never leave a cell empty when you mean zero or not applicable — an em dash or the words not applicable tells the reader the omission was deliberate rather than an error.

Two limits worth respecting. Tables wider than about five or six columns break badly on phones and in printed portrait pages; if you need more, split the table or rotate it so the long dimension runs down rather than across. And a table is for lookup, not for argument: it will not tell your reader why Option B is better, only what each option costs. Chapter 8 takes this further into charts and quantitative displays, where the same discipline applies with higher stakes.

White space is content

White space is the unmarked area of the page — margins, the gap between blocks, the indent, the space around a heading. Beginners treat it as waste and fill it; experienced writers use it as the primary tool for showing structure. Space above a heading defines where a section starts. Space around a warning makes the warning visible without any color at all. Generous margins are not extravagance; on a printed clinical protocol they are where the annotations go.

Two related settings deserve deliberate choices. Measure is line length. Typographic convention puts a comfortable measure somewhere in the range of 45 to 75 characters per line, with roughly 66 as a frequent target, because very long lines make the eye lose its place on the return sweep and very short ones break phrases awkwardly. Be honest about the evidence here: controlled studies of optimal line length have produced mixed results, and some find longer lines are read faster even though readers prefer shorter ones. The convention is a defensible default, not a law. On a full-width page, the practical fix is wider margins or a two-column layout rather than edge-to-edge text.

Leading, or line spacing, is the vertical distance between lines. Body text set too tight blurs into a grey mass; too loose and lines stop reading as a paragraph. Something in the range of 1.15 to 1.5 times the type size suits most business documents, and accessibility guidance specifically supports readers being able to increase line height to 1.5 without the layout breaking. Whatever you choose, do not use double line spacing to fake length in a professional document. Your reader has seen that trick since high school.

Section 4Type, Emphasis and Visual Signals

Size, spacing, and the choices that actually matter

Start with size, because it is the setting people get wrong most often and fix most easily. Printed body text below about 10 points is hard for many adult readers and genuinely excluding for older ones; 11 or 12 points is the ordinary professional range. On screen, browser default body text is commonly around 16 pixels, and shrinking it to look elegant is a decision to lose readers. If a document will not fit in its page limit at a readable size, the answer is to cut content, not to cut type. A reviewer who has to lean in has already formed an opinion about your document.

Next, establish a type scale: a small set of sizes with clear steps between them, used consistently. Three or four sizes is plenty for most workplace documents — title, section heading, subheading, body — with captions and footnotes one step below body. The step between levels should be obvious at a glance. A heading one point larger than body text does not read as a heading; it reads as a typo.

Then stop. The remaining typographic decisions have far less effect than writers imagine, and time spent on them is usually time stolen from structure. Two typefaces per document is the practical ceiling — commonly one for headings and one for body, or simply one family used at different weights. And if your employer supplies a template, use it: consistency across an organization’s documents is worth more than your improvement to any single one.

What the evidence does and does not say about typefaces

You will hear confident claims that serif faces are more readable in print and sans-serif faces more readable on screen. Treat this with caution. The research literature comparing serif and sans-serif reading performance is genuinely inconsistent, and several careful reviews have concluded that differences in reading speed and comprehension between mainstream, well-designed faces are small or absent once size and spacing are controlled. Familiarity and rendering quality appear to matter more than the presence of serifs. The old advice was formed when screens were low-resolution enough that fine serifs smeared; that constraint has largely disappeared.

What does hold up is less glamorous. Adequate size, adequate contrast, adequate line spacing, and a face with distinguishable characters make a measurable difference — particularly the distinction between capital I, lowercase l, and the digit 1, which matters enormously when your document contains medication names, room numbers, or account codes. Decorative, condensed, and light-weight faces reduce legibility for everyone and disproportionately for readers with low vision. Some typefaces are marketed as improving reading for people with dyslexia; controlled studies of these designs have not consistently shown a reading advantage over ordinary clear faces, and researchers in the area generally emphasize adjustable size and spacing over any specific typeface. Say “the evidence is mixed” rather than repeating the marketing.

The emphasis budget

Emphasis works by contrast, which means it is a fixed budget: every additional bold phrase devalues the ones already there. Decide before you start how many things on a page truly must be found first — usually one or two — and spend accordingly. The disciplined approach is to emphasize the item a reader would be harmed by missing, and to let structure (headings, position, tables) do everything else.

Each device has a job and a characteristic failure. Bold is for the thing a scanning reader must catch — a deadline, a dose limit, a name. It fails when a writer bolds every term they consider important, which is most of them. Italic is for titles, defined terms, and light vocal stress; it is weak in scanning and poor for long runs, especially on screen. Underline in a digital document is now effectively reserved for hyperlinks, and underlining plain text makes readers try to click it. ALL CAPS is read somewhat more slowly than mixed case — the mechanism is debated, with the old word-shape explanation contested by later research — and, more decisively for professional writing, extended capitals read as shouting. Reserve them for short signal words.

Color deserves its own rule: never let color be the only carrier of meaning. Roughly one in twelve men of northern European ancestry has some form of color-vision deficiency, documents get printed in greyscale, and a red row that means “overdue” becomes an ordinary grey row on the copier. Pair color with a word, a symbol, or a position — red plus the word Overdue, not red alone. That single habit resolves most accessibility complaints about color before they happen.

Callouts, captions, and other signals

A callout is content lifted out of the flow and boxed or ruled — a warning, a definition, a worked example, a reminder. Its power comes entirely from rarity. One callout on a page is a landmark; four are wallpaper. Give each callout a one-word label so its type is instantly recognizable (Warning, Example, Note) and use the same label for the same purpose every time. Safety-critical documents follow formal conventions on signal words, and Chapter 7 treats those in the context of instructions and procedures.

Captions carry more weight than most writers realize, because a scanning reader looks at every figure and reads its caption before reading any body text near it. A caption that says “Figure 3” wastes the one line you were guaranteed to have read. Write captions that state the point: “Figure 3. Fall rates fell on all four units after the July form change.” Number figures and tables if the document is long enough that someone will reference them, and refer to them by number in the text rather than by “the table below,” which stops being true the moment the document reflows on a different screen.

Section 5Accessibility, Devices and the Design Review

Designing for readers who cannot see your layout

Some of your readers will hear your document rather than see it, through a screen reader, or will see it enlarged four hundred percent, or in high-contrast mode with your careful colors stripped away. This is not a niche concern in the settings most of you work in: it is a legal obligation for many public institutions, a contractual one for many vendors, and a matter of basic professional competence everywhere else. The good news is that the changes are small and they improve the document for everyone.

Four habits carry most of the load. Use real headings. A heading created by making a line bold and large is not a heading to software — it is a bold paragraph. Applying the built-in Heading 1 and Heading 2 styles in your word processor, or true heading tags on a web page, creates the structure that lets a screen-reader user jump between sections the way you skim with your eyes. It also generates your table of contents for free, so the accessible choice is also the lazy one.

Write alt text. Every image that carries information needs a short text description of what it shows and, crucially, why it is there — “Line chart: falls per thousand patient-days dropped from 4.1 to 3.3 after July” beats “chart.” Purely decorative images should be marked as decorative or given empty alt text so a screen reader skips them rather than announcing a filename. Write meaningful link text. Screen-reader users often pull up a list of a document’s links out of context, and a list reading “click here, click here, more, here” is useless; link the destination instead — “the 2026 immunization policy.” Give tables real header cells and avoid merged cells and blank spacer rows, which scramble the reading order.

On contrast, there are published numbers you can check rather than guess. The Web Content Accessibility Guidelines set a minimum contrast ratio of 4.5 to 1 between text and its background for ordinary text, and 3 to 1 for large text — defined as at least 18 point, or 14 point bold. The stricter enhanced level asks for 7 to 1 and 4.5 to 1 respectively, and meaningful non-text elements such as icons and input borders are expected to reach 3 to 1. Free contrast checkers will compute the ratio from two color values in seconds. Light grey text on white, the most common design mistake in professional documents, usually fails these thresholds badly.

One document, many screens

Assume your document will be opened on a phone, because a large share of workplace email is. That single assumption drives several choices. Keep tables narrow enough to survive without horizontal scrolling. Avoid layouts that depend on a specific page break, since a document that reflows will move it. Do not build meaning into position — “see the box at right” may render below on a narrow screen. And be careful with documents composed as images: a scanned memo or a poster exported as a picture cannot be searched, zoomed cleanly, resized, or read aloud, which is why a photographed page is one of the least accessible things you can circulate.

Accessibility guidance formalizes this. Content is expected to remain usable when text is resized to two hundred percent, and to reflow into a single column without two-dimensional scrolling at the equivalent of a narrow phone width. Readers should also be able to increase line height and letter spacing without text disappearing behind other elements. You do not need to memorize the clause numbers; you need to open your own document on a phone before you send it to two hundred people. That thirty-second test catches nearly everything.

Screen and print are different media, and if the document will live in both, check both. Fine hairlines and pale tints vanish on a copier. Colors shift. Hyperlinks become invisible text, so a printed document that says “see the policy” with the URL hidden behind the words gives the reader nothing — spell out the address or provide a reference. Conversely, a document designed for print often wastes screen space with wide margins and small type. When in doubt, design for the medium in which the decision will actually be made.

Readability scores and their real limits

Software will happily give you a readability formula score — Flesch Reading Ease, Flesch–Kincaid Grade Level, SMOG, Gunning Fog. All of them work essentially the same way: they count words per sentence and syllables (or long words) per word, and convert the result into a single number — a US grade level for most of them, and for Flesch Reading Ease a 0-to-100 score on which higher means easier. That makes them useful as a rough smoke alarm. A document scoring at a graduate reading level when it is meant for patients or new hires is telling you something real.

But be clear about what they cannot do, because these scores are frequently misused as evidence of quality. They cannot detect whether your sentences are in a sensible order, whether a pronoun has an antecedent, whether an important step is missing, or whether the words are familiar — medication is four syllables and universally understood, while gait is one syllable and unknown to most patients. They cannot see your headings, tables, or white space at all: the visual structure that does most of the work of making a document usable is simply invisible to a tool that can only count words, sentences and syllables. And they are trivially gamed by chopping sentences at the commas, which raises the score while making the prose harder to follow. Reading researchers have criticized formula-driven writing on exactly these grounds for decades. Use a score as one signal among several, report it honestly if your organization requires it, and never let it override a real reader.

The better test is empirical and cheap: give the document to two people who resemble your actual audience, ask them to find a specific fact under mild time pressure, and watch. Where they hesitate is a design defect. This is a stripped-down version of usability testing, and in workplace settings it takes about ten minutes and outperforms every automated metric available.

The design review

Design review is a separate pass, done after the content is settled and before the document goes out. Do it on a printout or on a phone, not in the editing window where you wrote it, because the window you drafted in is the one context in which the document is guaranteed to look fine. Run the squint test first, then work the rubric below. Chapter 14 places this pass inside a full editing and quality-control workflow; here, treat it as the last thing you do before hitting send.

Words worth knowing