Isomorphism Check

Description

Lay the user's mental model and the system's real structure side by side and find exactly where the mapping between them breaks.

Hofstadter argues that symbols carry meaning only when there is an isomorphism, a part-for-part and rule-for-rule correspondence, between a formal system and something in the world. An interface works the same way: people act on a model of the system they carry in their heads, and things go wrong where that model and the real structure stop corresponding. An isomorphism check makes both structures explicit. You elicit the user's model (entities, relationships, the rules they believe apply) and draw the system's actual model (objects, states, rules) in the same notation, then pair the parts one by one. Elements with no partner, partners with the wrong relationship and rules that hold on one side but not the other are the places where users will form false beliefs, and they explain errors that look random in testing.

Attributes

Loss type
Latent
Effort
Days

Steps

  1. Draw the system's model: the objects users deal with, how they relate, and the rules that change them, in plain words.
  2. Elicit users' models through think-aloud, teach-back (ask them to explain the product to a new colleague) or a drawing task, with 5 to 8 people.
  3. Redraw each user's model in the same notation as the system model.
  4. Pair elements across the two models and mark each pair as matched, missing on one side, or mismatched in relationship or rule.
  5. Check whether each mismatch predicts an error or confusion you have seen in testing, support tickets or analytics.
  6. Decide per mismatch whether to change the system to fit the model, or change what the interface shows so the model can be corrected.

Sources

  • Hofstadter, D., Gödel, Escher, Bach: An Eternal Golden Braid (1979)

Also known as

  • Mental model to system isomorphism mapping
  • Form-meaning mapping audit

Categories

  • User Research
  • Cognitive Psychology & Perception