Further Reading — Chapter 22: Instructions and Procedures

Annotated, Tier 1 (verified, landmark) and Tier 2 (real, widely-attributed) sources only. Start with whichever matches what you write most.

Tier 1 — Verified, foundational

The Diátaxis framework (Daniele Procida) — diataxis.fr. A free, widely-adopted framework that separates technical documentation into four modes: tutorials, how-to guides, reference, and explanation—and argues that mixing them is the root cause of bad docs. The "how-to guide" mode is precisely the procedural writing this chapter teaches. Read this before Chapter 26, which builds on it; for now, note that an instruction set is a how-to (task-oriented, assumes some competence), distinct from a tutorial (learning-oriented, guarantees success). The cleanest mental model available for what kind of procedure you're writing.

Robert E. Horn, Developing Procedures, Policies, and Documentation / Information Mapping. The structured-documentation tradition behind much of 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. The intellectual ancestor of the "structure for the skipping reader" principle in §22.5.

ANSI Z535 standards (and the related ISO/IEC safety-symbol and signal-word conventions). The formal basis for the Danger / Warning / Caution / Notice hierarchy and the placement of safety messages in product documentation (§22.3). You don't need to buy the standard to follow the principle, but knowing it exists explains why signal words are not interchangeable and why hazard warnings have a defined, regulated form in consumer and industrial products.

Ginny Redish, Letting Go of the Words: Writing Web Content That Works. The definitive treatment of writing for readers who scan, skip, and arrive mid-task from a search engine—exactly the non-linear reader of §22.5. Though framed around web content, its lessons (write so any page stands alone, lead with what the reader wants to do, design for "information-seeking" not reading) apply directly to help articles, online procedures, and how-to content.

Tier 2 — Real, widely-attributed ideas

John M. Carroll, the "minimalist documentation" research (e.g., The Nurnberg Funnel). The body of work behind the idea that adults learning by doing skip most documentation, want to start acting immediately, and learn best from short, task-focused, error-tolerant instructions—plus the finding that supporting error recovery (the troubleshooting mindset) matters as much as the happy path. The empirical grounding for "get the reader doing fast" (§22.9, Going Deeper). Widely cited across technical-communication and HCI; look for summaries if the originals are hard to find.

The "curse of knowledge" (popularized by Chip & Dan Heath, Made to Stick; rooted in cognitive-psychology research on expert blind spots). The reason you cannot judge your own instructions: once you know something, you struggle to imagine not knowing it, so the steps you perform automatically become invisible to you (§22.8). The single most important concept for understanding why the beginner test works. (See also Chapter 2, where this idea is introduced for audience analysis.)

Usability testing of documentation (Jakob Nielsen and the broader usability tradition). The practice and 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," and why you don't need a big study to find most defects. Nielsen Norman Group's freely available writing on usability testing is a practical starting point; the principle transfers cleanly from interfaces to instructions.

How to use these: If you write software docs or READMEs, start with Diátaxis and Redish (and carry them into Chapters 25–26). If you write SOPs, work instructions, or safety-critical procedures, start with Information Mapping and the ANSI Z535 conventions. If you take one idea away, make it the curse of knowledge and its only cure—testing on a real beginner. Everything else in this chapter is mechanics; that is the discipline that actually makes your instructions work.