Literature Review Notes

This blog has been created to supplement my written diary and has been used as source for making notes and highlighting quotates from the literature I have reviewed. Furthermore, it serves as documented evidence for the material I have read and as a reference guide for key concepts, terminology and useful sources.

The layout of my blog is as follows:

1. The heading section of each post contains the title and author of a piece of literature I have reviewed. This can then be easily identified under the archive section of my blog, on the right hand menu. By opening a post you will see the notes I have made on the corresponding piece of literature.

2. Under the 'Useful Links' section of my blog is listed a number of websites, relating to my chosen subject area, which I have found useful.

3. Finally, I have created a 'Label' section in the right hand menu of the blog in order to identify key words within each piece of text, for the purposes of linking the literature together during the critique stage.




Saturday, 20 October 2007

The Design of Every Day Things - Donald Norman

Norman, Donald. A. (2002) The Design of Every Day Things. New York: Basic Books

Conceptual Models

  • Communication between the designer and the use
  • The formation of a mental image of the operation of a particular object or piece of equipment.
  • “A good conceptual model allows us to predict the effects of our actions” (p13).In other words the parts are visible and the outcome is clear.
  • If we are not able to visualise what our actions will produce then this makes for bad design.
  • The designer’s “model” must be inline with the users.
  • Conceptual models are influenced by “mental models” (the models people have of themselves, others, the environment and things they interact with). Mental models are formed through experience, intuition, training and instruction. “The mental model of a device is formed largely by interpreting its perceived actions and its visible structure” (p17)
  • The visible structure mentioned above is termed the “System image” – “When the system image is incoherent or inappropriate then the user cannot easily use the device” (p17). This links in with the comment above about designer and user model being in unison.

Feedback

  • “In design, it is always important to show the effect of an action. Without feedback, one is always wondering whether anything has happened” (p xii - preface)
  • If an action shows no visible and clear result the user will assume that the action has either failed or not registered.
  • Feedback – “sending back to the user information about what action has actually been done, what result has been accomplished” (p27)
  • As technology increases equipment becomes harder to use with less feedback. This is because companies want to keep the costs low for the consumer. If the usability and feedback increased so would the cost.

Constraints

  • “The surest way to make something easy to use, with few errors, is to make it impossible to do otherwise – to constrain the choices” (p xii – preface)
  • If choices are constrained then there will not be a need for instructions on how to work what are essentially simple tasks (e.g. push signs on a door, small instruction stickers on cameras)
  • “Rule of thumb: when instructions have to be pasted on something (push here, insert this way, turn off before doing this), it is badly designed" (p xii – preface)
  • Affordances

  • “A good designer makes sure that appropriate actions are perceptible and inappropriate ones invisible” (p xii preface)
  • Affordance is basically another word for describing what an item or a material or piece of equipment “is for” and indicate the operation of things (e.g. door knobs are for turning, slots are for inserting things in, balls are for bouncing etc.)
  • “When affordances are taken advantage of, the user knows what to do just by looking; no picture, label or instruction is required” (p xii – preface)
  • More complicated pieces of technology will probably need some form of explanation or instruction but Norman believes that simple objects should be intuitive. “When simple things need pictures, labels or instructions, the design has failed” (p9)
  • Visibility

    • Good design should be clear and visible.
    • Single controls should often have single functions. For example if a single button has multiple functions then confusion arises as it is difficult to remember the combinations for the user to achieve their desired result.
    • When controls have single functions these can then be specialised and therefore labelled, making its function clear. Moreover, if the user forgets the function the labels are then used as prompts to remind the user.
    • Visibility also links to structure. The structure should have a natural relationship between the functions / controls and have good mappings. They should be fluent / flowing and have some form of order and positioning that relates to the task (e.g. a car - the window operation buttons are usually near the window, the air conditioning on the dashboard near the air vents etc.)
    • Feedback should also be visible.
    • When functions are invisible and hidden from site (usually as a result of multiple functions) then labels can not be used to the same effect, and the task become more difficult. Furthermore, without labels then the user is more likely to forget the functions.
    • “Visibility acts as a good reminder of what can be done and allows the control to specify how the action is to be performed. The good relationship between the placement of the control and what it does makes it easy to find the appropriate control for the task. As a result there is little to remember” (p23)

    Mapping

    • “Mapping is a technical term meaning the relationship between two things” (p23) E.g. a steering wheel – turning clockwise turns the car right and anti-clockwise turns left.
    • The user being able to clearly identify the mappings of a control mechanism and its function is very important in terms of good design.
    • "Natural mapping, by which I mean taking advantage of physical analogies (relationships) and cultural standards, leads to immediate understanding” (p23) E.g. special analogy – moving a control in the upwards direction moves the object up.
    • Biological and cultural mappings – E.g. a rising level means “more”, a diminishing level means “less”. A louder sign means a greater amount. The relationship between these examples are known as “additive dimensions” (add more to show an increase).
    • Substitutive mappings – substituting one value for another to make a change (e.g a change in pitch or colour). There is no natural comparison to more or less by changing the colour or pitch of the control.
    • Some natural mappings follow the principal of intuition or perception and enable the user to form a natural pattern of the control and feedback. (e.g. a seat adjuster in a car in the shape of a seat. By pressing a section of the seat shaped button in a recline direction the seat reclines)
    • “A device is easy to use when there is visibility to the set of possible actions, where the controls and displays exploit natural mappings” (p25)
    • “Principal of natural mappings: the relationship between the controls and the actions should be apparent to the user” (p25)
    • “There must be a close, natural relationship between the control and its function: a natural mapping.” (p27)

    Requirements

    • Shops want from their manufacturers something that I attractive to the consumer.
    • Consumers focus on price, prestige and appearance in store but functionality and usability at home.
    • Repair services focus on reliability and maintainability.
      It is very difficult for the designer to satisfy all three but this is what they should aim to do.

    Paradox of Technology

    • “Technology offers the potential to make life easier and more enjoyable; each new technology provides increased benefits. At the same time added complexities arise to increase our difficulty and frustration” (p30)
    • Technology is affected by complexity. New technology is complicated and difficult to use. Then as technicians become more competent and the industry matures devices become easier to use, more powerful and more reliable. However, this encourages newcomers to increase power and capability and this then increases complexity again and may also decrease reliability.
    • “The paradox of technology should never be used as an excuse for poor design. It is true that as the number of options and capabilities of any device increases, so too must the number and complexity of the controls. But the principals of good design make complexity manageable” (p31)

    No comments: