1. Design and Evaluation Human Factors Psychology Dr. Steve

2. Human Factors Design Activities n Design product/system interfaces n Modify designs/correct design flaws n Safety activities (warnings, analyses) n Develop training programs/materials

3. Cost/Benefit Analysis Costs HF personnel salaries Extended time to product release Analysis tools (software, video) Prototyping Increased development cost Benefits More effective product Safer product Cheaper to change design early in development Higher sales Fewer liability suits What other costs and benefits of HF activity in product/system design can you think of?

4. System Development and HF Activities Stage 1. Front-End Analysis* user analysis function analysis preliminary task analysis environmental analysis system specifications Stage 2. Conceptual Design* function allocation support conceptual design Stage 3. Iterative Design and Testing* task analysis interface design & prototyping heuristic evaluation cost/benefit analysis of alternatives workload analysis (simulation & modeling) safety analysis usability testing Stage 4. Design of Support Materials develop manuals Stage 5. System Production Stage 6. Implementation and Evaluation experiments to evaluate system Stage 7. System Operation/Maintenance monitor system performance Stage 8. System Disposal * Topics covered in class

5. User-Centered Design 1. Early focus on the user and tasks 2. Empirical measurements questionnaires, usability studies, data collection 3. Iterative design prototyping of interface 4. Participatory design user input to design, preferences, SLUGs

6. Sources for Design Data Data Compendiums Engineering Data Compendium: Human Perception and Performance Human Factors Design Standards MIL-STD-1472D (military anthropometry, ergonomic specs) ANSI/HFES-100 (VDT specs) ANSI/HFES-200 (software specs) OSHA standards General HF Principles/Guidelines Textbooks (by topic: interface design, aviation, software) Research Journals (Human Factors, Ergonomics, Applied Ergonomics) Handbooks (Handbook of Human Factors) Conferences (CHI, HFES, IEA) Workshops (U of Mich)

7. Front-End Analysis Answers the following questions: 1.Who are the users? Consumers, trainers, maintainers, etc. 2. What functions are performed by system? Allocate functions to machine or person 3. What are the environmental conditions where system will be used? Noise, temperature, pressures, etc. 4.What are users’ preferences/requirements? Color, functions, shape, etc. 5.What are constraints to design of the system? Space, regulations, costs, resources 6.What are the HF criteria for design solutions? Shorter training time, less accidents, higher performance

8. Front-End Analysis User Analysis Who are the intended users? Age Experience level Intellectual level Anthropometrics (size & shape) Strength Culture & Language Disabilities (sight, hearing, mobility) Why does the drive- thru ATM have Braille on its controls? What are the characteristics of DVD player consumers?

9. Front-End Analysis Function/Preliminary Task Analysis Function Analysis: What are the basic functions of the system? Example: The function of a wheel barrow is to move objects to the work site. Preliminary Task Analysis: What are the jobs, duties, tasks, and actions that user will be performing? Example: Tasks to be performed with a wheel barrow include loading it with dirt/building materials, transporting, mixing, and dumping materials, cleaning, maintaining, and storing wheelbarrow.

10. Front-End Analysis Preliminary Task Analysis Preliminary Task Analysis Methods: Interviews Focus Groups Observation Questionnaires Used prior to design to learn how intended users perform their jobs. What method(s) would you use if you were designing a new library cataloguing system?

11. Front-End Analysis Environment Analysis Where will the tasks be completed and under what conditions? Indoors/outdoors Temperature/humidity Lighting levels Noise levels Vibration Gravity Special clothing/gear requirements How would the design of a radio transmitter differ if the intended users were researchers in Antarctica? Would a standard vending machine work on the space station? If not, how would you design a vending machine for that purpose?

12. Front-End Analysis User Preferences & Req’s When different design options are available, must determine the intended users preferences and needs (perhaps determined through focus groups). User preference issues include: What components are automated Color features/aesthetics Balance between performance and preference What makes other products popular/unpopular What can be made adjustable and what cannot Feasibility of user’s demands

13. Conceptual Design Activities Function Allocation Things Humans Do Well Ability to: detect small amounts of visual or acoustic energy perceive patterns of light or sound improvise and use flexible procedures store very large amounts of information for long periods and to recall relevant facts at the appropriate time reason inductively exercise judgment Things Machines Do Well Ability to: respond quickly to control signals, and to apply great force smoothly and precisely perform repetitive, routine tasks store information briefly and then to erase it completely reason deductively, including computational ability handle highly complex operations, I.e., to do many different things at once Fitt’s List (1951) Function Allocation: the assigning of tasks to humans or machine taking into account human vs. machine capabilities and limitations Is Fitt’s list still appropriate 50+ years later?

14. Conceptual Design Activities Decision/Action & Functional Flow Analyses Decision/Action and Functional Flow Analyses: Procedures for identifying and depicting the sequence of functions, actions, and decisions made by the system (user included as part of system). Example: Programming your VCR to record a show Thursday night at 7:30 on Fox Network Press “Program” “use up & down arrows to indicate selection” Access input menu Determine When show airs Hit arrow to indicate day VCR accepts Input, moves to next field Press “Enter” button Hit arrow to indicate time VCR accepts Input, moves to next field Press “Enter” button Hit arrow to indicate channel VCR accepts Input Press “Enter” button “Program complete Select another program or press End to finish” Yes or No Press “End” Yes No (See homework assignment)

15. Conceptual Design Activities Typical Design Meeting Brainstorming Story-Boarding

16. Iterative Design and Testing

17. Iterative Design and Testing Task Analysis (detailed) Purpose of Detailed Task Analysis is to identify: User goals and activities Tasks required to achieve goals Conditions under which task is performed Expected outcomes of tasks KSA’s needed to perform tasks Equipment needed to perform tasks Complex decision making, problem solving, diagnoses* Complex rule structures dependent on situation* * Part of Cognitive Task Analysis

