Design Principles
Knowledge in the World vs. the Head
Good design externalises the knowledge users need to act — it puts it in the world, not in their heads. A product that requires memorisation is a product that requires training.
Where it comes from
It's one of Don Norman's most actionable ideas, from The Design of Everyday Things. Norman distinguished knowledge 'in the head' — what a user must remember or already know — from knowledge 'in the world' — the cues, labels, and constraints that tell them what to do without prior knowledge.
Why it matters for your website
Norman's distinction between knowledge in the world and knowledge in the head is among the most actionable ideas in the book. Knowledge in the head is anything the user must remember or already know to operate a product; knowledge in the world is any cue, label, constraint, or contextual signal that tells them what to do without requiring prior knowledge. The principle is straightforward: the more a design relies on knowledge in the head, the more it excludes first-time users, the more training it demands, and the more cognitive load it imposes on every interaction. Great design minimises what users need to remember by making the environment itself informative. The ideal product is usable on first contact without instruction.
Every reliance on memory is an exclusion. The more a design demands knowledge in the head — remembered codes, learned sequences, prior expertise — the more it shuts out first-time users, the more training it requires, and the more it taxes everyone, every time.
Putting knowledge in the world flips this. A visible label, a sensible default, a constraint that rules out the wrong action — each lets the environment carry the knowledge so the user doesn't have to. The ideal is a product usable on first contact, with no instruction, because everything you need to know is right there in front of you.
Wrong vs right
An interface that expects users to remember codes, commands, or sequences from a previous step or session.
Visible labels, prompts, and options that show the user what to do without requiring recall.
A power-user tool that's only usable once you've memorised its conventions, excluding newcomers.
An interface usable on first contact, with the knowledge needed put into the world, not the head.
Asking users to carry information across screens in their memory.
Surfacing that information where it's needed, so the environment remembers for them.
Understanding Knowledge in the World vs. the Head
Norman distinguished two places the knowledge needed to use something can live: in the head or in the world. Knowledge in the head is whatever the user must remember or already know — a command, a code, a learned sequence. Knowledge in the world is any cue, label, constraint, or signal in the environment that tells them what to do without prior knowledge. Good design shifts the balance firmly toward the world.
The reason is inclusion and load. The more a design leans on knowledge in the head, the more it excludes first-time users, the more training it demands, and the heavier the cognitive load it places on every interaction — because users are constantly retrieving things they had to memorise. Externalising that knowledge removes the barrier and the burden at once.
The aspiration this points to is a product usable on first contact, without instruction. When the environment itself is informative — labels, defaults, constraints, visible options — the user doesn't need to remember anything, because everything required is right there in front of them. It connects to the paradox of the active user, signifiers, recognition over recall, and working memory.
How Kweri checks it
Kweri can flag some reliance on knowledge in the head — for instance interfaces that appear to require remembered codes or commands, or steps that depend on information from an earlier screen that isn't carried forward. What it can't fully assess is how much prior knowledge your particular users bring, which varies by audience. So Kweri surfaces places where the design seems to demand memory or prior expertise rather than putting the knowledge in the world, and prompts you to externalise it, while the real test is whether a genuine first-time user can act without instruction.
FAQ
What is 'knowledge in the world vs in the head'?
It's Don Norman's distinction between knowledge a user must remember or already know (in the head) and cues, labels, and constraints in the environment that tell them what to do (in the world). Good design puts the knowledge in the world.
Why is knowledge in the world better?
Because relying on knowledge in the head excludes first-time users, demands training, and adds cognitive load to every interaction. Putting knowledge in the world — visible labels, defaults, constraints — lets people act without remembering or being taught.
What's an example of knowledge in the head?
Anything users must remember or already know: a command to type, a code from an earlier step, a learned sequence, or conventions only experts know. Each requires recall or prior expertise that newcomers won't have.
How do I put knowledge in the world?
Use visible labels, sensible defaults, constraints that rule out wrong actions, and on-screen options that show what's possible. Make the environment itself informative, so users can act on first contact without instruction or memorisation.
How is this related to recognition over recall?
Closely. Recognition over recall says it's easier to recognise options than to remember them; knowledge in the world is the broader principle of externalising what users would otherwise have to hold in their heads, so recognition replaces recall.
Related principles
Show options and information on screen — don't make users carry them in their head between steps.
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.
Signifiers are the visible cues that tell users where and how an action can be taken.
Attribution & sources
Identified by Don Norman. Catalogued from The Design of Everyday Things (Don Norman).
One of Norman's most actionable ideas; there's no single canonical web source.
See Knowledge in the World vs. the Head 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 →