Bibliography

A unified reading list for Think, Then Write, compiled from the annotated further-reading.md cards at the end of all forty chapters.

This bibliography follows the book's own citation-honesty rule (see the note on tiers in Chapter 11, and the project standard the chapters were written to). Every source here is real and locatable. Nothing has been invented — no fabricated DOIs, no guessed years, no made-up page numbers. Where a standard, manual, or tool is revised on a cycle, we name it by function and tell you to consult the current edition rather than pin a year we can't vouch for.

The list has two tiers:

Tier 1 — Verified. Landmark works, official standards, and primary tool documentation we are confident exist and can point you to directly. Cited normally.
Tier 2 — Attributed. Real, widely-held ideas and bodies of research that the book referenced as ideas rather than pinning to an exact study, page, or year. These are written the way the chapters wrote them — "research on X suggests…" — so you can chase the primary literature yourself without trusting a secondhand statistic.

Within each tier, entries are grouped by topic and alphabetized by author (or by title where there is no single author). A source cited in several chapters appears once, with the chapters that lean on it noted in brackets.

How to use this list. You do not need any of these to read the book; the most important "further reading" is always the document in front of you, read once more as your reader would. But if you want to go deeper on a chapter, find its topic heading below. If you read only a handful of things in your writing life, start with Zinsser's On Writing Well, then Williams's Style, then keep Strunk & White and your field's style manual within reach — the four sources Chapter 39 calls the starter shelf.

Tier 1 — Verified

The craft of clear writing (the spine of the book)

