Stanford hci group / cs147 u 16 October 2007 Direct Manipulation and Mental Models Scott Klemmer tas: Marcello Bastea-Forte, Joel.

Slides:



Advertisements
Similar presentations
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica User interface Updated: December 2014.
Advertisements

CS0004: Introduction to Programming Visual Studio 2010 and Controls.
Understanding and conceptualizing interaction. Understanding the problem space –What do you want to create? –What are your assumptions? –Will it achieve.
Conceptual Models & Interface Metaphors. 2 Interface Hall of Fame or Shame? Tabbed dialog for setting options in MS Web Studio –more tabs than space to.
HCI 특론 (2007 Fall) Conceptual Models & Interface Metaphors.
1 Official Interface Guidelines by David Catmull User interface documentation published by Apple and Microsoft.
Design of Everyday Things Chapter One
Annoy Your Users Less Session 202 Philip Wolfe, Lead Developer Farm Credit Services of America.
CS774 Human-Computer Interaction Lecturer: Roger D. Eastman
Fall 2002CS/PSY Design of Everyday Things Agenda Discuss Norman’s views on HCI & design Discussion What did you take away from DOET book.
Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.
Design of Everyday Things
SIMS 213: User Interface Design & Development
Heuristic Evaluation. Sources for today’s lecture: Professor James Landay: stic-evaluation/heuristic-evaluation.ppt.
Part 3: Design Days 15, 19, 21, 23 Chapter 8: Work Reengineering and Conceptual Design Chapter 9: Design Guidance and Design Rationale Chapter 10: Interaction.
Lecture 7 Date: 23rd February
Psychological Aspects Presented by Hanish Patel. Overview  HCI (Human Computer Interaction)  Overview of HCI  Human Use of Computer Systems  Science.
Ch 7 & 8 Interaction Styles page 1 CS 368 Designing the Interaction Interaction Design The look and feel (appearance and behavior) of interaction objects.
Design Principles, Guidelines and Metaphor Howell Istance Department of Computer Science De Montfort University.
0 HCI Today Talk about HCI Success Stories Talk about HCI Success Stories Talk about Norman’s Paper Talk about Norman’s Paper Start talking about The human.
User Interface Design Users should not have to adapt to a piece of software; the software should be designed to fit the user.
Design of Everyday Things Don Norman on Design & HCI.
10th Workshop "Software Engineering Education and Reverse Engineering" Ivanjica, Serbia, 5-12 September 2010 First experience in teaching HCI course Dusanka.
Conceptual Models & Interface Metaphors Working as a Team*
Learning About Technology Chapter 2. 2 Learning New Tools How do you learn to use new tools?  Read the instruction manual Programming a VCR Cooling my.
Stanford hci group / cs147 u 25 September 2007 Information Design Scott Klemmer tas: Marcello Bastea-Forte, Joel Brandt, Neil.
1 ISE 412 Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation.
Prof. James A. Landay University of Washington Autumn 2008 Conceptual Models & Interface Metaphors October 23, 2008.
The psychology of design: Models
Introduction to Usability Engineering CS 352 Winter
Stanford hci group / cs147 u 04 October 2007 Intro to Human- Computer Interaction Design Scott Klemmer tas: Marcello Bastea-Forte,
CSCW Prof. Klemmer · Autumn 2007 Source:.
1 Human-Computer Interaction  Design process  Task and User Characteristics  Guidelines  Evaluation.
Human Computer Interaction An Introduction. Human-Computer Interaction "Human-computer interaction (HCI) is the study of the interaction between people,
SCV2113 Human Computer Interaction Semester 1, 2013/2013.
Prof. James A. Landay University of Washington Autumn 2004 Conceptual Models & Interface Metaphors October 7, 2004.
User Interface Design Main issues: What is the user interface How to design a user interface ©2008 John Wiley & Sons Ltd.
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.
Stanford hci group / cs October 2007 Fitts and GOMS Scott Klemmer (sub: Anoop Sinha) tas: Marcello Bastea-Forte, Joel Brandt,
AVI/Psych 358/IE 340: Human Factors Interfaces and Interaction September 22, 2008.
Chapter 2.2 Game Design. CS Overview This introduction covers: –Terms –Concepts –Approach All from a workaday viewpoint.
INFO 355Week #71 Systems Analysis II User and system interface design INFO 355 Glenn Booker.
Bringing it together Humans Computers Interaction Paradigms Design HCI in software development Design Rules Implementation Support – to come.
Stanford hci group / cs147 Intro to HCI Design Midterm Review Session November 2/
The Design of Everyday Things Darn these hooves! I hit the wrong switch again! Who designs these instrument panels, raccoons?
Interaction Tasks Select Position Orient Quantify Text.
Fall 2002CS/PSY Dialog Design 2 Direct Manipulation 1) Continuous visibility of the objects and actions of interest 2) Rapid, reversible, incremental.
Prof. James A. Landay Computer Science Department Stanford University CS 147 Autumn 2015 DESIGN THINKING FOR USER EXPERIENCE DESIGN + PROTOTYPING + EVALUATION.
Yonglei Tao School of Computing & Info Systems GVSU Ch 7 Design Guidelines.
Stanford hci group / cs147 u 27 November 2007 Ubiquitous Computing & “Natural” Interaction Scott Klemmer tas: Marcello Bastea-Forte,
Prof. James A. Landay University of Washington Autumn 2007 Conceptual Models & Interface Metaphors October 10, 2007.
Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation ISE
Mouse Trackball Joystick Touchpad TroughputError rate T roughput (bps) Error r ate (%) Image by MIT.
Review assessment two and three Design and develop an interactive, multimedia application to meet the documented requirements of an identified client.
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.
Design CSE 403. Announcements Design How do people interact with computers? Tremendous flexibility in designing/building interactions Look at physical.
Interaction Frameworks COMPSCI 345 S1 C and SoftEng 350 S1 C Lecture 3 Chapter (Heim)
Introduction to Human Factors in Information Systems Dr. Cindy Corritore Creighton University ITM 734 Fall 2005.
Stanford hci group / cs October 2007 An Overview of Design Process Scott Klemmer tas: Marcello Bastea-Forte, Joel Brandt,
6. (supplemental) User Interface Design. User Interface Design System users often judge a system by its interface rather than its functionality A poorly.
Stanford hci group / cs147 u 18 October 2007 Representations Scott Klemmer tas: Marcello Bastea-Forte, Joel Brandt, Neil Patel,
CS 3120 USER INTERFACE DESIGN, IMPLEMENTATION AND EVALUATION (UIDIE)
Conceptual Models & Interface Metaphors
Image by MIT OpenCourseWare Troughput (bps) Error rate (%) Mouse Trackball Joystick Touchpad.
Conceptual Models & Interface Metaphors Introduction to Human Computer Interaction & Design Hao-Hua Chu National Taiwan University Dec 12, 2016 *** Adapt.
The Design of Everyday Things
Dialog Design 2 Direct Manipulation
User-Centered Design Data Entry CS 4640 Programming Languages for Web Applications [The Design of Everyday Things, Don Norman, Ch 7]
User-Centered Design Data Entry CS 4640 Programming Languages for Web Applications [The Design of Everyday Things, Don Norman, Ch 7]
Presentation transcript:

