Key Takeaways — Chapter 4: Structure
A one-page summary card. Use it to re-ground before the quiz, or to review weeks later.
The one idea
The reader scans; they do not read. Almost everyone reads technical documents by hunting—scanning headers, reading first sentences, jumping to the relevant part, leaving the moment they have what they came for. Structure is how you serve that behavior. For most technical documents, structure matters more than style: a clear sentence buried on page nine is invisible; a clumsy one in the first line gets read by everyone.
The core moves
- Top-down, not bottom-up. Writers default to the order they discovered things (chronological, conclusion last). Readers need the order they'll use (conclusion first). Convert one to the other.
- Inverted pyramid / BLUF. Most important information at the top. State your conclusion, recommendation, or request in the first sentence or two ("Bottom Line Up Front"), then support it. A reader who stops early still gets the essential message.
- Signpost. Tell readers where you're going before you go: forecasting statements (name what's coming and in what order), topic sentences (the point goes first in each paragraph), and transitions (how ideas connect).
- Informative headers + clean hierarchy. Headers state content ("Recommendation: Ship the One-Line Patch"), not form ("Discussion"). Heading levels nest one step at a time, no skips—this is also an accessibility requirement, because screen-reader users navigate by heading.
- Lists vs. prose. Lists for discrete, parallel items (steps, requirements, options). Prose for connected reasoning (arguments, trade-offs). Tell: if you'd write "because/therefore/however" between bullets, make it prose.
- Parallel structure at the document level. Comparable parts share a shape, so the scanner learns the pattern once and navigates instantly.
- Layer your structures (long docs). An inverted-pyramid summary on top for scanners; an OCAR (Opening, Challenge, Action, Resolution) narrative arc beneath for deep readers.
The diagnostic
Reverse outline. Write down the single point of each paragraph, in order, then read the list. It exposes the skeleton instantly: Is the conclusion buried? Do the points flow? Any paragraph without a clear point? Fastest way to find a structural failure.
The cautionary tale
The Challenger engineers were correct and clear—but the one decisive fact (cold degrades the O-rings, untested this cold) was buried and fragmented, never given prominence as the bottom line. Time-pressured decision-makers never assembled it. Being correct is not the job; being received is.
The test to apply before you send anything
If the reader reads only the first line and the headers, will they reach the one conclusion that matters?
If no, you've written it bottom-up. Flip it.
Themes this chapter surfaced: #5 structure-serves-the-reader (central) · #2 audience-is-everything · #6 every-sentence-earns-its-place.
Threshold concept: The reader scans; they do not read.
Back to: Chapter 4 · Exercises · Quiz · Further Reading