Metaphor and Design |
The physical world grounds our thinking. Lakoff and
Johnson argue that our more abstract thoughts are built
metaphorically upon a physical foundation. The world of
information is inherently formless - and in that nebulous
state, very difficult for us to comprehend. Interface
designs shape and define information through metaphoric
structuring. Thus the web consists of "sites" and "pages",
email is put into "folders", operating systems provide
"windows" and "folders". Metaphors help us make sense of abstractions, but in the process also limit what we make of them. Organizing the formless stream of emails into folders both makes us better able to handle them, but also limits this potentially more versatile electronic form to the functions of the metaphor's physical counterpart, e.g. an email can only go in one folder, though it may be relevant to ten. Not all metaphors are as obvious as pages and folders. A clock puts time into the metaphor of a circle, an endless, seamless cycle. A stock market graph uses the metaphor of growth to be intuitive: higher numbers are up, lower ones are down. Any information system uses metaphor to make comprehensible its abstract contents. When the system is simple, such as a diagram, the visible form is the function. When it is more complex, such as an application interface, the visible form and verbal labels provides cues to identify the metaphor that structures the underlying functionality. E.g., The name "facebook" is a metaphorical cue to the funcion of that application. Since metaphors limit as well as empower, it behooves the designer to choose their metaphors carefully. |
|
readings |
|
|
assignment |
Please link your work by midday on Tuesday. |