
Users do not have access to the conceptual models of designers. Their understanding of how a product works is developed based on their interactions with the product itself, their previous experiences with the world, and their existing knowledge and expertise. All of these considerations affect how people interpret their experiences with a product, and the mental model [define] they create to explain how products work.
The term system [define] image refers to the way a product or service system actually appears to a user. System images are always imperfect representations of the conceptual models upon which they were built. For a product to be usable the system image needs to enable users to develop an accurate mental model of how relevant aspects of a product or service works.
An interesting feature of Norman’s 1988 model, is that designers relationship with system images is represented as a one-way phenomenon. This implies that once a product has been designed there is little opportunity for on-going improvements. During the last 20 years advances in technology and design methodology have made it possible for designers to continuously fine-tune product and service systems. This is especially true in the increasingly service-based world of software.

Hartmann posits that user-initiated feedback via the system will help identify mismatches between the designer’s conceptual model and the user’s model of how the system functions. Another important consideration is that offering an instantaneous feedback option in the same media on which the interaction is taking place will generate more reliable and richer data than feedback elicited later, or via a different channel.
[Sourced from Don Norman’s website, though I know Norman's framework was also featured in this book The Design of Everyday Things; Paper by Bjoern Hartmann written during graduate studies at Standford]
** What the hell is ID FMP? **
No comments:
Post a Comment