Laws of UX
Working Memory
The brain's temporary active store holds only 4–7 chunks for 20–30 seconds — information users have to remember across steps will be forgotten unless the system carries it for them.
Where it comes from
Working memory is the cognitive system that holds and manipulates information for the few seconds you're actively using it. The influential model by Alan Baddeley and Graham Hitch in 1974 described it as a limited, short-lived workspace — distinct from long-term memory — and decades of research have confirmed how quickly its contents fade.
Why it matters for your website
Working memory is the brain's scratch pad: active, limited (4–7 chunks), and temporary (20–30 seconds before content fades). Any design that asks users to hold information in their heads across steps, pages, or modals is fighting this constraint rather than working with it. The design rule is direct: put the burden of memory on the system, not the user. Carry context forward, echo back what was entered, show the running total, display the selection throughout the comparison. Every step that requires users to "just remember" something is a step where some users will fail.
Anything you ask a user to carry in their head between steps is at risk. A code shown on one screen and needed on the next, a total they have to remember while choosing options, a setting they must recall across a flow — each is a small bet that the user won't forget, and some always do. The fix is to stop betting: have the system hold the information instead.
This is why echoing matters so much. Showing the running total, repeating the entered email on the confirm step, keeping the selected item visible through a comparison — each one moves the memory burden off the user and onto the interface, where it can't be lost.
Wrong vs right
A verification code shown on one screen, then a code-entry field on the next with the code no longer visible, forcing the user to memorise it.
The code carried forward automatically, or kept on screen, so the user never has to hold it in mind.
A checkout that hides the order summary while the user fills in payment, making them remember what they're buying and for how much.
A persistent order summary that stays visible throughout, so nothing has to be held in memory.
A comparison flow that drops the items you've selected as you move between steps, forcing recall.
Selections echoed back at every step, so the context travels with the user.
Understanding Working Memory
Working memory is the brain's temporary workspace: the small, short-lived store that holds the information you're actively thinking about right now. It's sharply limited — on modern estimates, around four chunks at once — and it's fleeting, with contents fading in seconds unless actively maintained. Every design that asks users to remember something across steps is leaning on this fragile system.
The design rule that follows is blunt: put the burden of memory on the system, not the user. Whatever a person needs to know at a given step should be present at that step — carried forward, echoed back, kept on screen — rather than held in their head from somewhere earlier. Running totals, persistent summaries, repeated confirmations, and pre-filled context are all ways of doing the remembering for the user.
The failure mode is quiet but real: any step that depends on the user 'just remembering' something is a step where some proportion of users will fail, get it wrong, or give up. Designing with working memory in mind means never making a user hold information they shouldn't have to. It sits at the heart of a cluster including Miller's Law, chunking, recognition over recall, and cognitive load.
How Kweri checks it
Kweri can detect some concrete patterns that strain working memory — for instance flows where information shown on one step appears to be needed, but not carried, on a later one, or checkouts that hide the order summary during entry. But fully assessing memory burden often means walking a multi-step flow and tracking what the user must retain, which can exceed a static review. So Kweri flags likely instances where the interface asks users to remember rather than carrying the information for them, and prompts you to verify the full flow.
FAQ
What is working memory?
Working memory is the brain's temporary, active store for the information you're using right now. It's limited — around four to seven chunks — and short-lived, fading within roughly 20–30 seconds unless actively maintained.
How does working memory affect UX design?
It means users can't reliably hold information in their heads across steps. Any design that requires remembering a value, code, or selection from an earlier screen will cause errors and drop-off. The system should carry that information instead.
How do I design around working-memory limits?
Put the burden of memory on the system: carry context forward, echo back what users entered, keep running totals and selections visible, and pre-fill what you already know. Never make users remember something the interface could show them.
What's the difference between working memory and long-term memory?
Working memory is a small, temporary workspace for active thought, lasting seconds. Long-term memory is the durable store of knowledge and experience. Design should avoid overloading the limited working memory rather than relying on users to retain things.
How is working memory related to recognition over recall?
Closely. Because working memory is limited, interfaces should let users recognise options rather than recall them from memory — showing choices, context, and prior input instead of expecting users to remember them.
Related principles
Working memory holds only a handful of items — chunk information to ease the load.
The brain has a limited processing budget — demand too much and performance collapses.
Show options and information on screen — don't make users carry them in their head between steps.
Breaking information into small, meaningful groups makes it faster to scan, understand, and remember.
Attribution & sources
Identified by Alan Baddeley and Graham Hitch (1974). Catalogued from Laws of UX (Jon Yablonski).
Grounded in Baddeley and Hitch's model of working memory; popularised for designers by Jon Yablonski's Laws of UX.
See Working Memory on your own site
Run a free Kweri audit — a plain-English review of your site’s speed, accessibility, SEO and design, ranked by what to fix first. No login, no jargon.
Run a free audit →