Gaps between the mental model and the implementation are where design must bridge

What it is

Overlay what users believe on how the system actually works, and the misalignments are not “users don’t get it.” They are the mental-implementation model gap: people predict from their causal story, the system answers from another rule set. Design’s job is those mismatches—using the system image so visible behavior comes closer to the person’s model, or so the person can revise toward a still-usable model. The gap map is a work list, not a poster for mocking users.

Why it happens

People cannot see the implementation; they update an internal story from controls, copy, state, and feedback. If the image implies “delete means gone” while the implementation only archives, an item that later appears in search will be read as a fault. Gaps erupt when a prediction fails: the action should succeed under the user’s model, and the system takes another path. Bridging has two directions that must not collapse into “educate the user”: change the image to honor a stable, reasonable user model, or, when that model cannot support the task, use visible structure to help rewrite it. Both land on specific mismatch sites, not on a wholesale reconcepting.

Studying it

Align the user diagram and the implementation diagram on a shared set of entity aliases. Mark: present for the user but absent in the system, present in the system but absent for the user, same name with reversed causality, same action leading to different next states. For each mismatch, replay the pause or error it caused in the task. Experiments or revisions should manipulate the image at one mismatch (feedback, name, default visibility) and watch whether that class of failed prediction drops; a wholesale redesign cannot be attributed.

Where it stops holding

Some gaps are hard because the domain is hard, not because the interface was drawn badly—distributed consistency and eventual consistency, for example. Erasing those gaps completely would lie. When the user’s model contradicts itself, clarify the model before aligning it with the implementation. Experts who deliberately use the implementation model will be hurt if the image is forced into a novice metaphor.

Applying it

• Treat the mismatch table as design todos: each row names which piece of the image or which moment of guidance will change; do not write “more education” alone.
• Prefer fixing the feedback and names that caused failed predictions, before making a concept animation.
• If the choice is to teach a model closer to the implementation, specify at which task moment, with what visible evidence, and test whether predictions improve afterward.
• Before release, regress the original mismatch scenarios: if the old failures remain, the bridge did not land on the gap.

Related

• Same group: Q4.14.1 A mental model diagram shows how users think the system works, not how it does · Q4.14.3 Experience levels can differ in kind, not only in amount · Q4.14.4 Infer mental models from task observation; asking yields post-hoc stories
• Adjacent: Q4.13 Hierarchical task analysis · Q5.01 Fidelity levels
• Search terms: system image · gulf of evaluation · conceptual gap