A mental model is the internal representation a person holds of how something works, built from prior experience and used to predict what will happen when they act. Users approach every interface with a mental model already formed from other products, and they interpret what they see through it. When the model matches the system, the interface feels intuitive; when it does not, the same interface feels confusing regardless of how well designed it is by any internal standard.
The gap between a user's mental model and the system's actual model is where most usability problems originate. Organizations naturally build interfaces that reflect their internal structure: their database schema, their departmental boundaries, their product taxonomy, their operational processes. Customers have no knowledge of any of that and organize the same domain around their own goals. A site structured by business unit, a form organized by which system consumes each field, or a navigation labelled with internal product names all reflect the organization's model rather than the customer's, and each one requires the visitor to learn the organization before they can use the site.
Terminology is the most visible symptom. Every organization develops internal vocabulary for its offerings, and that vocabulary leaks into customer-facing interfaces where it is meaningless. Customers search for what they call the thing, not what the company calls it, and the mismatch shows up simultaneously in site search queries returning nothing, in navigation that nobody clicks, and in support contacts asking questions the site already answers under a name nobody recognizes.
Mental models also govern expectations about consequences, which matters more than terminology in transactional flows. What does saving mean, and is anything published. Does adding to a cart reserve stock. Does cancelling stop billing immediately or at the period end. Is a submitted form final or editable. Where the system's behavior differs from the assumed behavior, the result is not confusion but a specific, avoidable error, and errors of this kind generate the majority of support contacts in most self-service products.
Uncovering mental models requires methods that ask people to externalize their thinking rather than react to a design. Card sorting reveals how people group concepts. Interviews and contextual inquiry reveal the vocabulary and the assumed sequence of steps. Asking participants to predict what will happen before they click, then observing the mismatch, exposes expectation gaps efficiently. Analysis of site search terms and support enquiries provides the same evidence at scale and at no incremental cost.
Mental models also explain why partial consistency is worse than either full consistency or clear difference. When two parts of a product behave almost the same way but differ in one respect, users apply the model they built in the first area and are surprised by the exception, which produces errors more reliably than an interface that is obviously different and therefore approached carefully. This is common in organizations where sections of a site were built at different times or by different teams: navigation that mostly works the same way, forms that mostly validate identically, and terminology that is mostly consistent create a false sense of predictability. Auditing for near-consistency, rather than only for obvious inconsistency, tends to find the defects that generate the most support contacts.
The resulting insight is most valuable when it shapes structure rather than surface. Navigation labels, category taxonomies, form sequences, and terminology decided from customer research rather than internal convention are among the most durable improvements a site can make, because they reduce effort on every visit rather than at a single decision point. This is normally why user research precedes information architecture work in a product design engagement, and why redesigns that skip the research stage tend to reproduce the organization's own model in a new visual style.