cognitive psychology
Schema
What is a schema in UX?
A schema is a mental template built from past experience for how a kind of thing usually works - what a login form looks like, how a checkout flows, where the menu lives. We match new situations to these templates, so when an interface fits the schema people understand it instantly, and when it breaks the schema they're forced to stop and work it out.
Also known as: schema, mental schema, schemas
Prefer to watch?
Watch the recap 0:59
The demo
The same login form, twice - all the same parts. One follows the template in your head; the other breaks it. Flip between them and feel how much harder the second one is to use.
What this demo shows (text version)
The same login form is shown two ways. The conventional version matches the template people hold for forms - labels above their fields, username then password, the primary button at the bottom-right - so it's understood at a glance. The schema-breaking version contains all the same parts but rearranges them - labels below the fields, the submit button at the top, the order swapped - so you have to stop and consciously work out what goes where.
That's the power of a schema: a mental template from past experience that makes a matching interface effortless and a violating one slow and error-prone. It's the basis of Jakob's Law - conform to the conventions people already know by default, and break them only where a new pattern is genuinely worth the cost of relearning.
People arrive with ready-made templates for how interfaces behave, and they read yours through those templates. Match the schema - the logo links home, the cart sits top-right, the primary action is a filled button on the right - and people just know what to do without thinking. Break it, even with something "better", and you force conscious effort, hesitation and error, because reality no longer matches the template in their head. So innovate where it adds real value and conform everywhere else: novelty has a comprehension cost, and most of an interface should feel reassuringly familiar.
The conventional version you understood without a thought - because it matched the template already in your head. The scrambled one had all the same parts, yet you had to stop and decode it, because it broke the schema. That's the cost of fighting expectations: meaning that used to be free now takes effort. Conform where it doesn't matter, and spend novelty only where it truly pays.
Schemas are knowledge structures we build from repeated experience and then apply to make sense of new input quickly. When something matches an existing schema, comprehension is near-automatic - we fill in the expected parts without conscious effort. When it violates the schema, we can't run on autopilot and have to process it deliberately, which is slower and more error-prone. This is the cognitive basis for Jakob's Law: people expect your site to work like the others they know.
Interface conventions are shared schemas: a clickable logo returns home, navigation sits at the top or side, a cart icon lives top-right, underlined or coloured text is a link, a filled button is the primary action. Because these are learned across thousands of products, matching them lets people transfer existing knowledge straight to yours, while breaking them - even with a genuinely cleverer idea - forces relearning and invites mistakes.
The design balance is to honour schemas by default and break them only deliberately. Conform on the structural, low-value conventions so the interface feels familiar and effortless, and reserve novelty for places where a new pattern delivers real benefit worth the comprehension cost. When you do break a schema, signal it clearly and help people build the new template, rather than leaving them stranded between expectation and reality.