Task analysis is the method of breaking a process into steps the reader can follow, ordered by what the reader needs to do — not by how the writer learned the process or how the system works internally.
In technical writing, task analysis produces the structure of procedural content: numbered steps, prerequisites, decision points, and outcomes. Linda Flower described the failure to perform task analysis as writer-based prose — text organized around the writer’s discovery process rather than the reader’s need [@flowerhayes1981]. A developer who documents a feature by explaining its architecture is writing for themselves; a task analysis asks what the user is trying to accomplish and structures the documentation around that.
Task analysis draws on audience analysis (what does the reader already know?) and cognitive load theory (how much can the reader hold in working memory at each step?). John Sweller’s research showed that each step in a procedure competes for working memory — steps that combine multiple actions or introduce multiple concepts increase extraneous load [@sweller1988].
The vault’s plain language specification operationalizes task analysis through several rules: “order information by reader need” (section 5.2), “one purpose per section” (section 5.3), and the task test (section 12.3), which verifies that readers can actually complete the procedure using the document.
Related terms
- writer-based prose — task analysis is the antidote to writer-based organization of procedural content
- audience — task analysis requires knowing what the reader is trying to do
- cognitive load — task analysis manages cognitive load by sequencing information appropriately
- document design — headings, numbered lists, and progressive disclosure support task-structured content