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.

Slides:



Advertisements
Similar presentations
Don Norman’s User-Centered Design
Advertisements

Interaksi Manusia Komputer – Marcello Singadji. design rules Designing for maximum usability – the goal of interaction design Principles of usability.
Don Norman Worked for industry (Apple) Professor First published in 1988 Does not focus on computer interfaces Coined: user-centered design Goal: Motivate.
Ui design – general guidelines. Why designers go astray Putting aesthetics first: "It probably won a prize." Putting aesthetics first: "It probably won.
What is Design? Professor: Tapan Parikh TA: Eun Kyoung Choe
Good Design Visibility is key to interaction design Take advantage of affordances/constraints Provide a good conceptual model for the user.
Design of Everyday Things
CS147 - Terry Winograd - 1 Lecture 6 – Usability Terry Winograd CS147 - Introduction to Human-Computer Interaction Design Computer Science Department Stanford.
What is usability? Usability (1): effective, efficient and satisfactory Usability (2): Ease of learning (faster the second time and so on) Recall (remember.
Normans Principles Usability Engineering. Normans Principle Norman’s model of interaction is perhaps the most influential in human computer interaction.
April 19, 2004“Design of User-Friendly Systems” DLC, The Psychology of Everyday Actions “Humans will try to figure it out” A user sits down at an.
Design of Everyday Things Don Norman on Design & HCI.
Chapter 7 design rules.
Taking Responsibility You control (more then anyone else) how you perform in college.
Software Engineering: Analysis and Design - CSE3308
April 19, 2004“Design of User-Friendly Systems” DLC, Design of User Friendly Systems Joel Clawson Genevieve Hudak Brock LaMeres Kitty Turner.
© 2000 Franz Kurfess Cognitive Models 1. © 2000 Franz Kurfess Cognitive Models 2 Norman’s Cognitive Model [ Seffah ]
SIMS 213: User Interface Design & Development Marti Hearst Tues, Feb 11, 2003.
1 User Interface Design CIS 375 Bruce R. Maxim UM-Dearborn.
INTRODUCTION. Concepts HCI, CHI Usability User-centered Design (UCD) An approach to design (software, Web, other) that involves the user Interaction Design.
User Interface Evaluation CIS 376 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.
Principles of User Centred Design Howell Istance.
11 C H A P T E R Artificial Intelligence and Expert Systems.
Developing a Solution How to create the computer-based solution for a real-world problem. 1.
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.
Analysis of U-scan machines Group 4 Olivia Tran Jamie Tran Josh Wortman Calvin Hsu Oscar Guerrero Shawn Flynn Andrew Wong Todd Espiritu Santo.
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.
Fall 2002CS/PSY Design. Fall 2002CS/PSY System-Centered Design Focus is on the technology  What can be built easily using the available tools.
Design Rules-Part B Standards and Guidelines
Chapter 7- User Centered Design By: Atul Saboo Hardik Mishra Mohit Almal Pankaj Agarwal Sumeet Jalan.
1 3132/3192 User Accessibility © University of Stirling /3192 User Accessibility 2.
Chapter 7 design rules. Designing for maximum usability – the goal of interaction design Principles of usability –general understanding Standards and.
More on Design of Everyday Things. Turn it up, or shut it down?
The Design of Everyday Things Darn these hooves! I hit the wrong switch again! Who designs these instrument panels, raccoons?
Before Chapter 3… Chapter 2 (a bit more) Norman’s Seven stages of of action –Form the goal –Form the intention –Specify the action –Execute the action.
1 chapter 7 design rules. 2 Designing for maximum usability – the goal of interaction design Principles of usability –general understanding Standards.
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.
Theories and Practice of Interactive Media 13 October 2003 Kathy E. Gill.
The Design of Everyday Things Design Psychology (POET) Psychopathology.
Human Factors and Ergonomics I (056:144) Timothy L. Brown Adjunct Professor Department of Mechanical &Industrial Engineering.
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It describes what is a user doing or will.
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It specifies what functions the user will need.
Before Chapter 3… Chapter 2 (a bit more) Norman’s Seven stages of of action –Form the goal –Form the intention –Specify the action –Execute the action.
Today Discussion Follow-Up Interview Techniques Next time Interview Techniques: Examples Work Modeling CD Ch.s 5, 6, & 7 CS 321 Human-Computer Interaction.
Human Capabilities: Mental Models CS352. Announcements Project – your users: due next Wed. 7/7 Quiz #3 (human capabilities) next Tue. 2.
The Design of Everyday Things Donald A. Norman. The psychopathology of everyday things Doors Doors Light switches Light switches Taps Taps Telephones.
Copyright 1999 all rights reserved Evaluating Paper Prototypes n How do you do this? –What are the considerations? –What are the steps? ?
Chapter 7 design rules. Designing for maximum usability – the goal of interaction design Principles of usability –general understanding Standards and.
Design rules.
Human-Computer Interaction
Digital media & interaction design
design rules قواعد التصميم
SIE 515 Design Rules Lecture 5.
Good and Bad Interfaces
The Design of Everyday Things
HCI – DESIGN RATIONALE 20 November 2018.
Usability Techniques Lecture 13.
Norman 7 A: User-Centered Design
Discussion Nedas Matulionis 09/07/2018.
To Err is Human Owen Brennan.
CSE310 Human-Computer Interaction
Chapter 7 design rules.
Chapter 7 design rules.
Chapter 7 design rules.
User-Centered Design Data Entry CS 4640 Programming Languages for Web Applications [The Design of Everyday Things, Don Norman, Ch 7]
Chapter 7 design rules.
User-Centered Design Data Entry CS 4640 Programming Languages for Web Applications [The Design of Everyday Things, Don Norman, Ch 7]
Presentation transcript:

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 to remember that?” after the explanation.

7 principles of good design OR 7 principles for transforming difficult tasks into simple ones 1. Use both knowledge in the world and knowledge in the head. 2.Simplify the structure of the tasks. 3. Make things visible: bridge the gulfs of Execution and Evaluation. 4. Get the mappings right. 5. Exploit the power of constraints, both natural and artificial. 6. Design for error. 7. When all else fails, standardize.

Use knowledge in the world and knowledge in the head Users are more comfortable and learn better when the knowledge they need to perform a task is readily available in the world or through constraints. Users perform faster and more efficiently when they can synthesize the knowledge needed for their task. So it should be easy to go back and forth – to combine knowledge in the head with knowledge in the world. The designer must develop a conceptual model for the user that captures the important parts of the device and that is understandable by the user.

Simplify the structures of tasks The amount of planning and problem solving for a task should be minimized.

Make things visible On the execution side of an action: So that users know what actions are possible and how the actions can be done. On the evaluation side of an action: So that users know what the results of the actions are and the current state of the system.

Get the mappings right Make sure the user can understand the relationship between intentions and possible actions, actions and their effects on the system, the actual system state and what is reflected in the interface, and the perceived system state and the needs, intentions and expectations of the users.

Exploit the power of constraints, both natural and artificial Use natural and artificial constraints to make users feel that there is only one possible action.

Design for error Assume that any error is possible and plan for it. Allow users to recognize errors and recover from them. Make it easy to reverse operations and hard to do irreversible actions.

When all else fails, standardize When the above principles cannot be put into place, standardize the actions, layout, display, and results. With standardization, users only have to learn it once but they must be trained to the new standard.