Human Capabilities: Mental Models

Slides:



Advertisements
Similar presentations
Psychology of Everyday Actions. 2 Projector Story DOET page 45.
Advertisements

Day 4 More on Information Design and Theories of human computer interaction.
Human Capabilities: Mental Models CS352. Announcements Notice upcoming due dates (web page). Where we are in PRICPE: –Predispositions: Did this in Project.
Design of Everyday Things
SIMS 213: User Interface Design & Development
About the final report and feedback on demonstrations Judy Kay CHAI: Computer human adapted interaction research group School of Information Technologies.
User-Centered Design Good design The user says “Yes, I see” or “Of course”. A simple explanation is sufficient. Bad design The user says “How am I going.
Design of Everyday Things Don Norman on Design & HCI.
About the draft report Judy Kay CHAI: Computer human adapted interaction research group School of Information Technologies.
About the final report and feedback on demonstrations Judy Kay CHAI: Computer human adapted interaction research group School of Information Technologies.
1 User Interface Design CIS 375 Bruce R. Maxim UM-Dearborn.
People: Usability IS 101Y/CMSC 101Y November 5, 2013 Marie desJardins Amanda Mancuso University of Maryland Baltimore County.
People: Usability COMP 101 November 12, 2014 Carolyn Seaman Amanda Mancuso Susan Martin University of Maryland Baltimore County.
Conceptual Models & Interface Metaphors. Objectives By the end of this class, you will be able to… Define conceptual model Identify instances where the.
Principles of User Centred Design Howell Istance.
Don Norman’s DOET Jim Rowan Georgia Gwinnett College ITEC 4130.
JENNIFER WONG CHAPTER 7: USER – CENTERED DESIGN. The point of the book was to advocate a user- centered design which is a philosophy that things should.
Human-Computer Interaction (HCI)
Design of Everyday Things. Grade summaries Assignments 1-4 (out of 10) P0 (out of 10) P1 group grade (out of 100) P1 individual grade (out of 50) Midterm.
Gulfs of Execution and Evaluation. A Bad Day for an Object User can’t act and can’t think –Broken mapping –Can’t achieve goals –No feedback.
The Design of Everyday Things Darn these hooves! I hit the wrong switch again! Who designs these instrument panels, raccoons?
Design of Everyday Things. Agenda Questions? Project Part 1: Now what? Test review One last bit on prototyping Design of Everyday Things.
Interaction Tasks Select Position Orient Quantify Text.
Understanding Users Cognition & Cognitive Frameworks
User and Task Analysis © Ed Green Penn State University Penn State University All Rights Reserved All Rights Reserved 12/5/2015User and Task Analysis 1.
Theories and Practice of Interactive Media 13 October 2003 Kathy E. Gill.
Evaluation (cont.): Heuristic Evaluation Cognitive Walkthrough CS352.
The Design of Everyday Things Design Psychology (POET) Psychopathology.
LECTURE 09: INTERACTION PT. 2: COST October 19, 2015 SDS235: Visual Analytics Note: slide deck adapted from R. Chang.
Mouse Trackball Joystick Touchpad TroughputError rate T roughput (bps) Error r ate (%) Image by MIT.
Human Capabilities: Mental Models CS352. Announcements Project – your users: due next Wed. 7/7 Quiz #3 (human capabilities) next Tue. 2.
How do people use an Interface Gabriel Spitz 1. User Interface Design?  Design is solving a problem  Design is creating an object or the means to enable.
The Design of Everyday Things Donald A. Norman. The psychopathology of everyday things Doors Doors Light switches Light switches Taps Taps Telephones.
Interaction Frameworks COMPSCI 345 S1 C and SoftEng 350 S1 C Lecture 3 Chapter (Heim)
Copyright 2006 John Wiley & Sons, Inc Chapter 5 – Cognitive Engineering HCI: Developing Effective Organizational Information Systems Dov Te’eni Jane Carey.
[The Design of Everyday Things, Don Norman, Ch 7]
Chapter 6 : User interface design
Are you a Left Brain or Right Brain?
Welcome to M301 P2 Software Systems & their Development
PeerWise Student Instructions
The Campaign Management Cheat Sheet
Image by MIT OpenCourseWare Troughput (bps) Error rate (%) Mouse Trackball Joystick Touchpad.
User-centred system design process
Human Cognition What is cognition? 1.
Concepts and Prototypes
FOP: Buttons and Events
Imran Hussain University of Management and Technology (UMT)
Software Engineering: A Practitioner’s Approach, 6/e Chapter 12 User Interface Design copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Interface Design Guidelines
Cognitive approach Lesson 6.
The Design of Everyday Things
Introduction to Engineering Oral Presentation Details
Desirable “-abilities” in HCI
Evaluation (cont.): Cognitive Walkthrough and Heuristic Evaluation
Introduction to Usability Engineering
Evaluation - Analytical Cognitive Walkthrough and Heuristic Evaluation
Chapter 15 User Interface Design
Human Capabilities: Mental Models
Dr. Rob Hasker SE 3800 Note 9 Reviews.
Norman 7 A: User-Centered Design
Generating and Choosing Solutions
Revision Strategy Cornell Method On How To Take Notes
OX Isaac Goldstein Ian Hodge Cody Hankins Mischa Nee
Perceiving the self and others….
Water Quality of Watershed
User-Centered Design Data Entry CS 4640 Programming Languages for Web Applications [The Design of Everyday Things, Don Norman, Ch 7]
Evaluation - Analytical Cognitive Walkthrough and Heuristic Evaluation
Evaluation - Analytical Cognitive Walkthrough and Heuristic Evaluation
User-Centered Design Data Entry CS 4640 Programming Languages for Web Applications [The Design of Everyday Things, Don Norman, Ch 7]
Overview of the course Mid-Term
Presentation transcript:

