System Models vs User Mental Models

In human-computer interaction, three distinct models coexist during every interaction:

1. The Design Model: The designer's internal mental conception of how the product ought to function.
2. The System Model (or System Image): The physical interface, code, documentation, signals, and affordances that actually manifest on screen.
3. The User's Mental Model: The user's internalized mental simulation of how the system works, formed by past experience, digital conventions, and observed interface cues.

When users interact with software, they encounter two fundamental cognitive bridges:

• The Gulf of Execution: 'How do I make the system do what I want?' (Bridged by clear affordances, discoverable actions, and intuitive controls).
• The Gulf of Evaluation: 'Did the system do what I intended, and what state is it in now?' (Bridged by immediate feedback, progress indicators, and visible state confirmation).

When software exposes technical database architectures (e.g., asking users to 'commit schema cache' rather than 'save changes'), it widens both gulfs by forcing users to learn engineering internals.

Metaphors map familiar physical-world concepts onto digital interfaces (e.g., desktop, folders, trash bin, shopping carts, bookmarks).

• The Benefit: Metaphors bootstrap intuition, allowing first-time learners to guess how controls behave without reading a manual.
• The Pitfall: Metaphors inevitably break down when digital capabilities outgrow physical reality. (For example, physical folders can only be in one drawer at once; digital files can have multiple tags across several collections).

Design for conceptual integrity: use metaphors to teach initial interactions, but never compromise usability to satisfy physical-world realism.