Context cardTransitional topic
Cognitive psychology in technical communication: theory, application and the bridges between them
What is the difference between cognitive psychology as theory and its application in documentation, and how do the two fit together?
The short answer
Cognitive psychology as theory describes how people perceive, attend, remember, understand, decide and err; it is descriptive and judged by evidence. Applied cognitive psychology for information use is prescriptive: it turns those findings into design principles, practices and evaluation methods for documentation. The bridges are the explicit arguments that lead from one finding to one practice, together with their limits.
For: Technical writers, information designers and documentation managers who use psychological arguments in their work
Key points
- Theory is descriptive: models and findings about perception, attention, memory, comprehension, cognitive load, judgment and error, each with its evidence and its limits.
- Application is prescriptive: principles such as plain language, progressive disclosure, integrated figures or checklists, and methods such as think-aloud tests and cognitive walkthroughs.
- A bridge follows one finding into one practice and states what the finding supports and what it does not.
- Popular claims such as learning styles, a fixed "7 ± 2" rule or "people don't read" are myths or distortions and are flagged as such.
- No cognitive argument replaces the risk assessment or legally required safety information, and none makes a document compliant.
The context
Two bodies of knowledge
Technical writers often justify their decisions with psychology: steps are short "because of working memory", warnings stand before the step "because of attention". These justifications mix two different kinds of knowledge.
Theory is cognitive psychology as a research field. It describes how the mind takes in and uses information: selective attention and inattentional blindness, working memory and chunking, long-term memory and schemas, situation models in reading, cognitive load, heuristics, situation awareness and the types of human error. Its statements are descriptive and are judged by experiments and replication. They come with conditions: who was tested, with which material, under which load.
Application is what documentation does because of that theory. It is prescriptive: plain language, information scent and wayfinding, progressive disclosure, worked examples, integrated figures, job aids and checklists, warning design, and evaluation methods such as think-aloud protocols, cognitive walkthroughs, symbol comprehension tests and usability testing. Each practice rests on one or more findings, and many also rest on standards, law and craft experience.
On this site, the two are kept apart on purpose: a theory glossary (Cognitive psychology for technical communication, in The art of thinking) and an application glossary (Applied cognitive psychology for information use, in the Glossary & Norms Space). Their terms are published step by step.
The bridges
A bridge is a transitional context card that follows one finding from theory into practice and names its limits. Five bridges start from this card:
- Working memory and procedure steps: why "seven plus or minus two" is the wrong rule for steps.
- Mental models and concept information: from the mental model and the system image to concept information placed before tasks.
- Attention and warning placement: from selective attention and habituation to where a warning message goes.
- Cognitive load and split attention: from cognitive load theory to integrating figures, labels and text.
- Human error types and troubleshooting: from slips, lapses and mistakes to recovery information.
The encyclopedia topic Cognitive psychology in technical communication describes the research areas in a neutral style; the blueprint Cognitive psychology for technical communication arranges them as the reader's stack, from noticing to recovering, as a companion to the writer's stack in Thinking models for technical writers.
How to read a cognitive argument
A sound argument names the finding and its source, the conditions under which it was found, the practice it supports and the evidence that the practice works for these readers. Myths skip these steps. There is no good evidence that matching instruction to "learning styles" improves learning (Pashler and colleagues, 2008). Miller's "seven plus or minus two" is not a rule for list length. "People don't read" overstates findings about scanning: readers do read when the text answers their question.
Limits
Cognitive findings explain why a document is easier or harder to use; they do not decide what it must contain. The content of safety information follows from the risk assessment and the applicable law, and the usability of safety information is checked with real users, not inferred from a model. No cognitive argument replaces the risk assessment or legally required safety information, and applying a principle never makes a document or product compliant.
Questions readers ask next
- Is cognitive psychology the same as usability?
- No. Cognitive psychology is a research field that describes how the mind works. Usability is a quality of a product or document in use, checked with users; it draws on cognitive psychology but also on ergonomics, design practice and testing.
- Why separate theory and application into two glossaries?
- Because their statements are of different kinds. A finding says what was observed under which conditions; a practice says what to do. Keeping them apart makes it visible which practice rests on which finding and where the evidence ends.
- Can a cognitive principle justify leaving out a warning?
- No. What safety information a document must contain follows from the risk assessment and the applicable law. Cognitive findings can improve how that information is placed and worded, never whether it is given.
Sources
- Ulric Neisser (1967), Cognitive Psychology — Appleton-Century-Crofts, 5 October 2026
- Christopher D. Wickens, Justin G. Hollands, Simon Banbury and Raja Parasuraman, Engineering Psychology and Human Performance — Routledge, 5 October 2026
- Harold Pashler, Mark McDaniel, Doug Rohrer and Robert Bjork (2008), Learning styles: Concepts and evidence — Psychological Science in the Public Interest, 5 October 2026
- Nelson Cowan (2001), The magical number 4 in short-term memory: A reconsideration of mental storage capacity — Behavioral and Brain Sciences, 5 October 2026
- ISO 24495-1:2023 Plain language — Part 1: Governing principles and guidelines — ISO, 5 October 2026
Review log and changes
Every context card is checked against its sources before it is published, and again whenever it changes; the date under the byline is the last review. Corrections (something was wrong) and additions (something was missing) are logged below with date and time (Berlin time). Typos, formatting and link fixes are not listed.
Reviewed
No corrections or additions since publication.