Key Takeaways — Chapter 28: Blog Posts, Articles, and Science Communication
The summary card. Read this to re-ground before the next chapter or before writing for a general audience.
The one idea
The general reader is unobligated—they can leave at any second, at no cost, and owe you nothing—so you have to earn attention sentence by sentence instead of assuming it. Every other reader in this book has a reason to push through imperfect writing (a paycheck, a grade, a problem to solve). This one doesn't. That single fact is the chapter: it's why the hook can't wait, why the jargon budget is so tight, and why you lead with a story instead of a study.
🚪 Threshold concept: An analogy is a loan, not a gift. It borrows the reader's existing understanding to explain something new, and like any loan it comes due—every analogy is wrong somewhere, and the reader will spend it further than you intended. The break is the interest. You don't avoid the loan (it's your most powerful tool); you manage it—take only what the point needs, and disclose the cost before the reader trips over it.
The tools (in order of use)
| Tool | The move | Section |
|---|---|---|
| The analogy | Map a familiar source the reader owns onto your unfamiliar target, so they understand the idea before learning its vocabulary. | §28.2 |
| Finding the break | Every analogy diverges from the target somewhere. List the divergences; if one sits on your point, flag it or change sources. | §28.3 |
| The jargon budget | Two or three technical terms per article, max. Enforce it mechanically—circle every term, count, cut—because fluency makes your jargon invisible to you. | §28.3 |
| The hook | Open a curiosity gap in the first two sentences—a scene, a surprising fact, a question, or the stakes. Never announce the topic. | §28.4 |
| Narrative structure | Hook → journey → payoff. Narrate the rigor; don't front-load it. IMRaD serves a specialist and loses everyone else. | §28.5 |
| Honest SEO | A searchable-and-compelling title, a meta description under 155 chars, descriptive headers, an FAQ. The same choices this book makes. | §28.7 |
| The pitch | A short email that opens with the hook itself, names a specific angle that fits that publication, and makes a clean dated ask. | §28.8 |
Three things that trip people up
- Dumbing down is not translating. Cutting the real idea or condescending is the cardinal sin—readers punish it instantly. A general reader is less specialized, not less intelligent. Keep the idea; change the vocabulary and frame. If your "simple" version lost the thing that was interesting or true, you gutted it.
- A vivid analogy you love is the one most likely to mislead. You'll ride it past its edge without noticing. The break—not the comparison—is where the skill lives. Know where your analogy stops being true, and whether that edge sits on your point.
- You can't count your own jargon by feel. The curse of knowledge (Chapter 2) makes your field's vocabulary read as plain to you, so the walls are invisible. Circle every term in a near-final draft and count. Most writers find five or six where they thought they used one.
If you remember three things
- Earn the reader, don't assume them—open a curiosity gap fast, because the unobligated reader leaves the instant they're bored.
- The analogy is your most powerful tool, and finding where it breaks is your most important skill—borrow the reader's understanding, then disclose the cost.
- Translate, don't dumb down—keep the real idea, spend two or three jargon terms, and deliver it as a story. The finding stays the same; only the audience moved.