Contextual Design – The Basics and the Contextual Interview based on: Rapid Contextual Design by Holtzblatt, Wendell, & Wood Contextual Design by Beyer.

Slides:



Advertisements
Similar presentations
CVs & Telephone Skills Top Tips to remember …
Advertisements

Chapter 9 User-centered approaches to interaction design By: Sarah Obenhaus Ray Evans Nate Lynch.
Methods: Deciding What to Design In-Young Ko iko.AT. icu.ac.kr Information and Communications University (ICU) iko.AT. icu.ac.kr Fall 2005 ICE0575 Lecture.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday Consolidation Reading: CD Ch.s 8, 9, & 10 Modeling & Interpretation.
Interview Skills for Nurse Surveyors A skill you already have and use –Example. Talk with friends about something fun You listen You pay attention You.
Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 7: teams present research plan + a sequence diagram from phase 2 homework; Affinity.
1 Contextual Inquiry. 2 Hall of Fame or Hall of Shame? Gas pump display.
Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 6: analyzing work practices – rationale and challenges; the 5 Contextual Design work.
Contextual Inquiry Material Source: Professor John Landay, UCB.
An evaluation framework
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #3.
Data collection methods Questionnaires Interviews Focus groups Observation –Incl. automatic data collection User journals –Arbitron –Random alarm mechanisms.
Understanding and Representing Users A.J. Brush cse490ra January 22, 2003.
Administrivia Turn in ranking sheets, we’ll have group assignments to you as soon as possible Homeworks Programming Assignment 1 due next Tuesday Group.
Contextual Design. Purpose for us An example A term often used, with varying levels of precision.
Contextual Inquiry Katayoon Etemad November 2007.
1 Contextual Interview Shahnewaz A. Jolly CPSC 681: Research Methods in Human Computer Interaction Instructor: Dr. Saul Greenberg Date: November 4, 2009.
Effective Questioning in the classroom
Interviews By Darelle van Greunen.
1 Hole in the wall experiment Rural internet kiosks English ATMs used by paanwalas and peons NGOs importing used PCs for Indian schools Dabbawalas PCOs.
Z556 Systems Analysis & Design Session 9 ILS Z556 1.
Evaluation Framework Prevention vs. Intervention CHONG POH WAN 21 JUNE 2011.
Requirements Gathering. Why are requirements important? To understand what we are going to be doing We build systems for others, not for ourselves Requirements.
The UX Connection Driving Innovation on an Agile Project Hugh Beyer Cohealo.
Visioning ITM 734 Fall 2006 Corritore. 2 Visioning Goal – to create a vision of how your system will support your users’ work. * says what the new work.
Conducting an Interview
S556 SYSTEMS ANALYSIS & DESIGN Week 11. Creating a Vision (Solution) SLIS S556 2  Visioning:  Encourages you to think more systemically about your redesign.
Michael KwonJoel AzpeitiaKaren Yeung Alex Dodge Ryo KoyamaDanna LeeKrystin Tani Channelle Washington.
Process Walk & SIPOC Define Kaizen Facilitation. Objectives Understand the process as a “system” Describe the concept of an entity and how it relates.
Allison Bloodworth, Senior User Interaction Designer, Educational Technology Services, University of California - Berkeley October 22, 2015 User Needs.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Interview Techniques (Hand-in partner preferences) Thursday In-class Interviewing.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 5.1.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today System Design & Putting it Together Reading: ABF: Ch. 9 CD Ch.s 14, 15, 16,
Modeling Work and the Interpretation Session ITM 734 Fall 2006 Corritore.
User Interface Design & Usability for the Web Card Sorting You should now have a basic idea as to content requirements, functional requirements and user.
Task Analysis Methods IST 331. March 16 th
Collecting Qualitative Data
SBD: Analyzing Requirements Chris North CS 3724: HCI.
1 L545 Systems Analysis & Design Week 3: September 16, 2008.
S556 SYSTEMS ANALYSIS & DESIGN Week 6. Using Language to Focus Thought (cf., Wood, 1997) SLIS S556 2  The language gives you a way to see:  a framework.
©2001 Southern Illinois University, Edwardsville All rights reserved. CS 321 Human-Computer Interaction Today Consolidation Reading: CD Ch.s 8, 9, & 10.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 5: Requirements Determination.
Introduction to Usability Engineering Learning about your users (cont.): The field interview 1.
Today Next time  Interaction Reading: ID – Ch 2 Interaction  Introduction to HCI & Interaction Design Reading: ID – Ch. 1 CS 321 Human-Computer Interaction.
Z556 Systems Analysis & Design Session 10 ILS Z556 1.
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.
Computer/Human Interaction Spring 2013 Northeastern University1 Name of Interface Tagline if you have one (80 chars max, including spaces) Team member.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Putting it in Practice: CD Ch. 20 Monday Fun with Icons CS 321 Human-Computer.
Today Discussion Follow-Up Interview Techniques Next time Interview Techniques: Examples Work Modeling CD Ch.s 5, 6, & 7 CS 321 Human-Computer Interaction.
Continuous Improvement. Start Simple and Continually Improve E.g., Gmail Labels 1.
The Four Conversations: An Introduction
©2001 Southern Illinois University, Edwardsville All rights reserved. Today System Design: Reading: CD Ch.s 14, 15, &16 Monday Midterm CS 321 Human-Computer.
Learning about your users (cont.).: The field interview CS 352 Usability Engineering Summer 2010.
Computer/Human Interaction Fall 2015 Northeastern University1 Name of Interface Tagline if you have one Team member names and schools/years Team member.
Partnering to Progress K-5 Science Alliance April 14, 2009 Blue Licks State Park Come on In! Please help yourself to some refreshments and make sure you.
Week 2: Interviews. Definition and Types  What is an interview? Conversation with a purpose  Types of interviews 1. Unstructured 2. Structured 3. Focus.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Thursday Consolidation Reading: CD Ch.s 8, 9, & 10 In-class modeling exercise.
User-centered approaches to interaction design By Haiying Deng Yan Zhu.
CS160 Discussion Section Matthew Kam Feb 10, 2003.
Z556 Systems Analysis & Design Session 3 1 ILS Z556.
Introduction to Usability Engineering
From: A. Cooper et al.: About Face Andreas Rudin
Lecture 2: Discovering what people can't tell you: Contextual Inquiry and Analysis Methodology Brad Myers / : Introduction to Human Computer.
Introduction to Usability Engineering
Lecture 2: Discovering what people can't tell you: Contextual Inquiry and Analysis Methodology Brad Myers / : Introduction to Human Computer.
Learning about your users (cont.): The field interview
Introduction to Usability Engineering
Presentation transcript:

