Case Study 1 — Redesigning the Wall of Text

A note on this example. The document below is a composite—fictional but realistic, assembled from the kind of internal report that lands in inboxes every day. No real organization or person is depicted. We're illustrating a design principle, so the "before" and "after" carry the same words; only the visual presentation changes. That constraint is the whole point: it isolates design from writing.

The situation

Priya, a platform engineer, sends her manager a one-page quarterly reliability update. The writing is fine—clear sentences, accurate numbers, a real recommendation. But she pasted it into the email body as one block, hit send, and moved on. Her manager skims it for ten seconds, can't find the recommendation, and files it under "read later" (i.e., never). The content was solid. The delivery surface was hostile. This is the §10.1 flinch test failing in real time: the manager judged the block of text and bounced before reading it.

The "before": a wall of text (described)

Picture the email body exactly as sent:

❌ Before (described): No subject beyond "Q3 update." No heading inside. The text runs the full width of the email window—on the manager's wide monitor, about 120 characters per line. It's a single continuous paragraph of roughly 220 words, no breaks. Every sentence is the same size and weight. The three things the manager actually needs—(1) we had two incidents, (2) both are now fixed, (3) I recommend funding one engineer to finish the alerting work—are scattered through the middle and end of the block, in plain text, indistinguishable from the surrounding detail. The 99.92% uptime figure and the single recommendation sit mid-paragraph with no visual prominence whatsoever.

Read it the way the manager does—skimming, between meetings. There is no entry point (nothing says "start here" or "here's the bottom line"), no hierarchy (everything looks equally (un)important), no white space (nowhere for the eye to rest), no navigation (no headings to jump between), and the line length is exhausting (the return sweep keeps missing). Against the chapter's principles, the failures are exact:

  • No visible hierarchy (§10.3): the recommendation and the key number have no more prominence than routine detail.
  • No white space (§10.1, §10.3): one undifferentiated block; the eye has nowhere to rest and reads it as a chore.
  • Line too long (§10.2): full-width text makes the return sweep error-prone, adding physical reading effort.
  • No emphasis where it counts (§10.5): the one number and the one recommendation that the manager needs are not set off at all.

Note what is not wrong: the sentences. The writing passed Chapters 3 and 4. The document still failed—because design is the layer the reader hits first, and it failed.

The "after": same words, designed (described)

Now redesign using only typography, white space, hierarchy, and one stroke of emphasis. Not one word changes.

✅ After (described): Subject line: "Q3 reliability: 99.92% uptime, 2 incidents (both fixed) — 1 ask." The email opens with a one-line bold bottom line: "We hit 99.92% uptime this quarter. Two incidents, both resolved. One ask: fund one engineer to finish alerting." Below it, white space, then three short sections under clear, bold headings—"What happened," "What we fixed," and "The one ask"—each heading larger and bolder than the body, with more space above than below. The body sits in a comfortable column (margins added, so ~70 characters per line), in short three-to-four-line paragraphs separated by visible space. The single key number (99.92%) and the recommendation appear in the bold opening line and again in their sections; nothing else is bolded, so they stand out. The page now has air and an obvious reading path.

What changed, structurally and visually:

  • A visible bottom line leads (§10.3, and Ch 4's BLUF): the manager reads one bold line and already has the recommendation and the headline number. If she stops there, she still got the point.
  • Real, informative headings create hierarchy and navigation (§10.3, §10.6): she can scan three headings and jump to "The one ask." The headings are real (semantic), so they also work for a screen reader and in the inbox's outline.
  • White space and short paragraphs de-wall the page (§10.1, §10.3): grouping by proximity, room to rest; the email now invites rather than repels.
  • Line length constrained (§10.2): the return sweep is reliable; less reading effort.
  • Exactly one thing emphasized (§10.5): the bottom line and key number are bold; because nothing else is, they actually catch the eye.

The lesson

The "before" and "after" are the same writing. Every improvement lives in the visual presentation. That isolates the lesson cleanly: how a document looks determines whether good writing gets read. Priya didn't need to write better; she needed to design the surface so her already-good writing could land. The fix took five minutes and zero rewriting—a subject line that carries the bottom line, a one-line bold lead, three real headings, short paragraphs with air, a constrained column, and a single emphasis.

This is the wall-of-text anchor from §10.1, made concrete in a document you'll send a hundred times. The diagnostic question to carry away: before I send this, if the reader looks at it for three seconds without reading, can they see where to start, what matters most, and where to go? If the page is a gray block, the answer is no—and no amount of sentence-level quality will save it.

Related: Chapter 10 §10.1, §10.3 · Case Study 2 · Further Reading