Garner, Bryan A. Garner's Modern English Usage. Oxford University Press. The authoritative modern reference for the disputes a style chapter raises and can't settle: data is vs. data are, which vs. that, comma and semicolon conventions, correlative-pair parallelism, and which "rules" are real versus superstition. Garner's Language-Change Index tells you how accepted a usage currently is, so you can distinguish a genuine error from a contested convention. Consult it by entry, not cover to cover. [Ch. 3, 6]
Pinker, Steven. The Sense of Style: The Thinking Person's Guide to Writing in the 21st Century. Viking, 2014. A cognitive scientist's account of why good writing is good, and the most rigorous popular treatment of the curse of knowledge — why expertise makes you worse at telling whether your prose is clear to others. Excellent on "classic style," on over-formalization, and on when a "rule" (including the passive-voice rule) should be broken. [Ch. 1, 2, 3, 6, 7, 28, 39]
Strunk, William, Jr., and E. B. White. The Elements of Style. Longman/Pearson, 4th ed., 2000 (Strunk's original, 1918). The famous short manual. Rule 17 — "Omit needless words" — is the four-word version of this book's "every sentence must earn its place." Read it as sharp advice rather than law: some of its prohibitions are the superstitions Chapter 6 warns against, and it is lighter on the why than Williams. But its sentence-level discipline is timeless, and it is itself a model of the concision it preaches. [Ch. 1, 3, 4, 6, 8, 11, 12, 13, 19, 21, 23, 24, 25, 27, 28, 29, 33, 34, 36, 39, 40]
Williams, Joseph M. (with Joseph Bizup). Style: Lessons in Clarity and Grace. Longman/Pearson, many editions (originally Style: Toward Clarity and Grace). The single best book on the mechanics of clear prose and the source behind much of this book's diagnostic method. Williams explains why sentences feel clear — the characters-as-subjects, actions-as-verbs principle, and the management of old and new information (cohesion and the given-new contract). If you read one book to deepen Parts I and II, read this. [Ch. 2, 3, 6, 7, 8, 12, 13, 14, 15, 16, 20, 23, 29, 33, 35, 36, 38, 39, 40]
Zinsser, William. On Writing Well. HarperCollins, 30th-anniversary ed., 2006 (first published 1976). The book this textbook borrows its spirit from: clarity, brevity, warmth, and respect for the reader. Zinsser's chapters on simplicity, clutter, and rewriting — including his own marked-up manuscript pages — are the most persuasive case in print that clear writing follows from clear thinking and that the writing is in the rewriting. If you read one book cover to cover alongside this one, make it this. [Ch. 1, 2, 3, 4, 7, 8, 10, 12, 13, 19, 20, 21, 24, 27, 28, 29, 36, 37, 39, 40]

The writing process and revision

Elbow, Peter. Writing Without Teachers. Oxford University Press, 2nd ed., 1998. The origin of freewriting — writing fast and continuously without stopping to edit — and the separation of "generating" from "criticizing" that is the intellectual foundation for splitting drafting from revising. [Ch. 5; see also the Tier 2 note on Elbow's reader-response feedback model]
King, Stephen. On Writing: A Memoir of the Craft. Scribner, 2000. Aimed at fiction, but its revision advice is field-neutral and quotable: the "2nd Draft = 1st Draft − 10%" formula is the diminishing-clutter discipline as arithmetic, and "let it rest in a drawer" is the cold-gap rule scaled up. [Ch. 12; also cited among the "read to write" tradition]
Lamott, Anne. Bird by Bird: Some Instructions on Writing and Life. Anchor Books, 1994/1995. The single best thing written on why your first draft is supposed to be bad. The chapter "Shitty First Drafts" is the permission slip behind this book's drafting advice. [Ch. 5, 12]
Murray, Donald M. "The Maker's Eye: Revising Your Own Manuscripts." Essay, widely anthologized, 1973. A short classic arguing that writers must learn to read their own work as a stranger would — the discipline behind "let it sit for 24 hours." (Exact pagination varies by anthology.) [Ch. 5]
Silvia, Paul J. How to Write a Lot. American Psychological Association. Short, blunt, and aimed at academics who "can't find time to write." Its real subject is the myth that you must wait to feel inspired — a cousin of the transcription model Chapter 1 dismantles. [Ch. 1]

Structure and persuasion

Minto, Barbara. The Pyramid Principle: Logic in Writing and Thinking. Pearson/Financial Times. The classic argument for top-down structure: lead with the answer, then group and order supporting ideas beneath it. The source of the SCQA framing and the most thorough case anywhere for "conclusion first" in professional and business writing. [Ch. 4, 19, 20, 21, 37]

Visuals, data display, and document design

Bringhurst, Robert. The Elements of Typographic Style. Hartley & Marks. The deeper, more literary reference on typography as a discipline in service of the reader (the source of Chapter 10's epigraph, "Typography exists to honor content"). More than most technical writers need; dip into it. [Ch. 10]
Butterick, Matthew. Practical Typography. Free online at practicaltypography.com. A working typographer's no-nonsense guide for ordinary people who write documents — type size, line length (the measure), line spacing, and choosing and limiting typefaces. Opinionated, concise, free. [Ch. 10]
Cairo, Alberto. The Truthful Art: Data, Charts, and Maps for Communication. 2016 (and The Functional Art, 2012). The best modern companion to Tufte and more practical for the working analyst, focused on truthfulness — how charts mislead (truncated and dual axes) and how to be honest with data. [Ch. 9]
Few, Stephen. Show Me the Numbers: Designing Tables and Graphs to Enlighten. 2nd ed., 2012. The deepest practical treatment of tables — when a table beats a graph and how to design both for clarity. Reach for it on value-heavy work (finance, ops, reporting). [Ch. 9]
Knaflic, Cole Nussbaumer. Storytelling with Data: A Data Visualization Guide for Business Professionals. Wiley, 2015 (with the companion workbook Storytelling with Data: Let's Practice!, Wiley, 2019). The most actionable book on turning a chart into a story rather than an exhibit — decluttering, preattentive attributes, and titles and annotations that carry a takeaway. The best bridge to the data memo. [Ch. 9, 27]
Tufte, Edward R. The Visual Display of Quantitative Information. Graphics Press, 2nd ed., 2001 (first ed., 1983). The foundational text on presenting data honestly and clearly — the source of data-ink, the data-ink ratio, and chartjunk. The principle that arrangement and prominence determine whether evidence persuades generalizes from charts to slides to page design. [Ch. 4, 9, 10, 18, 27, 30, 32, 35, 38, 39, 40]
Tufte, Edward R. Envisioning Information. Graphics Press, 1990. Best for small multiples, layering and separation, and the design of dense, information-rich displays. [Ch. 9]
Tufte, Edward R. Visual Explanations: Images and Quantities, Evidence and Narrative. Graphics Press, 1997. Contains Tufte's analysis of the Challenger charts — how an accurate presentation can scatter the decisive temperature-versus-damage relationship out of sight. The data-display reading of the case used across the book. [Ch. 2, 4, 9, 38] (Tufte's separate essay The Cognitive Style of PowerPoint is worth reading as the strongest case against slideware as usually built — see Ch. 30.)
Web Content Accessibility Guidelines (WCAG). W3C. The authoritative source for the accessibility rules the book applies at the chart and document level: text alternatives (alt-text) for non-text content, never conveying information by color alone, minimum contrast ratios (4.5:1 for normal text, 3:1 for large text), and meaningful heading and link structure. Free; consult the current success criteria. [Ch. 9, 10]
Williams, Robin. The Non-Designer's Design Book. Peachpit Press, multiple editions. The best starting point for someone who must design documents but isn't a designer. Its four principles — C.R.A.P.: Contrast, Repetition, Alignment, Proximity — are the practical backbone of the design chapter. [Ch. 10]

Citation, integrity, and the style manuals

The ACS Guide to Scholarly Communication (ACS Style Guide). American Chemical Society. The convention for chemistry and chemistry-adjacent journals; meticulous on journal abbreviations and chemical-literature formatting. [Ch. 11, 39]
AMA Manual of Style. American Medical Association. The house style for much of medicine. [Ch. 39; medical conventions, Ch. 36]
The Chicago Manual of Style. University of Chicago Press, 17th ed., 2017. The standard for the humanities, history, and much of publishing, and the source for both Chicago systems (notes-and-bibliography and author–date). Its discussion of when and why to cite is the deepest treatment of citation-as-craft. Also a general reference you own — the arbiter of the comma, the hyphen, and the thousand small mechanical questions. The free Citation Quick Guide (chicagomanualofstyle.org) is a practical entry point. [Ch. 11, 23, 29, 39]
Council of Writing Program Administrators. "Defining and Avoiding Plagiarism: The WPA Statement on Best Practices." A concise, authoritative statement distinguishing deliberate plagiarism from the misuse-of-sources errors (like patchwriting) that honest writers commit. The best short read on why the gray areas exist. [Ch. 11]
IEEE Reference Guide / IEEE Editorial Style Manual. IEEE, current edition. The authoritative source for the numbered [1] style used across engineering and computer science. When a venue says "IEEE style," this is the rulebook. [Ch. 11, 29, 39]
Mendeley — official documentation. mendeley.com. A reference manager (free basic tier, owned by Elsevier) with strong PDF organization; the workflow mirrors Zotero's. Primary tool documentation. [Ch. 11]
MLA Handbook. Modern Language Association. The humanities citation style most common in the literatures and languages; named among the style authorities a writer should locate for their field. [Ch. 29, 39]
Publication Manual of the American Psychological Association. APA, 7th ed., 2020. The definitive guide to author–date (APA) citation across the social and behavioral sciences and increasingly the life sciences and nursing — and the source of widely-adopted statistical-reporting conventions (italicized statistics, exact lowercase p, no leading zero on bounded quantities, effect sizes and confidence intervals) and bias-free-language guidance. The free companion site is apastyle.apa.org. [Ch. 7, 11, 29, 35, 39]
Zotero — official documentation. zotero.org. Free, open-source, and the most widely recommended reference manager in academia: capture sources with the browser connector, cite while you write, generate reference lists in any style, and attach your own notes. Start here if you've never used a manager. Primary tool documentation. [Ch. 11]

The research paper and the publication process

Booth, Wayne C., Gregory G. Colomb, Joseph M. Williams, et al. The Craft of Research. University of Chicago Press, current edition. The deepest treatment of research as argument and as a conversation: how to move from a topic to a question to a claim, and the "so what?" / "says who?" tests. (Note the shared lineage with Style: Lessons in Clarity and Grace — the same Williams.) [Ch. 14, 15, 16]
COPE — Committee on Publication Ethics. publicationethics.org. The reference body for publication-ethics questions — disputes, corrections, conflicts of interest, misconduct — and the standard legitimate journals follow. Primary guidance. [Ch. 14]
Day, Robert A., and Barbara Gastel. How to Write and Publish a Scientific Paper. Greenwood / Cambridge University Press, multiple editions. The classic, practical, section-by-section manual for the scientific report and paper: what belongs in each IMRaD section, how to write a reproducible Methods section, how the submission-and-review process works, and how to respond to editors and reviewers. The field's most widely assigned guide. [Ch. 13, 14, 35]
The ICMJE Recommendations. International Committee of Medical Journal Editors, "Recommendations for the Conduct, Reporting, Editing, and Publication of Scholarly Work in Medical Journals." Aimed at medicine but influential across the sciences and freely available; the most authoritative short statement on who counts as an author and how peer review should work. [Ch. 14, 35]
Think. Check. Submit. thinkchecksubmit.org. A free, cross-industry checklist for vetting a journal or conference before you submit — built to help researchers avoid predatory venues. Primary resource. [Ch. 14]

The long document, the thesis, and grant proposals

Bolker, Joan. Writing Your Dissertation in Fifteen Minutes a Day. Holt, current edition. The classic on the psychology of the long project: shrink the unit of work below the threshold of dread and write continuously rather than banking it for the end. Short, humane, honest about the emotional reality. [Ch. 16]
NIH — "Write Your Application" / Specific Aims guidance. grants.nih.gov. The agency's own instructions for the research plan (Specific Aims, Significance, Innovation, Approach) — the most authoritative source on the structure Chapter 17 teaches. Read it alongside the specific Funding Opportunity Announcement, which overrides general guidance. [Ch. 17]
NSF — Proposal & Award Policies & Procedures Guide (PAPPG). National Science Foundation. The governing document for NSF proposals, including the Project Summary and the two review criteria, Intellectual Merit and Broader Impacts. Non-optional reading if you write for the NSF. [Ch. 17]

Reporting standards and reproducibility (named resources)

EQUATOR Network. equator-network.org. A clearinghouse and registry of field-specific reporting guidelines for empirical and especially health-and-life-sciences research — the formal extension of "write so someone could replicate it." Browse the guideline that fits your study type before writing up serious empirical work. [Ch. 13, 35]
Robert's Rules of Order. The classic parliamentary-procedure reference. Cited not for procedure but for the principle that formal minutes record what was done (motions, decisions, results), not what was said — the same discipline this book applies to ordinary workplace minutes. [Ch. 21]

Workplace and safety-critical writing

Dekker, Sidney. The Field Guide to Understanding 'Human Error'. The research-grounded case for why blaming individuals fails and why you must examine the system and the conditions that allowed a person to err. Essential for understanding why "X was careless" is a dead end and "the process allowed…" is the only useful framing. [Ch. 21; see also the Tier 2 note on blameless postmortems, Ch. 34]

Instructions, procedures, and developer-facing documentation

Brown, Simon. The C4 Model for Visualising Software Architecture. c4model.com. The discipline that fixes most architecture diagrams: don't draw "the architecture," draw a set of diagrams at increasing zoom — Context, Container, Component, Code. Free, concise, notation-light. [Ch. 32]
The Diátaxis framework (Daniele Procida). diataxis.fr. A free, widely-adopted framework that separates technical documentation into four modes — tutorials (learning-oriented), how-to guides (task-oriented), reference (information-oriented), and explanation (understanding-oriented) — and argues that mixing them is the root cause of bad docs. The cleanest mental model available for what kind of document you're writing. [Ch. 22, 24, 25, 26, 40]
diagrams.net (draw.io). drawio.com / app.diagrams.net. A free, full-featured visual diagram editor; its docs cover keeping diagrams in version control (the embedded-source-in-PNG/SVG trick) and platform integrations. Primary tool documentation. [Ch. 32]
The Google Developer Documentation Style Guide and the Microsoft Writing Style Guide. Written specifically for technical and software documentation and freely available online; the bases many teams adopt before adding a short house layer. [Ch. 3 (E2), 23]
Google's Engineering Practices documentation — the Code Review Developer Guide. google.github.io/eng-practices. The best free resource on the writing of code review, in two halves: "How to do a code review" (the reviewer's guide) and "The CL author's guide" (writing a change and its description so it can be reviewed well). Concrete, battle-tested at scale. [Ch. 34]
Horn, Robert E. Developing Procedures, Policies, and Documentation (the Information Mapping tradition). The structured-documentation approach behind how modern SOPs, work instructions, and policy manuals are laid out — chunking, labeling, and consistent formatting so a reader can find and perform a procedure without reading linearly. [Ch. 22]
Keep a Changelog. keepachangelog.com. The community convention for a human-readable changelog grouped by Added / Changed / Fixed / Deprecated / Removed / Security, written for users rather than as a commit dump. [Ch. 25]
The OpenAPI Specification. openapis.org. The standard machine-readable format for describing REST APIs and the basis for generated reference docs (and "try it" consoles) that can't drift from the code. [Ch. 25]
Nygard, Michael. "Documenting Architecture Decisions," 2011 (blog post), and Release It! Design and Deploy Production-Ready Software. The short post popularized the lightweight Architecture Decision Record and its Context / Decision / Consequences format; Release It! supplies the production mindset behind the kinds of decisions worth an ADR. [Ch. 25, 32]
Redish, Ginny. Letting Go of the Words: Writing Web Content That Works. The definitive treatment of writing for readers who scan, skip, and arrive mid-task — write so any page stands alone, lead with what the reader wants to do, design for information-seeking rather than reading. [Ch. 22]
Semantic Versioning. semver.org. The MAJOR.MINOR.PATCH specification that lets a version number communicate the risk of an upgrade; pairs with Keep a Changelog. [Ch. 25]
Chacon, Scott, and Ben Straub. Pro Git. The official Git book, free online. The reference for the "git for docs" / docs-as-code model — branching, pull requests, and why a semantic merge conflict must be resolved by a human. [Ch. 23]
Write the Docs. writethedocs.org. A global community of documentation practitioners — engineers and technical writers — whose talks, guides, and conference archives are an excellent, continuously updated, free resource on every documentation genre in Part V. [Ch. 24, 25, 26]

Software safety and reliability (named practice)

The Site Reliability Engineering tradition's postmortem practice. The publicly available Site Reliability Engineering material includes a chapter on blameless postmortem culture and example templates: blamelessness, a neutral timeline separated from analysis, system root causes, and action items that change the system. The formalized, large-scale version of the incident report. [Ch. 21, 34]

Presentations and slide design

Alley, Michael. The Craft of Scientific Presentations. Springer. The definitive source for the assertion–evidence approach — slides whose headlines are full-sentence claims and whose bodies are visual evidence, developed and tested for scientific and engineering talks. The companion site is assertion-evidence.com. [Ch. 18, 30, 31]
Duarte, Nancy. slide:ology: The Art and Science of Creating Great Presentations (and Resonate). O'Reilly. A designer's deep, practical treatment of slide craft — visual hierarchy, turning data into clear slide graphics, one idea per slide; Resonate adds the narrative arc behind a memorable talk. [Ch. 30, 31]
Reynolds, Garr. Presentation Zen: Simple Ideas on Presentation Design and Delivery. New Riders. The most influential popular argument for restraint: simplicity, one idea per slide, big visuals, empty space, against the bullet-point deck. The most useful single book for a technical speaker who wants to be clear and not boring. [Ch. 18, 30, 31]
The Mermaid documentation. mermaid.js.org. The reference for the diagrams-as-code format this book uses for figures — flowcharts, sequence, ER, class, and state diagrams, with a browser-based Live Editor. Primary tool documentation. [Ch. 32]

Rhetoric and science communication

Aristotle. Rhetoric. The original treatment of adapting a message to its audience — ethos, pathos, logos — and the root of "audience is everything." The three appeals still explain why composure under a hostile question, a concrete opening, and a clear argument all matter. [Ch. 2, 31]
Olson, Randy. Houston, We Have a Narrative: Why Science Needs Story. University of Chicago Press, 2015. By a scientist-turned-filmmaker: scientists lose audiences because they default to the structure of a study (IMRaD) when they need the structure of a story. The "And, But, Therefore" (ABT) template is the most practical single device in the science-communication literature. [Ch. 28]

Field-specific standards and bodies

CRediT (Contributor Roles Taxonomy). The fourteen-role controlled vocabulary (Conceptualization, Methodology, Investigation, Formal analysis, Writing – original draft, etc.) that a growing number of journals require for author-contribution statements. [Ch. 35]
The GRADE Working Group. The international collaboration behind the GRADE approach (Grading of Recommendations Assessment, Development, and Evaluation) for rating the certainty of evidence separately from the strength of a recommendation — the authoritative source for the certainty-vs-strength distinction in clinical and guideline writing. [Ch. 36]
IEEE and ACM codes of ethics; the Society for Technical Communication (STC) ethical principles. Professional codes describing honesty, accuracy, and responsibility to the public — the formal articulation of duties Chapter 38 argues from first principles. [Ch. 38]
INCOSE (International Council on Systems Engineering) guidance on writing requirements. incose.org. A vendor-neutral professional body publishing a widely-used systems-engineering handbook and well-regarded material on the characteristics of good requirements (necessary, unambiguous, verifiable, traceable). Consult the current edition. [Ch. 33]
PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses). The de facto standard for documenting a systematic review's search-and-screen process, including the flow diagram that makes the review reproducible. Consult the current version and your venue's requirements. [Ch. 15, 35] (Other field-specific reporting guidelines named in the book — CONSORT for clinical trials, ARRIVE for animal research — are catalogued via the EQUATOR Network, above.)
Preprint servers — arXiv, bioRxiv, medRxiv, ChemRxiv. Browse the one for your field and read its posting policy and "what is a preprint" explainer; reading recent preprints is the best way to understand the norm. [Ch. 35]
RFC 2119 — Key Words for Use in RFCs to Indicate Requirement Levels. IETF, S. Bradner, 1997 (Best Current Practice, BCP 14). The short, free, foundational document defining MUST / SHALL / SHOULD / MAY and their negatives. Barely two pages — read the original; you'll use its vocabulary for the rest of your career. Free at the IETF site. [Ch. 33]
RFC 8174 — Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words. IETF, 2017. The one-idea clarification: the special normative meaning applies only when the keywords are in uppercase; lowercase "must" is ordinary English. Free at the IETF site. [Ch. 33]

Public-health and clinical communication

The American Medical Association's guidance on health literacy and clear patient communication. The clinician-facing companion to the CDC's writer-facing materials, including the teach-back technique. [Ch. 36]
The CDC's plain-language and clear-communication guidance. U.S. Centers for Disease Control and Prevention. Widely used materials and toolkits on writing clear, plain-language health information for the public, including checklists and the rationale for recommended reading levels. [Ch. 36]

Law and plain language

The Plain Writing Act of 2010 (U.S. Public Law 111-274) and the Federal Plain Language Guidelines at plainlanguage.gov. Real law requiring U.S. federal agencies to write public documents in plain language, plus free, example-rich guidance (active voice, strong verbs, cutting jargon, leading with what the reader needs). Proof that clarity is treated as a civic and legal obligation, not a stylistic preference. [Ch. 2, 3, 7, 10, 12, 19, 36, 37]
The U.S. Section 508 standards. Require many U.S. federal electronic documents to be accessible (incorporating WCAG). With the Plain Writing Act, they make the point that accessible, clear design is a legal baseline, not extra credit. [Ch. 10]

Public investigations and committee reports (the recurring cases)

Report of the Presidential Commission on the Space Shuttle Challenger Accident (the "Rogers Commission Report"), 1986. The official public investigation and the primary-source record for the Challenger case. Cited for the established facts only — the O-ring seal failure, the cold-temperature contributing factor, and the existence of the pre-launch teleconference. Volume I covers the night-before decision sequence; treat individual recollections as attributed perspective, not settled fact. [Ch. 2, 38]
U.S. House Committee on Transportation and Infrastructure. The Design, Development & Certification of the Boeing 737 MAX (final committee report, 2020), together with the official aircraft-accident investigation reports issued by the relevant national air-safety authorities for Lion Air Flight 610 (2018) and Ethiopian Airlines Flight 302 (2019). The public records behind the 737 MAX discussion; read for the documented, multi-factor account. [Ch. 38]

Tier 2 — Attributed

Real, widely-held ideas and bodies of research the book referenced as ideas rather than pinning to an exact study, page, or year. Where a named author or work below is itself verifiable (e.g., the American Scientist essay, Made to Stick, Burke's Philosophy of Literary Form), it is real — what is "Tier 2" is the claim or finding we attributed without a single page-cited source. Chase the primaries directly rather than trusting a secondhand statistic.

How readers read, attend, and remember

The curse of knowledge. That knowing something makes it hard to model someone who doesn't — and that this systematically makes experts worse at judging their own clarity. The "tappers and listeners" demonstration is widely attributed to Elizabeth Newton's 1990 Stanford dissertation work (tappers vastly overestimated how often listeners would identify a tapped-out tune). The term comes from economics and cognitive science. Chip Heath and Dan Heath's Made to Stick: Why Some Ideas Survive and Others Die (Random House, 2007) popularized the study and is an accessible entry point. We cite the idea as widely attributed; consult the originals for exact figures. [Ch. 1, 2, 3, 6, 22, 26, 27, 28, 31]
The explanation / self-explanation effect (and "learning by teaching"). That explaining material in your own words — to yourself or others — improves understanding more than rereading. Well established in the learning-sciences literature on self-explanation and the "protégé effect"; the rubber-duck-debugging folklore is the programmer's everyday encounter with it. Search the cognitive-science literature directly rather than trusting a secondhand statistic. [Ch. 1]
Reading behavior and the F-pattern. That on-screen readers scan in a rough "F" shape, favoring the top and the left. Associated with usability research, notably the Nielsen Norman Group's eye-tracking studies; widely replicated. The pattern, not a single experiment, is the point. [Ch. 4]
Information foraging theory. Models readers as foragers hunting "information scent," explaining why informative headers and strong topic sentences work. Originating with Pirolli and Card at Xerox PARC. [Ch. 4, 19]
Cognitive load and multimedia learning (the redundancy and modality effects). Why a text-dense slide narrated aloud fails: working memory has limited capacity, and identical on-screen text and spoken narration compete for the same channel. The territory of cognitive-load theory (associated with John Sweller) and multimedia-learning principles (associated with Richard Mayer). Real, robustly attributed findings; cite the ideas, not invented figures. [Ch. 18, 30]
The information-gap theory of curiosity (the "curiosity gap"). That curiosity is driven by a perceived gap between what we know and what we want to know — the mechanism under a good hook. Most associated with the economist George Loewenstein's work in the 1990s. [Ch. 28]

Sentence, paragraph, and document craft

Gopen, George D., and Judith A. Swan. "The Science of Scientific Writing," American Scientist, 1990. A widely-assigned essay arguing that readers attach meaning based on where information sits — they read the topic position (start of a sentence) as what it's "about" and look for the point in the stress position (the end) — and that scientific prose fails when authors violate these expectations. The "reader-expectation" approach behind topic sentences, signposting, and the given-new logic. The essay is real and widely attributed; we cite it by title and venue without claiming a page reference. [Ch. 4, 8, 20]
The passive-voice consensus among usage authorities. That respected style authorities do not ban the passive; they advise using it deliberately and warn that overzealous passive-avoidance produces its own bad writing. A broadly attributed consensus across usage guides (the specific guides — Garner, Pinker — are Tier 1). [Ch. 3]
The "process movement" in composition studies. The shift, from the 1970s on, from the finished product to the process that creates it — treating planning, drafting, and revising as recursive rather than linear. A real body of scholarship summarized in any current composition handbook. [Ch. 5]
Hedging and epistemic modality in academic writing. That scientific genres hedge heavily while popular genres strip hedges out, and that hedging norms vary by field and language. A well-established area of applied linguistics, much of it associated with Ken Hyland's work on academic discourse and metadiscourse (his books are the Tier 1 entry point). [Ch. 7]
Inclusive-language guidance. That preferred usage genuinely shifts and communities differ (person-first vs. identity-first), so current style-guide editions and community sources beat any dated list. Practical references include the Conscious Style Guide (an aggregator of community-sourced guidance), the APA Publication Manual's bias-free-language chapter, and major tech organizations' published inclusive-language guides (the named manuals are Tier 1). [Ch. 7]
"Read to write." That writers improve by reading closely and analytically — a near-universal theme among working writers and teachers (Zinsser; King's On Writing; Francine Prose's Reading Like a Writer, among many). A widely-held, much-attributed idea rather than a single empirical claim. [Ch. 39]

Structure, argument, and the scholarly conversation

Burke, Kenneth. The Philosophy of Literary Form — the "unending conversation" / "parlor" metaphor (Chapter 14's epigraph). The image that organizes academic writing: you arrive at a conversation already in progress, listen, then put in your oar. The passage is famous and real; read it in Burke for the primary text. [Ch. 14]
The inverted pyramid (journalism), the lede, and the nut graf. Century-old newsroom conventions — put the most important information first; "don't bury the lede"; the nutshell paragraph that orients the reader after the opening. Real, pervasive craft taught in every journalism program, with no single citable origin. [Ch. 4, 20, 28]
BLUF (Bottom Line Up Front). A documented, taught convention in U.S. military and federal writing (and the broader plain-language movement): state the conclusion or request first, support it after. Real and pervasive; treated as an attributed convention rather than the work of a single author. [Ch. 19, 21, 27, 28]
The IMRaD convention. That science converged on the four-part Introduction–Methods–Results–Discussion structure over the twentieth century, and that it persists because it tracks the order a skeptical reader must evaluate evidence. Well documented across the scientific-writing literature (Day and Gastel give the most accessible account). [Ch. 13]
The systematic-review and evidence-synthesis literature. The distinction between narrative, systematic, and scoping reviews, and the defining ideas of a predefined reproducible search protocol, explicit inclusion/exclusion criteria, and transparent reporting. A large, real methodological literature across medicine, the social sciences, and software engineering. [Ch. 15]
The grant-writing literature. A genre of scientific grant-writing guides (associated with figures such as Robert Porter, John Robertson, Liane Reif-Lehrer, and the workshop tradition associated with Morgan Giddings on the "story" of the Specific Aims page) that converge on the same lessons — the aims page is paramount, aims are objectives not activities, significance must be specific. Treat their advice as craft wisdom; verify any agency-specific rule against the current official source. [Ch. 17]
Research on how reviewers read and score proposals. The recurring finding — that scores are noisier and reviewer attention scarcer than applicants assume. The direction is robust and well-attributed; no single statistic governs every panel. [Ch. 17]

Workplace, business, and persuasion ideas

The "executive summary stands alone" principle and features-versus-benefits. Staples of business-communication and MBA, sales, and marketing pedagogy: the summary must let a reader decide without reading the body; sell the outcome, not the specification. Widely taught; attributed rather than pinned to a single originator. [Ch. 20]
Root-cause analysis traditions — "5 Whys" and related techniques. A family of methods for pushing past an incident's surface trigger to its underlying cause, with the well-noted caution that real incidents usually have several contributing causes, not one neat root. [Ch. 21]
Project-management status reporting and RAG indicators. That standard PM bodies of knowledge treat status reporting, RAG/traffic-light health indicators, and decision logs as core practice. Consult a major PM guide's communications-management sections. [Ch. 21]
Governance and board-writing practice. That professional governance and nonprofit-board resources teach board packets, the consent agenda, and writing for directors at strategic altitude, separating decisions from information. The durable principles are real; a specific board's conventions you learn locally. [Ch. 37]
Think-tank and government policy-brief guidance. That many universities, institutes, and policy organizations publish practical guides to the policy brief (one-page format, recommendations first, options with trade-offs). Real and easy to find; named honestly without inventing a specific guide's title or year. [Ch. 37]
The "single-threaded owner" / DRI idea. That one named person must be accountable for an outcome, because a thing owned by everyone is owned by no one. Widely attributed to how large technology organizations structure ownership; the label varies. [Ch. 23]
RACI. The Responsible / Accountable / Consulted / Informed matrix, a standard project-management tool for separating who does the work, who owns the outcome, who advises, and who is told. [Ch. 23]

Software, instructions, and developer culture

John Carroll's minimalist-documentation research (e.g., The Nurnberg Funnel / the "minimal manual"). The body of work showing that adults learning by doing skip most documentation, want to act immediately, and learn best from short, task-focused, error-tolerant instructions — and that supporting error recovery matters as much as the happy path. Widely cited across technical communication and HCI. [Ch. 22, 26]
Usability testing of documentation (associated with Jakob Nielsen and the broader usability tradition). The often-cited rule of thumb that even a handful of test users surfaces the large majority of usability problems — the empirical case for "test on someone who has never done this." Nielsen Norman Group's free writing is a practical start. [Ch. 22]
The social dynamics of code review. The widely-shared engineering-blog and conference argument that the tone and framing of review comments shape team health as much as the technical content — "critique the code, not the coder." No single canonical text; the durable part is separating the artifact from the person. [Ch. 34]
"Human error" and systems thinking in safety-critical fields ("just culture"). That "human error" is a starting point for investigation, not a conclusion, and that resilient systems are designed assuming people will err — from decades of human-factors and safety research (aviation, medicine, industrial operations) that the software postmortem tradition borrowed from. [Ch. 21, 34]
The agile / user-story tradition. The "As a… I want… so that…" template and the Given-When-Then structure for acceptance criteria — widely-used conventions attributed across the agile community rather than to a single source. The durable function is forcing the who/what/why and making "done" a testable contract. [Ch. 34]
Docs-as-code and developer experience. The widely-shared movement that documentation should live in the repo, be version-controlled with the code, reviewed in pull requests, and tested in CI. No single canonical text; attributed across the Write the Docs community and many engineering blogs. [Ch. 25]
"Code is read far more often than it is written." A maxim long current in software engineering (frequently associated with guidance around Python's design). The exact origin is diffuse; the underlying claim — optimize code and its documentation for readers — is the point. [Ch. 24]
"Documentation is a love letter you write to your future self." A line widely circulated in programming communities, often attributed to Damian Conway. Attributed, not precisely sourced; the sentiment is the reusable part. [Ch. 24]
The "plausible, not true" framing of language models. The understanding, widely held among practitioners and researchers, that LLMs predict likely text rather than retrieve verified facts. The specific technical literature changes fast; the durable idea is the part you need. [Ch. 29]
Documented real-world AI failures (e.g., sanctioned legal filings citing fabricated cases). Several widely-reported instances of professionals submitting AI-hallucinated citations and facing consequences. Real and instructive; search for current cases rather than relying on a fixed list. [Ch. 29]
Patchwriting (the concept and its diagnosis). That writers patchwrite — copy a source and swap a few words — when engaging with material they don't yet fully understand. From Rebecca Moore Howard's work in composition studies. Real and well-established; read Howard directly for the primary source. [Ch. 11]

Presentation, persuasion, and performance

The 10/20/30 rule. Guy Kawasaki's memorable heuristic — about 10 slides, no more than 20 minutes, no font smaller than 30 point. A rule of thumb aimed at pitches; the spirit (few points, tight time, big type) matters more than the precise count. [Ch. 30]
Cognitive reappraisal of anxiety as excitement. A real, widely-discussed line of psychology research suggesting that relabeling pre-performance anxiety as excitement improves performance, because the two arousal states feel similar and reinterpreting arousal is easier than suppressing it. Associated with research by Alison Wood Brooks and others. A technique to try, not an iron law; not tied to a specific cited effect size. [Ch. 18, 31]
Gallo, Carmine. Talk Like TED: The 9 Public-Speaking Secrets of the World's Top Minds. A popular, accessible distillation of what makes widely-watched talks work — strong openings, story, brevity. A real book that synthesizes patterns and attributed research rather than presenting primary studies; treat its claims accordingly. [Ch. 31]
The broad public-speaking tradition (from classical rhetoric through Dale Carnegie's Public Speaking writings to modern coaching). The craft converges on a stable core: know your audience, rehearse hard, open strong, tell a story, use less text, manage nerves rather than eliminate them. [Ch. 31]

Research on disclosure and trust

Disclosure and trust. That acknowledging the limitations of one's own evidence tends to increase a reader's trust rather than decrease it. Widely reported across communication and decision research; the principle is solid — resist citing a single study as if it settled it. [Ch. 38]

Ethics of technical communication, and medical-safety evidence

The ethics of technical and professional communication. An established subfield in technical-communication journals and textbooks, recurring on accuracy, the limits of "I just wrote it," responsibility to the end user, and the line between persuasion and manipulation — the source of the duty-of-care and "reasonable reader" vocabulary. [Ch. 38]
The patient-safety literature on medication errors. Decades of work (associated with national patient-safety bodies and institutes of medicine/health) documenting that ambiguous abbreviations, unclear dose expressions (e.g., trailing zeros), and poorly designed labels and instructions contribute to medication errors. A well-established body of findings rather than a single paper; look for "do not use" abbreviation lists and plain-language labeling guidance from recognized safety organizations. [Ch. 36, 38]
Teach-back resources from patient-safety and health-literacy organizations. Free toolkits dedicated to the teach-back method — why it works, how to phrase it without shaming the patient, how to train teams. Widely-attributed, freely available practitioner guidance. [Ch. 36]

Expertise and practice

Deliberate practice. That skill grows through focused, feedback-driven repetition on the edge of one's ability, not raw volume. Associated with the psychologist K. Anders Ericsson and colleagues, and popularized — with distortions — as the "10,000-hour rule." The principle is real and widely cited; the exact hours and the popular gloss are contested. We cite the idea, not a number. [Ch. 39, 40]
"Show, don't tell." A maxim long taught across writing disciplines — an assertion the reader can verify beats one they must trust. The spine of the portfolio's growth narrative. [Ch. 40]

Documentation and writing portfolios

Documentation-portfolio and "writing samples" guidance from technical-writing and developer-relations communities. The consistently recommended emphasis on range plus revision evidence over volume. Practitioner wisdom, not formal research. [Ch. 40]

Practical UML

"Just enough UML" and crow's-foot (entity–relationship) notation. UML is a large formal notation maintained by the Object Management Group; the practical wisdom — captured in books like Martin Fowler's UML Distilled — is to borrow its vocabulary (class, sequence, state diagrams) while skipping its ceremony. Crow's-foot cardinality notation ("one," "zero-or-many," "one-or-many") is a widely-attributed convention from early data-modeling work, covered by any reputable database-design text. [Ch. 32]

A closing note on honesty, fitting for a bibliography in a book about clear communication. Every entry above is real and locatable, and where a claim is widely attributed but not pinned to an exact study, it is marked Tier 2 and phrased as such — the same discipline (Chapter 11) the book practiced throughout. The book deliberately did not compile a list of "best technical-writing textbooks" or chase fast-moving AI-capability citations, because the durable sources are the craft classics, the official standards, and the primary tool docs. When you read writing advice elsewhere, apply the book's own test: does the claim name a real source you could find, or does it just assert authority? And remember that for any specific document you write, the most authoritative source is always the one closest to you — your target venue's instructions for authors, your assignment's rubric, your organization's style guide, or your institution's policy. When those speak, they overrule every general work on this list.

Back to: Answers to Selected Exercises