Contextual Design – The Basics and the Contextual Interview based on: Rapid Contextual Design by Holtzblatt, Wendell, & Wood Contextual Design by Beyer & Hotlzblatt Corritore, Fall 2006 ITM 734

Copyright 2006 John Wiley & Sons, Inc2 of 9 Contextual Design Customer-centered process that supports finding out how people work so that the optimal redesign of work practice can be discovered. Design: Intentional structuring of a system so that the parts work together coherently to support the work of people.

Copyright 2006 John Wiley & Sons, Inc3 of 9 Caveats Marketing data doesn’t provide design data Just justification – understanding what people will buy Design – want to know how people work and what they need to do this better. Eg. Installation is the #1 problem (marketing) What is wrong with the installation? (design)

Copyright 2006 John Wiley & Sons, Inc4 of 9 Caveats Intuition Designers have it – but they are not typical users (nor are developers) They aren’t the ones doing the work

Copyright 2006 John Wiley & Sons, Inc5 of 9 Caveats Customer will focus on a narrow fix Eg. What tweak to the system will overcome the problem I am having? (customer) What new concepts or features would make the system radically more appropriate to the job at hand? (designer)

Copyright 2006 John Wiley & Sons, Inc6 of 9 Caveats In CI avoid Interviewer-interviewee model Expert-novice (you the expert) Guest-host You are to be nosy, close, follow around, ask questions (ie. What was that phone call about?)

Copyright 2006 John Wiley & Sons, Inc7 of 9 The challenge Customer way of working is largely subconscious So can’t describe easily if at all Tend to describe it at high, summative level Design needs low-level details

Copyright 2006 John Wiley & Sons, Inc8 of 9 Contextual Inquiry Bottom line: go where the customer works, observe the customer as he/she works, and talk to the customer about the work. As customer works, artifacts and work processes jogs memory, illustrates mis- conceptions of designer, etc. They can talk about how they work as they do it

Copyright 2006 John Wiley & Sons, Inc9 of 9 Models for Successful Contextual Inquiries Apprentice-Master Model Focus on the details – ‘why are you doing that’ or ‘I’m doing this because …’ Learn the basic strategies involved as see them over and over Artifacts trigger conversation about how, when used Forms, papers, notes, etc.

Copyright 2006 John Wiley & Sons, Inc10 of 9 Apprentice-Master Model Incomplete Don’t want to learn how to do it – want to learn how it is done in order to improve and/or support it Four principles to guide extension Context Partnership Interpretation Focus

Copyright 2006 John Wiley & Sons, Inc11 of 9 Add Context Go to the customer’s workplace and see the work as it happens Ongoing experience, not summative (eg. What was that movie about?) Concrete rather than abstract data (lump together like activites – lose the details) Exception – Retrospective Account Retelling a past event If must, listen for what they are leaving out and fill in the holes

Copyright 2006 John Wiley & Sons, Inc12 of 9 Add Partnership Make you and customer collaborators in understanding his/her work – mutual relationship of shared inquiry and discovery of customer’s work Model: customer is working on something, interviewer watching the details – looking for pattern and structure – thinking about reasons behind customer’s actions. when something doesn’t fit model of interviewer, interrupt to talk about it – discuss with customer customer returns to working Attempting to make implicit things explicit If think of design solutions, go ahead and run them by customer – great opportunity can’t get them out of your head anyways! If say ‘huh’ or ‘what?’ or ‘ummm – could be’ you are on the wrong track

