Identifying and Compensating for Biases in User Feedback A Case Study Team Chartreuse.

Slides:



Advertisements
Similar presentations
Chapter 5 Development and Evolution of User Interface
Advertisements

Requirements gathering
Object-Oriented Analysis and Design LECTURE 3: REQUIREMENTS DISCIPLINE.
Cognitive Walkthrough More evaluation without users.
ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.
What is Design? Professor: Tapan Parikh TA: Eun Kyoung Choe
Saul Greenberg CPSC 481 Foundations and Principles of Human Computer Interaction James Tam.
COMP 6620 Chapter Presentation Karthik Vemula. Agenda:-  User Centered Approach  Basic Activities of Interaction Design.  In Class Assignment.
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.
CS CS 5150 Software Engineering Lecture 12 Usability 2.
Usability presented by the OSU Libraries’ u-team.
Saul Greenberg CPSC 481 Foundations and Principles of Human Computer Interaction James Tam.
Graphical User Interfaces Design and usability Saul Greenberg Professor University of Calgary Slide deck by Saul Greenberg. Permission is granted to use.
Foundations and Principles of Human Computer Interaction Slide deck by Saul Greenberg. Permission is granted to use this for non-commercial purposes as.
Useability.
Paper Prototyping A tool for iterative design Wai Yong Low.
Evaluation Methodologies
Design and Evaluation of Iterative Systems n For most interactive systems, the ‘design it right first’ approach is not useful. n The 3 basic steps in the.
Identifying needs and establishing requirements Chapter 7b.
Course Wrap-Up IS 485, Professor Matt Thatcher. 2 C.J. Minard ( )
© Lethbridge/Laganière 2001 Chapter 7: Focusing on Users and Their Tasks1 7.1 User Centred Design (UCD) Software development should focus on the needs.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 20, 2005.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 22, 2004.
James Tam CPSC 481 Foundations and Principles of Human Computer Interaction James Tam.
Part 2: Requirements Days 7, 9, 11, 13 Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 18, 2007.
SE 555 Software Requirements & Specification 1 SE 555 Software Requirements & Specification Prototyping.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
Software Integration and Documenting
Human Interface Engineering1 Main Title, 60 pt., U/L case LS=.8 lines Introduction to Human Interface Engineering NTU Seminar Amy Ma HIE Global Director.
Predictive Evaluation
1 DENIM: An Informal Web Site Design Tool Inspired by Observations of Practice CS 376 – Research Topics in HCI 11/01/2005 Tony Tulathimutte.
+ Interaction Design User Centred Design. + Does the Interface Make sense? Characteristics of successful ID Products makes sense to the users when they.
Interaction Design Process COMPSCI 345 S1 C and SoftEng 350 S1 C Lecture 5 Chapter 3 (Heim)
Q Q Human Computer Interaction – Part 1© 2005 Mohammed Alabdulkareem Human Computer Interaction - 1 Dr. Mohammed Alabdulkareem
Visualizing Information in Global Networks in Real Time Design, Implementation, Usability Study.
2Object-Oriented Analysis and Design with the Unified Process The Requirements Discipline in More Detail  Focus shifts from defining to realizing objectives.
Usability and Internet Instruction INST 5240 Mimi Recker Utah State University.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Usability Evaluation June 8, Why do we need to do usability evaluation?
CS2003 Usability Engineering Human-Centred Design Dr Steve Love.
Requirement Elicitation Process Lesson 3. Requirements Elicitation  Is the process to find out the requirements for an intended software system by communicating.
Chapter 15: Analytical evaluation. Inspections Heuristic evaluation Walkthroughs.
User Interfaces 4 BTECH: IT WIKI PAGE:
Mario Čagalj University of Split 2014/15. Human-Computer Interaction (HCI)
Design Process … and some design inspiration. Course ReCap To make you notice interfaces, good and bad – You’ll never look at doors the same way again.
1 Chapter 8 Building the Analysis Model (1) Analysis Concepts and Principles.
Usability Evaluation. Objectives for today Go over upcoming deliverables Learn about usability testing (testing with users) BTW, we haven’t had a quiz.
Cognitive Walkthrough More evaluating with experts.
Introduction to Evaluation without Users. Where are you at with readings? Should have read –TCUID, Chapter 4 For Next Week –Two Papers on Heuristics from.
UML - Development Process 1 Software Development Process Using UML.
User Interface Evaluation Introduction Lecture #15.
In the news. Taxonomy Organizing Information Observation The Organization Project Scope Start the project Stakeholder Interviews Gather goals Focus groups.
Creating User Interfaces (Catch-up XML?) CMS, Usability checklist reports Preparation for user observation studies Blogs, Social Spaces, etc. Homework:
5. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the activities of the requirements discipline  Describe the difference.
Requirements Elicitation CSCI 5801: Software Engineering.
1 Design and evaluation methods: Objectives n Design life cycle: HF input and neglect n Levels of system design: Going beyond the interface n Sources of.
User-Centered Design Services for MSU Web Teams Sarah J. Swierenga, Director Usability & Accessibility Center MSU Webmasters 402 Computer Center February.
Project Breakdowns HCDE 492/592 Winter 2014.
Investigating System Requirements
User-centred system design process
Requirements Elicitation – 1
Cognitive Walkthrough
Introducing Evaluation
CS 321: Human-Computer Interaction Design
Informatics 121 Software Design I
PROJECT GROUP 1A IN4MATX 132 Group 1A.
CS 522: Human-Computer Interaction Lab: Formative Evaluation
Usability Techniques Lecture 13.
Cognitive Walkthrough
Presentation transcript:

