Chapter 3 Understanding users (adapted from the text’s materials)

Slides:



Advertisements
Similar presentations
Understanding users.
Advertisements

Chapter 11 Designing the User Interface
User Interfaces 4 BTECH: IT WIKI PAGE:
User-Centered Design and Development Instructor: Franz J. Kurfess Computer Science Dept. Cal Poly San Luis Obispo FJK 2005.
Chapter 3: Understanding users. Overview What is cognition? What are users good and bad at? Describe how cognition has been applied to interaction design.
Barbara white : interaction design Understanding users cognitive social affective.
Chapter 3: Understanding users. What goes on in the mind?
Knowledge in the Head and in the World
From requirements to design
Part 2c: Requirements Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain Chapter 4: Finding.
3. Memory and Human Computer Interaction. Memory memory 4 The multi-store model of memory describes how the processes of the stage model of HCI are interconnected.
Interaction Design Session 11 LBSC 790 / INFM 718B Building the Human-Computer Interface.
Chapter 3: Understanding users. Overview What is cognition? What are users good and bad at? Describe how cognition has been applied to interaction design.
Chapter 5 Attention and Memory Constraints Presentation By: Sybil Calvillo.
ICS 463, Intro to Human Computer Interaction Design: 4. Attention and Memory Dan Suthers.
User Interface Design Users should not have to adapt to a piece of software; the software should be designed to fit the user.
Chapter 3: Understanding users. Overview What is cognition? What are users good and bad at? Describe how cognition has been applied to interaction design.
1 Chapter 3: Understanding users 1. 2 FJK Copyright Notice These slides are a revised version of the originals provided with the book “Interaction.
Chapter 3 COGNITIVE ASPECTS.
Meaningful Learning in an Information Age
G063 - HCI Design Perception, Attention, Memory & Learning (PALM)
EQNet Travel Well Criteria.
1. Human – the end-user of a program – the others in the organization Computer – the machine the program runs on – often split between clients & servers.
Chapter 3 Understanding users.
Spring Chp.3: Understanding Users Considering (modeling) how “humans work” –want to see what humans are good and bad at and use this knowledge to.
©2011 1www.id-book.com Cognitive aspects Chapter 3.
CSC 480 Software Engineering Lecture 19 Nov 11, 2002.
Psychology: memory. Overview An understanding of human memory is critical to an appreciation of how users will store and use relevant information when.
Gary MarsdenSlide 1University of Cape Town Human-Computer Interaction - 7 Design Guidelines & Standards Gary Marsden ( ) July 2002.
Computer Science Department California Polytechnic State University San Luis Obispo, CA, U.S.A. Franz J. Kurfess CPE/CSC 486: Human-Computer Interaction.
Chapter 3: Understanding users Question 1 With a bit more added about personality theories!
Metaphors for Learning  Learning involves strengthening correct responses and weakening incorrect responses.  Learning involves adding new information.
Chapter 7 “___________ is the KEY for MEMORY” Qz. #4 pages System that allows for retention of what is learned.
AVI/Psych 358/IE 340: Human Factors Interfaces and Interaction September 22, 2008.
 How does memory affect your identity?  If you didn’t have a memory how would your answer the question – How are you today?
CSCD 487/587 Human Computer Interface Winter 2013 Lecture 4 Human Cognition.
1 CSC111H User Interface Design Dennis Burford
Comp 15 - Usability and Human Factors
Module 11 Types of Memory.
Understanding Users Cognition & Cognitive Frameworks
Usability 1 Usability evaluation Without users - analytical techniques With users - survey and observational techniques.
Human Abilities 2 How do people think? 1. Agenda Memory Cognitive Processes – Implications Recap 2.
Module 11 Types of Memory. INTRODUCTION Definitions –Memory ability to retain information over time through three processes: encoding, storing, and retrieving.
1 Cognitive aspects Chapter 3. 2 Overview What is cognition? What are users good and bad at? Describe how cognition has been applied to interaction design.
Yonglei Tao School of Computing & Info Systems GVSU Ch 7 Design Guidelines.
AVI/Psych 358/IE 340: Human Factors Cognition September
Chapter 3 COGNITIVE ASPECTS. What is cognition? How can it be described? There are various ways to talk about cognition
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Chapter 3: Understanding users. Overview What is cognition? What are users good and bad at? Describe how cognition has been applied to interaction design.
Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation ISE
Barbara white : interaction design Understanding users cognitive social affective.
Chapter 3: Understanding users Modified by E. Kraemer, 10/4/07.
IT323 - Software Engineering 2 1 Tutorial 3.  Suggest ways in which the user interface to an e-commerce system such as an online stores might be adapted.
Memory Chapter 4. Flashbulb Memories : are extremely vivid and apparently permanent memories. are typically of highly emotional and personal events. are.
Copyright 2006 John Wiley & Sons, Inc Chapter 5 – Cognitive Engineering HCI: Developing Effective Organizational Information Systems Dov Te’eni Jane Carey.
6. (supplemental) User Interface Design. User Interface Design System users often judge a system by its interface rather than its functionality A poorly.
Chapter 3 COGNITIVE ASPECTS. Overview What is cognition? What are users good and bad at? Describe how cognition has been applied to interaction design.
Chapter 3: Understanding users
CEN3722 Human Computer Interaction Cognition and Perception
Chapter 3 Understanding users
The User Lecture 2 DeSiaMore
الجوانب المعرفية Chapter 3 COGNITIVE ASPECTS.
CEN3722 Human Computer Interaction Displays
Chapter 3: Understanding users
Chapter 3 COGNITIVE ASPECTS.
Introduction UI designer stands for User Interface designer. UI designing is a type of process that is used for making interfaces in the software or the.
Human Computer Interaction
Cognitive Aspects of Design
Cognitive Aspects of Design
Presentation transcript:

