Skip to content

Mental Model Mismatch Repair

Detect and repair mismatches between a person's mental model and how the system actually behaves.

The Diagnostic Story

Symptom: The same errors recur even after training, and incident narratives contain phrases like 'I thought it would.' Users create workarounds that fight the system rather than use it, and explanations that seem perfectly clear do not stick. The gap between expected and actual behavior keeps generating friction that could have been resolved if its source had been diagnosed.

Pivot: Make the expected behavior explicit, compare it with observed or demonstrated actual behavior, diagnose the source of the divergence, choose the right correction locus -- model, system, or both -- and test whether future expectations are corrected.

Resolution: Predictions become more accurate, repeated errors decrease, and trust calibration improves. Training transfers because learners now hold a model that matches system behavior. The mismatch remains observable so drift can be caught before errors return.

Reach for this when you hear…

[aviation training] “The student keeps pulling back when the stall horn sounds because they are applying car-driving intuition -- until we directly surface that model and contrast it with how lift actually works, the correction will not hold.”

[EHR implementation] “The nurses keep clicking the wrong button because they expect the save to happen on navigation, not on explicit submit -- the system needs to either match the expectation or make the actual behavior unmissable.”

[DevOps] “Developers keep thinking the staging environment behaves like production until something breaks on Friday evening -- we need to either make the difference legible or reduce the difference, not just add another warning they will ignore.”

Mechanisms / Implementations

  • Documentation Revision
  • Expectation Audit: Traces where an expectation, label, or score enters a process and maps the behavior channels through which it may be quietly manufacturing its own confirmation.
  • Incident Mental-Model Review
  • Interface Affordance Redesign
  • Simulation-Based Correction
  • Training Feedback Loop
  • Usability Testing
  • User Journey Diagnostics

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

Also references 6 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Interface Expectation Repair · implementation variant · recognized

Repair mismatches created or reinforced by interface cues, labels, defaults, or affordances.

Operator Model Retraining · domain variant · recognized

Repair outdated or incomplete operator expectations about a machine, process, policy, or operational environment.

Reasonable Expectation System Alignment · risk or failure variant · candidate

Repair the mismatch by changing the system or process to match a reasonable user expectation rather than changing the user.