stanford hci group / cs147 u 16 October 2007 Direct Manipulation and Mental Models Scott Klemmer tas: Marcello Bastea-Forte, Joel Brandt, Neil Patel, Leslie Wu, Mike Cammarano

 How do people learn interactive systems?  What makes an interface easy or hard to remember?  Why do people make errors?

Scott Adams deletes all 500 comments in blog  Dear Tog:  Scott Adams moderated 500 comments to his blog and then deleted them permanently despite prominent warnings about permanent deletion. Whose fault was it?  ~Veky  Not Scott  A chain of five errors led to Scott Adams losing his work. Not one of those errors was his. They had been made months and even years before Scott Adams ever started work on his blog. His was an accident waiting to happen, an accident that has almost certainly befallen a large number of other individuals who have had the misfortune to use the same software. Source: Toggazini, Bruce. “The Scott Adams Meltdown: Anatomy of a Disaster”.  Error One: User Model didn't reflect the Design Model  Scott Adams believed that there were two documents holding his comments… there was only one database.  Error Two: Misleading metaphor  “Publish” [used to mean]… the mass replication and distribution of a document…. [some developers] decided to drastically redefine “publish” to “set a little flag.”  Error Three: Confirmation Dialogs Ambiguous  dialogs kept warning Scott Adams about destroying what he considered now-useless information. Of course, he Okayed them.  Error Four: Confirmation Substituted for Undo  Often, developers wanting to avoid undo will throw in a confirmation dialog instead…. The only effect of such dialogs is to make the developers feel good: “The users may be screwing up, but we warned them, so it is their own fault.”  Error Five: No Usability Evaluation

Marr’s 3 Levels of Representation  Computational (semantic, content)  Algorithmic (syntactic, form)  Implementational (physical, medium)

What is a Mental Model?  “defined inputs and outputs that lead to a believable process which operates on the inputs to produce outputs.”

What kinds of models?  My own behavior  Someone else’s behavior  A software application  …or any information process that’s mediated