Chapter 3 Understanding users (adapted from the text’s materials)

Topics What is cognition? Core cognitive concepts Conceptual frameworks for cognition Mental models External cognition

Why do we need to understand users? Interacting with technology is cognitive We need to take into account cognitive processes involved and cognitive limitations of users We can provide knowledge about what users can and cannot be expected to do Identify and explain the nature and causes of problems users encounter Supply theories, modelling tools, guidance and methods that can lead to the design of better interactive products

1. Bringing cognitive psychology knowledge to HCI

Core cognitive aspects Attention Perception and recognition Memory Reading, speaking and listening Problem-solving, planning, reasoning and decision- making, learning Here we focus on attention, perception & recognition, & memory

Attention Selecting things to concentrate on from the mass around us, at a point in time Focussed and divided attention enables us to be selective in terms of the mass of competing stimuli but limits our ability to keep track of all events Information at the interface should be structured to capture users’ attention, e.g. use perceptual boundaries (windows), colour, reverse video, sound and flashing lights

Design implications for attention Make information salient when it needs attending to Use techniques that make things stand out like colour, ordering, spacing, underlining, sequencing and animation Avoid cluttering the interface - follow the google.com example of crisp, simple design Avoid using too much because the software allows it

Perception and recognition How information is acquired from the world and transformed into experiences Obvious implication is to design representations that are readily perceivable, e.g. –Text should be legible –Icons should be easy to distinguish and read

Memory Involves encoding and recalling knowledge and acting appropriately We don’t remember everything - involves filtering and processing Context is important in affecting our memory We recognize things much better than being able to recall things –The rise of the GUI over command-based interfaces Better at remembering images than words –The use of icons rather than names

Multi-store model of memory Sensory store –Modality-specific, holds information for a very brief period of time (a few tenths of a second) Short-term memory store –Holds limited information for a short period of time (a few seconds: 7 ± 2) Permanent long-term memory store –Holds information indefinitely

The problem with the classic ‘7  2’ George Miller’s theory of how much information people can remember People’s immediate memory capacity is very limited Many designers have been led to believe that this is useful finding for interaction design

What some designers get up to… Present only 7 options on a menu Display only 7 icons on a tool bar Have no more than 7 bullets in a list Place only 7 items on a pull down menu Place only 7 tabs on the top of a website page –But this is wrong? Why?

Why? Inappropriate application of the theory People can scan lists of bullets, tabs, menu items till they see the one they want They don’t have to recall them from memory having only briefly heard or seen them Sometimes a small number of items is good design But it depends on task and available screen estate

More appropriate application of memory research File management and retrieval is a real problem to most users Research on information retrieval can be usefully applied Memory involves 2 processes –recall-directed and recognition-based scanning File management systems should be designed to optimize both kinds of memory processes

Mental models Users develop an understanding of a system through learning & using it Knowledge is often described as a mental model –How to use the system (what to do next) –What to do with unfamiliar systems or unexpected situations (how the system works) People make inferences using mental models of how to carry out tasks

Mental models Craik (1943) described mental models as internal constructions of some aspect of the external world enabling predictions to be made Involves unconscious and conscious processes, where images and analogies are activated Deep versus shallow models (e.g. how to drive a car and how it works)

External cognition Concerned with explaining how we interact with external representations (e.g. maps, notes, diagrams) What are the cognitive benefits and what processes involved How they extend our cognition What computer-based representations can we develop to help even more?

Externalizing to reduce memory load Diaries, reminders,calendars, notes, shopping lists, to-do lists - written to remind us of what to do Post-its, piles, marked s - where placed indicates priority of what to do External representations: –Remind us that we need to do something (e.g. to buy something for mother’s day) –Remind us of what to do (e.g. buy a card) –Remind us when to do something (e.g. send a card by a certain date)

Computational offloading When a tool is used in conjunction with an external representation to carry out a computation (e.g. pen and paper) Try doing the two sums below (a) in your head, (b) on a piece of paper and c) with a calculator. –234 x 456 =?? –CCXXXIIII x CCCCXXXXXVI = ??? Which is easiest and why? Both are identical sums

Annotation and cognitive tracing Annotation involves modifying existing representations through making marks –e.g. crossing off, ticking, underlining Cognitive tracing involves externally manipulating items into different orders or structures –e.g. playing scrabble, playing cards

Design implication Provide external representations at the interface that reduce memory load and facilitate computational offloading e.g. Information visualizations have been designed to allow people to make sense and rapid decisions about masses of data

Informing design based on our understanding of users How can we use knowledge about users to inform system design? Provide guidance and tools –Design principles and concepts –Design rules Provide analytic tools –Methods for evaluating usability

Mental models & system design Notion of mental models has been used as a basis for conceptual models Assumption is that if you can understand how people develop mental models then can help them develop more appropriate mental models of system functionality For example, a design principle is to try to make systems transparent so people can understand them better and know what to do

The design principle of transparency NOT to be understood as literal useful feedback easy to understand intuitive to use clear & easy to follow instructions appropriate online help context sensitive guidance of how to proceed when stuck

Key points Cognition involves many processes including attention, memory, perception and learning The way an interface is designed can greatly affect how well users can perceive, attend, learn and remember how to do their tasks The conceptual framework of ‘mental models’ and ‘external cognition’ provide ways of understanding how and why people interact with products, which can lead to thinking about how to design better products