1. Design of Everyday Things

2. Agenda Questions? Project Part 1: Now what? Test review One last bit on prototyping Design of Everyday Things

3. What to do now Start brainstorming!! – Lots of ideas, then narrow down to 3 or 4 Explore design space – Vary what you can – hardware, forms of input, forms of output, features, requirement priorities, usability priorities Be off the wall, crazy – This will lead to less crazy but original ideas Project poster – October 20 Project report + prototype: Nov. 10

4. Midterm review How to study: – Look at slides for topics, bullets, vocabulary, etc. – Find details and examples in the books as needed Test format – 25-50% true/false, multiple choice, fill-in-blank – Rest short answer, probably with one longer answer

5. Review What is usability? What is design? Why is it hard? The user centered design process – General steps – various models – high level understanding – Waterfall vs. other models

6. Requirements Review Functional vs. non functional Summative eval vs. formative eval What pieces are part of this? – User characteristics, task analysis, environment, etc.etc. – Persona – what is it and what makes a good one? – Scenario – what is it and what makes a good one? – Stakeholders (primary, secondary, tertiary, facilitating) How do you gather data? Tradeoffs? – Interview, questionnaire, observation, etc. etc. Task models – Hierarchical task analysis - how to do it? – Other models – what can they represent?

7. Humans review What are issues concerning our senses? Model Human Processor model of memory – What are pieces of memory (STM, LTM, etc.) – What’s a chunk? Why do we care? – What are implications? (recognition over recall, etc.) Other processes – what are they? (attention, learning) – What are the implications?

8. Interaction Review Command line WIMP Direction manipulation Pen & mobile Speech & natural language Issues, advantages, disadvantages, etc.

9. Prototyping – What’s vertical vs. horizontal? – What’s low vs. high fidelity? – What are various methods? Scenarios, mockups/sketches, etc. Issues and tradeoffs?

10. Prototyping Technique Wizard of Oz - Person simulates and controls system from “behind the scenes” – Use mock interface and interact with users – Good for simulating system that would be difficult to build Can be either computer-based or not

11. Wizard of Oz Method: – Behavior should be algorithmic – Good for voice recognition systems Advantages: – Allows designer to immerse oneself in situation – See how people respond, how specify tasks

12. Review Low-fidelity Medium-fidelityHigh-fidelity Sketches, mock-ups Slide shows Simulations System prototypes Scenarios Storyboards For more: take ITIS 3150 Rapid Prototyping and Interface Building Offered next fall

13. Summary Darn these hooves! I hit the wrong switch again! Who designs these instrument Panels, raccoon?!

14. Don Norman Professor at Northwestern and Principal of Nielsen Norman group Previously Professor at UCSD, senior positions at Apple & HP ACM/CHI Lifetime Achievement Award Prolific author http://www.jnd.org/

15. Discussion What did you take away from DOET book so far?

16. Here are some Affordances are important Minimize the gulf of interpretation and gulf of execution Use natural mappings Make state visible Use a conceptual model that makes sense Provide feedback

17. Daily Challenges How many of you can use all the functionality in your – VCR – Digital watch – Copy machine – Stereo system – Plumbing fixtures

18. Hall of Shame Example Leitz slide projector – To move forward, short press – To move backward, long press What happens when you get frustrated?

19. Fun Examples Phones How do you - transfer a call - change volume - store a number -...

21. Changing Ringer Volume Press “Program” Press “6” Set volume – Low - Press “1” – Medium - Press “2” – High - Press “3” Press “Program”

22. Much better…

23. Important Concepts Affordances Visibility Conceptual models Mapping Feedback Constraints

24. Affordances Perceived and actual properties of an object that determine how it could be used – Chair is for sitting – Button is for pushing – Door handle is for …. – Scroll arrow is for … – Icon is for …

25. Door Opening Affordances 12345 67 Which doors are easy to open? Which doors are hard to open? Why?

26. Affordances in interfaces Interfaces are virtual and do not have ‘real’ affordances like physical objects Interfaces have ‘perceived’ affordances – Learned conventions of arbitrary mappings between action and effect at the interface – Some mappings are better than others

27. Mantra Complex things may need explanation, but simple things should not – If a simple thing requires instructions, it is likely a failed design Norman’s 2 main principles – Provide a good conceptual model – Make things visible Affordances is part of this

28. Conceptual Models People build their own systems of how things work – Example - thermostat Designer can help user foster an appropriate conceptual model – Appearance, instructions, behavior...

29. Conceptual Models Mental models are not always right Two Classes: – Functional model Stimulus - response “Press the accelerator once, then turn the key” At surface or superficial level – Structural model Deeper sense of why it happens, not just what happens “Press the accelerator to engage the automatic choke on a carburetor”

30. Visibility When functionality is hidden, problems in use occur – Occurs when number of functions is greater than number of controls When capabilities are visible, it does not require memory of how to use – Recognition over Recall – in the world vs. in the head

31. Simple Example Bathroom faucets – Two functions Hot/cold Flow

32. Bathroom Faucets 1 Can you figure out how to use it? Are two functions clear and independent?

33. Bathroom Faucets 2 Can you figure out how to use it? Are two functions clear and independent?

34. Bathroom Faucets 3 Can you figure out how to use it? Are two functions clear and independent?

35. My parent’s microwave 5:45

36. My microwave

37. About that VCR… That old joke - “how many of you have a VCR that is blinking 12:00?” :-) Still true today :-(

38. Which is Faster for Setting Time?

39. Mapping Relationship between control and action/result in the world Take advantage of physical analogies or cultural understandings – Good: Car, various driving controls Mercedes Benz seat adjustment example – Bad Car stereo - Knob for front/back speakers

40. Which is better? or

41. Mapping Example: Euros Size::value

42. Mapping Example: Stove Which controls which?

43. Why not this?

44. Yikes!

45. Why Not Design Better Stove Speakers Physical, monetary, convenience, etc., constraints dictate otherwise

46. Feedback Sending information back to the user about what has been done Includes sound, highlighting, animation and combinations of these – e.g. when screen button clicked on provides sound or red highlight feedback: “ccclichhk”

47. Execution-Evaluation cycle Norman (DOET, p. 46) User Goals Physical System Gulf of Execution Gulf of Evaluation

48. Goals, Execution, Evaluation Physical System Goals What we want to happen Execution What we do to the world Evaluation Comparing what happened with what we wanted to happen (Gulf of Execution) (Gulf of Evaluation)

49. Execution Goals What we want to happen An intention to act so as to achieve the goal The actual sequence of actions that we plan to do The physical execution of that action sequence Physical System

50. Evaluation Goals What we want to happen Evaluation of the interpretations with what we expected to happen Interpreting the perception according to our expectations Perceiving the state of the world Physical System

51. Seven Stages - All Together Goals What we want to happen Evaluation of the interpretations with what we expected to happen Interpreting the perception according to our expectations Perceiving the state of the world An intention to act so as to achieve the goal The actual sequence of actions that we plan to do The physical execution of that action sequence Physical System

52. Implications – Which Gulf does these Address? Make current state and action alternatives visible Need good conceptual model with consistent system image Interface should include mappings that reveal relationships between stages User should receive continuous feedback Provide affordances

53. Goal: Minimize Gulfs Gulf of Execution – Conceptual model – Affordances – Natural mappings Gulf of Evaluation – Make state visible – Feedback

54. Try and Try Again Norman thinks that it often takes 5 or 6 tries to get something “right” Simply may not have that luxury in a competitive business environment