Copyright 2006 John Wiley & Sons, Inc13 of 9 Add Interpretation Assign meaning to the facts Facts alone don’t direct design – interpretation does Interpretation is the data you want to direct the design Eg. Accounting pkg, user kept a sheet of accounts and account numbers next to her screen. Perhaps …. acct numbers necessary but hard to remember? (way to cross- reference numbers and names in system) numbers unnecessary but a hold-over from paper systems and just need a way to refer to an acct uniquely (get rid of numbers, use unique names) Compatibility with paper systems needed, but referring to accts by name easier (keep numbers but use names)

Copyright 2006 John Wiley & Sons, Inc14 of 9 Add Interpretation Process From the fact (the observable event) Make a hypothesis (initial interpretation about what the fact means or the intent behind the fact) This hypothesis has implications for the design So leads to a design idea See previous example Can only validate interpretation by sharing with customer

Copyright 2006 John Wiley & Sons, Inc15 of 9 Add Focus Defines the point of view that interviewer takes while studying work Specific kind of work that is relevant to the design Use to keep conversation on track Gives team a uniform starting point Evolves over time Challenge your Assumptions (flags to indicate deviations) Surprises and contradictions – assume that everything they are doing is for a reason and is not unique Nods – dangerous – rather, assume that everything they do is new, something you have not seen before. Don’t understand – have customer explain

Copyright 2006 John Wiley & Sons, Inc16 of 9 Parts of the Contextual Interview 1. Conventional Interview Introduce self and project Confidentiality Permission to audiotape Customer and her work is primary Depend on her to teach you the work and correct your mis-understandings Get overview of work to be done that day 15 min.

Copyright 2006 John Wiley & Sons, Inc17 of 9 Parts of the Contextual Interview 2. Transition – State new rules for the contextual interview – customer will do his/her work while you watch, you will interrupt when you see something interesting or that you don’t understand If it’s a bad time to interrupt, customer can say 30 seconds

Copyright 2006 John Wiley & Sons, Inc18 of 9 Parts of the Contextual Interview 3. Contextual Interview – Audiotaping Copious notes Be nosy, follow around

Copyright 2006 John Wiley & Sons, Inc19 of 9 Parts of the Contextual Interview 4. Wrap-up Skim over your notes and summarize what you have learned (not verbatim) Last chance for customer to correct you

Copyright 2006 John Wiley & Sons, Inc20 of 9 Our project – start on this Lightning fast+ - Steps (pg. 39)

Copyright 2006 John Wiley & Sons, Inc21 of 9 Our project Setting Project Focus What is the work we expect to support? What is the work associated with the problem? How does this work fit into the customer’s whole work life? How is this work done now? Other products Paper and pencil – real world What activities are associated with the work? Given the work problem, what tasks do people do to complete the work? Start with your entering assumptions about the task Is this work like anything else? (metaphor) – What are the fundamental new characteristics introduced by the new technology? Boil down into key characteristics of the work – put on interview form Write on every page of interview notepad (use spirals)

Copyright 2006 John Wiley & Sons, Inc22 of 9 Our project Who does the work? Work group Job roles Job titles Context (see pg 69)

Copyright 2006 John Wiley & Sons, Inc23 of 9 Our project Who to interview? (N = 16 – 20; 3-4 per work role) Who is involved in making the work happen? Who are the informal helpers? Who provides the information needed to do the work? Who uses the results of the work? Maximize differences Recruiting – Sample recruiting script pg. 74 Thank you to interviewees

Copyright 2006 John Wiley & Sons, Inc24 of 9 Our project Problem analysis: Investigate the market space What are market expectations? Are they already using another product? Typical complaints? Requests? What are best practices? Competition? What are known issues, design ideas (work backwards on these), stakeholder concerns Communication – who, when, what Invite to interpretation sessions Progress reports

Copyright 2006 John Wiley & Sons, Inc25 of 9 Plan the Contextual Interview – start on this Conventional Interview – see pg. 76 Contact Info name, title, company name, division/unit/department, address, phone, Interview Info Subject No., interview date, interview time, interview location, directions to interview site

Copyright 2006 John Wiley & Sons, Inc26 of 9 Set up interviews Data Collection Sept. 26 (Tues) – Oct 8 Interpretation Oct. 2 and Oct. 9 Spring break Oct. 14 – 22

Copyright 2006 John Wiley & Sons, Inc27 of 9 Schedule Date(s)Activity Sept. 26 – Oct. 8Ten contextual field interviews Oct. 2 and Oct. 9Two Interpretation Sessions Oct. 23 and Oct. 30Work Modeling, Affinity Notes Consolidation, Affinity Diagrams Personas Walking the Affinity and Consolidated Sequences Nov. 6Visioning & Storyboarding Nov. 13Prototypes and Prototype Testing Nov. 20Final Presentation