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)

    Understanding Your Users - Courage and Baxter

    Courage, C. and Baxter, K. (2005): Understanding Your Users: A Practical Guide to User Requirements. London: Morgan Kaufmann Publishers.

    Synopsis

    The focus of this book is on the ‘user requirements gathering’ stage of product development, in terms of data collection techniques and data analysis.

    The authors define requirements as the “…features./attributes the product should have or how it should perform.” Requirements for a variety of sources including the user (i.e. stakeholders) should be taken into account (e.g. marketing, purchase-decision makers, product development)

    User Requirements Definition

    • “…the features/attributes your product should have or how it should perform from the users’ perspective” (p3)

    User-Centred Design (UCD) Description

    • Definition – “…product development approach that focuses on the end users of a product” (p3)
      “…the product should suit the user, rather than making the user suit the product” (p3)
    • Principals of UCD (Gould and Lewis 1985) – Note date and how they are still being considered today
    • Early focus on users and tasks:
    • Structured and systematic collection of data relating to user requirements.
      · “To maximise the usability of a product, the user should be involved from the product’s conception” (p4)
      · “The earlier the user is involved, the less repair work needs to be done at the final stages of the lifecycle” (p4) – In other words after a usability test.
      · “By collecting user requirements, you can gain an understanding of such things as what your users really want and need, how they currently work or how they would like to work, and their mental models or mental representations of their domain. This information is invaluable when creating a superior product” (p4)
    • Empirical measurement of product usage
      · A measurement on product usage based on experience rather than theory.
      · Usually involves testing of a prototype or final product on the user by asking them to perform a number of tasks and by identifying the issues that arise.
    • Iterative Design
      · In other words the repeated design, testing and modification of requirements.
      · “…you continue to iterate and fine-tune with each cycle until you get it right” (p5)
      · “No one gets all the information the first time, no matter how expertly you execute each usability activity” (p5)

    Variety of Requirement

    • “…many product teams now realise the importance of understanding their users and the consequences that result when users are unable to utilize products with maximum case” (p8)
    • However, many companies only perform a usability test as opposed to user requirements.
    • “There is a clear difference between usability testing and user requirements gathering. Usability testing determines whether a given solution is usable. Requirements gathering provides insight into the many possible solutions and allows a person to select and investigate the best solution from the users’ perspective. The difference between a good designer and the outstanding designer is the latter’s vision of solutions. Without requirements gathering, your vision is seriously limited” (p9)
    • Usability testing is still very important but it only plays a part

    Importance of Getting the Correct Information Concerning User requirements

    • “…before and the product is sold, you want to make sure that end users can actually use it and that it contains the features they need” (p13)
    • “…you may think you understand what the end users want and need because other sources have told you on their behalf. This is the number one mistake that product teams make” (p13)
    • USEFUL DIAGRAM OF MISCOMMUNICATION OF PRODUCT RESEARCH / USER REQUIREMENTS ON PAGE 14
    • “…you must talk to the actual users, the people who will use the product at the end of the day, to gain an understanding of their perspective and needs” (p14)

    Benefits of Correct User Requirement Information

    • Customer satisfaction and increased ease of use = increased sales and market share
    • Decreased training and support calls that often occur as a result of a mismatch in the users’ mental model (conceptual model)
    • Decreased development time and cost as the product only contains the “necessary functionality” (p14)

    Learn About Your Product

    • "It is key for you to ascertain as much as possible about the existing product in terms of its functionality, competitors, customers etc. In addition, you need to assess what is currently understood about the users and begin to create user profiles" (p29)
    • "Before you even begin working with a single user, you need to understand the domain you are working in" (p29)
    • It is important know your product intrinsically - functions (available or planned), competitors, issues, perceived users etc.
    • "...the best way to learn about a product is to use it" (p31)
    • Networking - Find out from people in your domain
    • Log files - Web server log files can be very useful in finding out about usability data. They indicate such aspects as files requested, times and dates of requests, content type and length, error messages, users browser etc. However, you would need a specific programme to be able to do this.
    • Surrogate products - These are products which may not directly compete within your market segment but have similar features. Analysing these types of product can also provide very useful.

    Competitors

    • "A competitive analysis can be an effective way to gain an advantage over your competitors" (p37)
    • "It is beneficial to conduct a competitive analysis when you are creating an entirely new product or simply entering a new product domain" (p37)
    • This can also be useful if you are struggling with your product but your competitors are thriving. That way you can analyse what it is that is making them succeed.

    Learn About Your Users

    • "If you do not understand who your users (or potential users) are, your product is doomed to fail" (p41)
    • "The single most critical activity to developing a quality product is understanding who your users are and what they need" (p41)
    • This can be done by developing a user profile (a detailed description of user attributes - e.g. experience, level of education, age etc.) personas (examples of your end user) and scenarios (a day-in-the-life of your end user). SEE TABLES ON PAGE 42 FOR A COMPARISON OF THESE THREE ASPECTS.

    User Profile

    • Understanding this characteristics of your users help you create a better picture of who you are building your product for. Possible areas to consider are:-

      1. Demographic Characteristics – age, gender, location, socio-economic status
      2. Occupation Experience – current job, length of experience, responsibilities, previous employment
      3. Computer Experience – skill set, skill level, experience
      4. Education – degree, subject area etc.
      5. Tasks – primary and secondary.
      6. Domain Knowledge – user’s level of understanding of product area.
      7. Technology Available – hardware, software, other tools.
      8. Attitudes and Values – product preferences, fear of technology etc.
      9. Learning Style – visual learner, audio learner etc.
      10. Criticality of Errors – possible consequences of user error.
    • Once this information has been established you can then group each attribute into the following categories:

      1. Age (child, young adult, adult or older)
      2. Experience (noive, expert)
      3. Attitudes (first adopters or technophobes)
      4. Primary Tasks (e.g. buyer, seller)

    This will be incredibly useful to include in the assignment section on how to establish your users.

    Scenarios

    • "Scenarios help you test your system and to build functionality into your product that users will actually want to use" (p41)

    Personas

    • A fictitious method for establishing a 'typical' user of your product
    • "Personas are designed to help keep specific users in focus during design discussions" (p41)
    • There are a number of benefits for using personas when attempting to understand your users:

      1. "...personas give your users life and help team members feel connected to them" (p48)
      2. "Trying to build a porject for a generic "user" is like trying to hit a moving target. Without a specific target to focus on "the user" can change from the expert to the noive to your grandmother all in the midst of a single conversation" (p49)
    • There are also a number of things to be aware of when using personas:

      1. Numbers are an important aspect to consider. Too many examples of personas and you may end up being to vague and non-specific. At the same time, "By limiting your vision to one persona, you may end up filtering out valuable data from end users who do not match that one profile" (p49)
      2. "Personas should never replace conducting usability activities with your end users. Personas should be based on the data from usability activities" (p50)
    • Creating personas can be done by including the following informaiton:-

      1. Identity - first name/sirname, demographic information (age, gender etc.)
      2. Status - primary, secondary user?
      3. Goals - user's goals
      4. Skill set - background, education level, expertise, training, specialist skills (does not have to relate to product)