In UI design we often talk about "mental models" that users need to form. I'm wondering if there is a particular relationship between that mental model and the actual information model that the system implements. Is the mental model a strict subset? Do they just overlap?
1
-
note that in the context of this question the terms: information model and data model may be considered synonymous. If you think otherwise, reply.– Dan D.Commented Mar 8, 2012 at 11:09
Add a comment
|
3 Answers
Just break down the two terms to see the difference and, consequently, the relationship.
Note from @PhilipW's link in the comments:
Mental models are representations in the mind of real or imaginary situations.
From A Gentle Introduction to Mental Models (Phil Johnson-Laird and Ruth Byrne, May 2000)
In the context of your question, a mental model is just jargon for "the picture I have in my head of how I expect this thing to work". An "information model" or domain model is the way the designer of the system intends for it to work.
For designers, it's important to recognise that whatever you design, however well you design it, people will end up forming their own picture in their heads of how they think it works. And that can differ pretty substantially from what you as a designer had intended.
Great designers therefore are able to intuit and predict the ways that their domain model will end up being translated by users of the system into different pictures. Being able to do that is usually a function of experience and talking to hundreds of people to learn the patterns that lead to that translation taking place.
This is why domain-driven design is a great methodology: it standardises that approach and helps you learn to map domain models to mental models more effectively.
See Mental model vs conceptual model: what's the difference? for a similar question.
-
Mental Models are an (old: 1943) concept from Psychology - they can represent abstract situtations rather than things which can be visualised: tcd.ie/Psychology/other/Ruth_Byrne/mental_models– PhillipWCommented Mar 7, 2012 at 12:56
-
Indeed; I didn't mean visualise literally, I was using it as a metaphor to describe how you should think about what mental models are.– RahulCommented Mar 7, 2012 at 13:02
-
When I picture an information model, I think of something like a database schema - boxes or blobs connected to each other by relationships. Is it possible to similarly diagram the intended mental model, and thus overlay the two diagrams? Commented Mar 9, 2012 at 11:26
-
The closest thing to that is affinity diagrams (KJ models), which attempt to record the information structure from a group of stakeholders and then group that in a logical way from which you can draw a content model.– RahulCommented Mar 9, 2012 at 12:07
Mental models are about goals and tasks, and the links between them.
Information models are about objects and meta data, and the relationships between them. In many ways the info model is the designer's view of the system.
Ideally, they do overlap. See Don Norman here: http://jnd.org/dn.mss/design_as_communication.html
-
-
1It only gets onto conceptual models towards the end. The main points are that a conceptual model is a set of stories with reasons: any explanation that makes to the user for why they have to do a particular series of actions. Commented Mar 7, 2012 at 4:10
-
Don' s orginal explanation is on page 16 of the Design of Everyday Things - which you might have to hand...– PhillipWCommented Mar 7, 2012 at 12:53
If you use correct idioms in UI to explain the relationship between the information and how the users may think about it (their mental model), its easier to overlap them. The more the implementation or information models resemble the user's mental model the better. Alan Cooper talks about it extensively in About Face 3
