Working memory is the cognitive system that holds information actively in mind while you use it. It is not the same as short-term memory — it is more dynamic, involving both storage and manipulation of information. Alan Baddeley and Graham Hitch proposed their influential model of working memory in 1974, identifying a central executive that coordinates attention, a phonological loop that holds verbal and acoustic information, a visuospatial sketchpad that holds visual and spatial information, and (added later) an episodic buffer that integrates information across systems. Understanding these components matters for designers because different interface contexts load different working memory subsystems.
The Psychology
The key architectural insight for UX is that working memory is both limited and specific. The phonological loop handles roughly four chunks of verbal information — which is why reading a phone number and then dialling it from memory is a direct test of its capacity. The visuospatial sketchpad handles spatial layouts and visual information — which is why users can navigate a complex interface without reading every label but struggle to remember a sequence of menu locations across sessions. Interfaces that require users to hold information in one subsystem while executing tasks in another create dual-task interference: a form that requires users to remember information from a previous screen while filling in a new one, for instance, overloads two subsystems simultaneously.
In Product Design
The practical consequences for interface design are direct. Multi-step forms should not require information from earlier steps to be held in memory for later steps — either persist the earlier information visibly or carry it forward automatically. Navigation paths should not require users to hold a route in mind — provide breadcrumbs, progress indicators, or persistent context panels. Table-based tasks should not require users to remember a value from one row while editing another — highlight the relevant row, enable sorting, or provide a comparison mode. Workflows that span sessions should restore context so users are not forced to reconstruct the task state from memory when they return.
How to Apply It
The deeper design principle is: do not ask users to be the interface's memory. Every piece of information a user needs for a task should be available in the interface at the point of the task, not stored in the user's working memory because the design has not provided for it. This seems obvious, but it is violated constantly. Checkout flows that display a cart summary in a sidebar earn their keep — users should not have to remember what they were buying while they enter payment details. Calendar event creation forms that keep the selected date visible during form completion earn their keep for the same reason.
Why It Matters
Working memory failures feel like user errors but are design failures. When users report being confused about what they were supposed to do, forgetting information they entered two steps earlier, or having to go back and re-read instructions, the working memory load your interface imposes is too high for reliable task completion. The test is simple: complete the task yourself without looking at the design as a designer. Track every moment you have to hold something in mind that the interface is not actively showing you. Each of those moments is a working memory dependency that better design could eliminate.
