Users at different experience levels may hold qualitatively different mental models

What it is

Gaining experience does not only fill in the same drawing. Expertise-differentiated mental models means novices and practiced users may work with different kinds of entities and different causal skeletons: a file is “a document” for one person and an object with versions and permissions for another; an account is “how I log in” for one and a billing principal for another. Averaging both groups’ statements into one figure erases both structures.

Why it happens

Skill acquisition rewrites representation; it does not only speed the same path. Novices often group by surface (screens, buttons, colors); practiced users group by task goals and system invariants (whether state is committed, who holds write permission). Intermediate levels can hold an unstable mix and fall back to surface strategies under pressure. Qualitative difference implies different error types: novices mis-predict “not seen means it did not happen”; practiced users mis-predict “this action is isomorphic to the last one.” A compromise diagram explains neither, and cannot support the latter’s acceleration.

Studying it

Stratify on operational experience: years with related products, history of success on the specific task, adjacent professional roles—not a self-rating of “how expert.” Model each stratum on its own, then compare entity lists, relation types, and the repair stories invoked after failure. Look for breaks that cannot be crossed by “adding detail”—for example novices lacking the pair “draft / submitted.” Test for those breaks before mixing groups into a “generic model”; if they exist, keep layered diagrams.

Where it stops holding

Experience is not a single ladder. A person expert in one module can be a novice in the next; stratify by task, not by head. Some products never form a qualitative jump, only a speed difference. Stratifying too finely treats every individual as a model and loses designable clusters. Self-reported fluency often disagrees with observable performance; stratify on performance.

Applying it

• Deliver at least two mental model drawings: target novice and target practiced user, with break points marked, not one merged figure.
• Give the default flow visible state on the novice skeleton; make practiced users’ shortcuts accelerators that do not break that skeleton.
• Training should not only add a feature list; it should name the new entities that must replace old ones (for example “submitted and draft are not the same object”).
• Recruit usability samples by experience strata; averaging a mixed group will read a qualitative difference as “some people were slower.”

Related

• Same group: Q4.14.1 A mental model diagram shows how users think the system works, not how it does · Q4.14.2 Gaps with the implementation model are where design must bridge · Q4.14.4 Infer mental models from task observation; asking yields post-hoc stories
• Adjacent: Q1.04 Sampling and representativeness · Q4.03 Personas
• Search terms: expertise · qualitative shift · novice expert mental model