Human Capabilities: Mental Models

Hints: Team Process Improvement List risks and what you’ll do if they materialize. Agree on a process for working out disagreements in direction. We should use a web interface! No, we should use portable bar-code readers! eg: votes? eg: try both quickly with user? eg: joint visits to office hours? Do a post-mortem after every hand-in or grade received What went right in our process? Data, not finger-pointing: “we got an A-”. What went wrong in our process? Data, not finger-pointing: “we had to pull an all-nighter because we started too late” What will we do differently from now on? Write it down and revisit next time.

Mental Models = How to use the system (& how the system works). MENTAL: Users build these in their heads. Developed over time. Not always correct (and usually not complete). Thermostat example. Lightswitch example. Why do users build these? Rote mem is hard, explained-by memory easier. Mental model is an explanation. If user’s mental model is correct, will have an easier time using the system.

How to help user’s mental model be correct Remember Norman’s 2 Gulfs? Useful feedback in response to inputs (Evaluation). Ways of interacting with UI consistent with underlying workings (Eval+Exec). Context-sensitive devices for guidance (Execution). Activity: sketch a thermostat UI idea that does 1, 2, or 3.

How people do things: the 7 stages of an action Norman, at a conf in Italy. Speaker needed to show film, had trouble threading it into projector. Many people came up to help, none succeeded. Finally technical was called, who quickly threaded it correctly. Q: Why so hard? A: Structure of an action as relate to the Gulfs.

The 7 stages 1=goal. 2,3,4=execution. 5,6,7=evaluation.

The 7 stages (cont) 1 goal: “what” we want to do. Example. 2. execution intention (from what to how but top-level without details) 3. execution: sequence of actions. 4. execution: physically do them.

The 7 stages (cont.) 5. evaluation: perceiving (senses) what the world did in response (with our eyes, etc.) Example. 6. evaluation: interpreting (brain) the perception. 7. evaluation: comparison of interpretation with goal.

The 7 stages (cont.) Gulf of Execution. Gulf of Evaluation. How to get from 1 to 2, 2 to 3, or 3 to 4. Example. Gulf of Evaluation. How to get to 5 at all, 5 to 6, 6 to 7.

The 7 stages as design aids To find problems, apply these to any task in a UI: How easily can determine ... 1. My Goal 2. Exec: ...what relevant actions are possible? 3. Exec: ...map those actions to physical moves? 4. Exec: ...actually do the physical move? 5. Eval: ...what state the system is in? 6. Eval: ...what “that (feedback in UI)” means? 7. Eval: if system is in desired state? Could do example using Block-a-pix, the way I saw Ellie interact with it, but no need really because we did an example with the slide projector. * 1. color blocks st everything filled. 2. But WHAT FEATURES/ACTIONS are relevant here? 3. “You have to stretch the block”. to do that, grab it and pull 4. can’t grab it and pull. too high, doesn’t keep thumb down, etc., etc.

To find solutions Consider these remedies. Visibility: 2: Exec: ...what relevant actions are possible? Consider these remedies. Visibility: show what actions available (2). Good mappings revealing: relationships between actions and results (2), controls (causes) and effects (3), system state visible (5,6,7) Feedback every action provides immediate feedback of results (5,6,7) 3: Exec: ......map actions to physical moves? 5: Eval: ...in what state? 6: Eval: …what feedback means? 7: Eval: …in desired state?