Learning Mental Models  “A text processor is a typewriter”  “Indeed, the models that learners spontaneously form are incomplete, inconsistent, unstable in time, and often rife with superstition”  Olson and Carroll

The Design of Everyday Things Source: Norman, Don. The Design of Everyday Things. Currency, Examples

ON DOORS & AFFORDANCES

Users / designers communicate through their mental models  Designer’s model = mental/conceptual model of the system  User’s model = mental model developed through interaction with the system  Designer expects user’s model to be the same as the designer’s model  But often it isn’t! Source: Norman, Don. The Design of Everyday Things. Currency, 1990.

Conceptual Model Mismatch  Mismatch between designer’s & user’s conceptual models leads to…  Slow performance  Errors  Frustration ...

The gap : the gulfs of execution & evaluation  The right mental model can reduce the gulfs Source: Norman, Don. The Design of Everyday Things. Currency, 1990.

Good design reduces the gaps Source: Norman, Don. The Design of Everyday Things. Currency, 1990.

Examples (Bad) : Old Refrigerator Problem: freezer too cold, but fresh food just right freezer fresh food Source: Norman, Don. The Design of Everyday Things. Currency, James Landay, CS160 UC Berkeley, Mental Models Lecture.

Example (bad): Refrigerator Controls What is your conceptual model? A B C D E Normal SettingsC and 4 Colder Fresh FoodC and 5-6 Coldest Fresh FoodB and 7 Colder FreezerD and 6-7 Warmer Fresh FoodC and 3-1 OFF (both)0 Source: Norman, Don. The Design of Everyday Things. Currency, James Landay, CS160 UC Berkeley, Mental Models Lecture.

Example (bad): Most Likely Conceptual Model i.e., independent controls A B C D E cooling unit cooling unit Source: Norman, Don. The Design of Everyday Things. Currency, James Landay, CS160 UC Berkeley, Mental Models Lecture.

Example (bad): Actual Conceptual Model Now can you fix the problem? A B C D E cooling unit Source: Norman, Don. The Design of Everyday Things. Currency, James Landay, CS160 UC Berkeley, Mental Models Lecture.

Principles of mental models  Controls mapped to actions in an understandable way  affordances disclose how to performing an action  sense making: user problem solving allows the user to make sense of the interface  analogies / examples play a key role in communicating how a design works Source: Norman, Don. The Design of Everyday Things. Currency, Klemmer, Scott, Examples Research.

Direct manipulation  Immediate feedback on actions  Continuous representations of objects  Real world metaphors / mental models  Direct manipulation can minimize the gap Source: Hutchins, Edwin L.. James D. Hollan, and Donald Norman.Direct manipulation interfaces. (1985). Shneiderman, Ben. "Direct manipulation: a step beyond programming languages," IEEE Computer 16(8) (August 1983),

Notorious Example

What happens in good designs  Good idea of how each object works and how to control it  Interface itself discloses how it is used  The art in design is to translate users cognitive capabilities and existing mental models into interfaces that work! Source: Norman, Don. The Design of Everyday Things. Currency, 1990.

Example (good) Source: Mercedes S500 Car Seat Controller

Make Things Visible  Refrigerator (?)  make the A..E dial something about percentage of cooling between the two compartments?  Controls available on watch w/ 3 buttons?  too many and they are not visible!  Compare to controls on simple car radio  #controls = #functions  controls are labeled (?) and grouped together

 Control should mirror real-world  Which is better for dashboard speaker front / back control? Dashboard Map Interface Controls

Evolution of Windows Source: Xerox, Apple, Microsoft, Wikipedia Xerox Star Windows 3.1 Mac OS Windows Vista

COMMAND LINE v. GUI

Desktop to mobile… Source: Microsoft, Wikipedia Original Microsoft Palm PC Windows Mobile 6

Paper Flight Strips visibility

E-Voting visibility

“If technology is to provide an advantage, the correspondence to the real world must break down at some point.” - Jonathan Grudin

NEW TECHNOLOGY minimize this distance CURRENT PRACTICE

Medical Records thick practice

Final Scratch thick practice

Announcements  Individual grades and aggregate statistics are posted for assignments 1 & 2  Attendance is posted for studios 1-3  Assignment 3 grades will be posted tomorrow  You can view all of this on the studio page  with any questions (errors are most likely due to studio shifting)

Further Reading  Mental Models  Olson and Carroll 1984  Gentner and Stevens, Mental Models  Errors  Norman, Design of Everyday Things (chapter _)  Norman, Things that Make Us Smart (chapter 5)  Norman, Design Rules based on analyses of human error  James Reason, Human Error  Direct Manipulation  Shneiderman  Hutchins, Hollan, Norman