18. Task Analysis Methods Interviews Interviews: Questioning subject matter experts to get them to explain what they do on the job. Tries to answer questions such as: How do you perform the task? Why do you perform the task? Under what conditions do you perform the task? What happens before and after performing the task? What are the consequences of performing or not performing the task? Advantage: simple to use Disadvantage: SMEs may not be good at describing tasks

19. Task Analysis Methods Observation Observation: Watch and take notes of people performing the task Suggestions: Be unobtrusive Use video if possible and with approval Review observations with SMEs Advantages: See what workers do, not what they say they do. Disadvantages: Does not capture cognitive processes.

20. Task Analysis Methods Think-Aloud Verbal Protocol Think, think, think! Think-Aloud Verbal Protocol: Worker state what they are thinking as they perform the task Concurrent – verbalize as performing the task Retrospective – verbalize what they were doing as they view a videotape of themselves Prospective – verbalize as they imagine performing a hypothetical task Advantage: Can get info regarding thought processes and decisions of experts performing the task. Disadvantage: Doing concurrently can interfere with the task, and doing retrospectively relies too heavily on memory

21. Task Analysis Methods Hierarchical Task Analysis Hierarchical Task Analysis: Graphical (chart or diagram) depiction of task analysis Advantage: Allows to conceptualize task sequences Disadvantage: May not accurately represent true parallel nature of task Example: Table 3.5 from Wickens, Gordon, & Liu Hierarchical task analysis for using a lawnmower Step 1. Examine Lawn a. Make sure grass is dry b. Look for any objects laying in the grass Step 2. Inspect Lawnmower a. Check components for tightness 1. Make sure grass bag handle is securely fastened to grass bag support 2. Make sure grass bag connector is securely fastened to bag adapter 3. Make sure the deck cover is in place 4. Check for any loose parts (such as oil cap) and blade

22. Iterative Design and Testing Link Analysis Link Analysis: Shows the relationships between components of a system (e.g., communication, control, movements) For determining: layout of related workstations placement of controls communication patterns frequency of equipment use Advantage: Graphic depiction of relationships among system features Disadvantage: Shows frequency of use, not importance, and may vary by situation Link Analysis of CIC of USS Louisville

23. Iterative Design and Testing Flow Diagrams Operational Sequence Diagram: Graphically depicts the sequence and timing of activity, and shows the interactions between individuals and equipment Advantage: Connects actions to time and component Disadvantage: Does not lend itself easily to interface design Diagram for a collision avoidance system

24. Iterative Design and Testing Interface Design Principles 1.Provide a good conceptual model 2.Make things visible 3.Use natural mappings 4.Provide feedback

25. Iterative Design and Testing Interface Design Principles Provide a good conceptual model: when things are designed to be consistent with our mental models of how they should work (expectancies) then it is easier to predict what will happen when we use them. In this metronome, the tempos are arranged around a circle with a knob and arrow in the middle. Most people would expect to twist the knob until the arrow points to the desired tempo. Actually the arrow is a button that you push if you want the tempo to increase and the knob is not a knob at all.

26. Iterative Design and Testing Interface Design Principles Make things visible: It is easier to operate a system when the features are clearly visible Starting this gas pump is more difficult than it sounds because the start button is hidden among the other sea of information and does not “pop out” at you as a start button either figuratively or literally. Additionally, the use of red usually signals something other than start.

27. Iterative Design and Testing Interface Design Principles Use natural mappings: Actions should correspond to the system’s state. To make something go up, the action should be up, to make it go right, the action should be to the right This stovetop makes good use of natural mappings. The burners are arranged in the same pattern as the controls.

28. Iterative Design and Testing Interface Design Principles Provide feedback: Feedback is important because it allows one to see whether the intended actions have taken place. (like hourglass icon on computer software) (read “Set Phasers to Stun” in Casey book for another example). In this example the feedback is confusing. The light on the bottom signifies that the smaller quantity of coffee was requested. The light does not go on when the larger quantity is requested.

29. Iterative Design and Testing Interface Design Principles Other Design Principles (Norman, 1992): Simplify the structure of tasks Make alternative actions and knowledge of results visible Make it easy to determine what actions are possible Make it easy to evaluate current system state Exploit the power of constraints (remove possibility of error) Design for easy error recovery (undo) When all else fails, standardize.

30. Iterative Design and Testing Prototyping Prototypes or Mockups: Used to test features of the interface prior to production - may be anything from crude cardboard cut-outs to realistic models Example of Rapid Prototyping Software used to model different phone interfaces

31. Iterative Design and Testing Evaluative Studies Types of evaluative studies: Cost/Benefit Analysis for Design Alternatives Trade-Off Analyses Safety Analysis Workload Analysis Simulation & Modeling

32. Mathematical Modeling Evaluative Studies Simulation & Modeling Cognitive Modeling Biomechanical Modeling Modeling programs: MicroSAINT Mannequin COMBIMAN HUMANCAD

33. Evaluative Studies Usability Testing Usability Testing: Ease of use (user-friendly) May test for: Learnability Efficiency Memorability Errors Satisfaction

34. Final Test and Evaluation Field Studies Design: between vs. within subjects Test Participants: user population Proximal Measures: satisfaction usability performance errors Distal Measures: manufacturing costs personnel costs number of accidents/disability claims

35. Alternatives to HF Design and Development Training To use system capabilities Methods to make task safer Modifying Current Equipment Equipment Replacement Ergonomic Aids Wrist pads Foot stools Anti-fatigue mats Job Rotation (and other admin approaches) Vary tasks Rest periods

36. Cow Factors in Design This is what happens when you fail to consider the user in the design