Scott McDaniel's article about mental models can be meaningfully connected to several of the earlier postings in EduResources about cognitive mapping. I especially like the way that Scott explains mental models with simple examples and also how he shows the value of exploring mental models in working with clients. The focus of his work is on designing user interfaces for software to improve usability; he uses mental models to compare users' mental models with the designer's model--arriving at a workable revision of the software interfaces or at guidelines for the use of the software.
"... mental models aren't defined more specifically than a mental representation of something. How, then, do you tell people in other disciplines, such as managers or developers, what they are? I often use examples to convey what a mental model is. If I tell them that I recently ordered a steak at a restaurant, they might assume that I was met at the door by a host or hostess, seated, and presented with a menu. They assume these details, and others, that I never actually mentioned because they have a mental model of how restaurants operate. To illustrate the consequences of having a mismatched mental model, I describe a person who goes into a buffet restaurant and waits for someone to take their order. The person's mental model of how that restaurant operates doesn't match the actual situation, and he would experience confusion and frustration until he modified his original model to include buffets."
"Defining mental models by example is not sufficient if we want to treat them more formally, however. All mental models have a few key characteristics:
* Mental models include what a person thinks is true, not necessarily what is actually true.
* Mental models are similar in structure to the thing or concept they represent.
* Mental models allow a person to predict the results of his actions.
* Mental models are simpler than the thing or concept they represent. They include only enough information to allow accurate predictions."
"Mental models should serve as an analytic tool, allowing us to clearly document users' current mental images, vocabulary, and assumptions. Once the mental model is documented, we can create a target mental model--the model of the product that we want our users to have. If there is a difference between the two, we can design the UI and user assistance material to transition users from their current models to the target model."
_____
What's Your Idea of a Mental Model. From Boxes and Arrows: This article proposes a formalization for mental models. Mental models should serve as an analytic tool,... [Ed Tech Dev]
9:45:00 AM 
|