Identifying and Compensating for Biases in User Feedback A Case Study Team Chartreuse

Walkthrough PayR is an iPhone app which aids restaurant goers in splitting bills. Split Bill EvenlySplit Bill by Item

A Model of Design Processing of Data GatherAnalyzeImplement External Input Design Representations

Design Process Concept Development Initial Feedback Formal Analysis Final Review User Studies Personas Values Idea Generation Paper Prototypes User Feedback Interpretation Concept Selection Redesign Cognitive Walkthrough Heuristic Evaluation Interpretation Redesign User Feedback Experiment Interpretation Final Design Gather Analyze Implement

Categories of Bias Background, Personal Preferences, Values, Technical Experience Intended use of product, Context of meals, How bills are paid Purpose of feedback, Location of session, Relations among participants, Prototype issues Who The Person Is What The Product is Used For Context Of Feedback Session

PAPER PROTOTYPE

Paper Prototype Context – Detailed Feedback vs General Feedback – Paper Prototype is “slower” than Software Prototype Who – Active Feedback vs Passive Feedback

HEURISTIC EVALUATION

Inconclusive Rewarding Scope Severity BIG small Low High Trivial

FINAL REFINEMENT

Tip Selection Experiment Four Test Cases – Slider snaps to 1% increments – Slider snaps to 5% increments – Slider snaps to values that make each person’s tip convenient to pay with cash – Slider snaps to tip values that make each person’s total bill convenient to pay with cash Observed ability to select desired tip amount and time taken to select desired tip

-Scenario based walkthrough of prototype - Non-Scenario based tip selection experiment Babson Interview -Babson student -Non Designer -Complementary Personality -Non-iPhone user -Final Prototype -Close Friend -Conducted at Babson in a friendly situation Who The Person Is What The Product is Used For Context Of Feedback Session

Observations -Scenario based walkthrough of prototype - Non-Scenario based tip selection experiment -Babson student -Non Designer -Complementary Personality -Non-iPhone user -Final Prototype -Close Friend -Conducted at Babson in a friendly situation Who Struggled with draging and keyboard layouts Context Of Feedback Session Technical Issues Personality Scenarios Usability TestTip Experiment Did not suggest interface changes despite struggling Context Who Context Tip selector did not afford sliding on computer Context Feedback based on what he was told to do, not what he wanted to do. Let user identify “What’s Important” Who Context Who Focuses on whether it works not how well it works

Results Identified 18 instances of “Analysis of External Input” Categorized based on the main bias corrected for Context What Who

What The Product is Used For 5 Instances – Heavily influenced by use of scenarios Main Sources of Bias – Occurred in “Tip Experiment” Merged results towards scenarios- based on observations What Intended use of product, Context of meals, How bills are paid

Who The Person Is 8 Instances – Influenced by use of scenarios Main Sources of Bias – Technical Knowledge (iPhone Specific) – Background of Individual (Designer vs Non-designer) Merged results towards that of personas Who Background, Personal Preferences, Values, Technical Experience

Context of Feedback Session 11 Instances Main Sources of Bias – Type of Prototype – Platform of Prototype (Computer vs iPhone) – Purpose of Feedback – Location of session Context Purpose of feedback, Location of session, Relations among participants, Prototype issues

Identifying and Compensating for Biases in User Feedback A Case Study Team Chartreuse