Contextual Inquiry (Week 2) Flashcards
Contextual Inquiry (CI)
a method for gathering and representing data about the user and his/her work
“Contextual Design makes data gathering from the customer the base criterion for deciding what the system should do…”
“The core premise of Contextual Inquiry is very simple: go where the customer works, observe the customer as he or she works, and talk to the customer about the work. Do that, and you can’t help but gain a better understanding of your customer.”
The User is Not Like Me
Why not? Based on Norman:
Designers are much more familiar with the interface and with the problems being solved than users.
Designers are confident.
Users are often fearful.
Designers work in settings that are different than the context in which the product may be used.
Designers may have different skills than users (e.g., perceptual, cognitive, or domain skills).
CI: A hybrid process of discovery
Participatory design tradition from Europe
Interviews from social science
Think-aloud from cognitive psychology
Ethnography from anthropology
Brainstorming, stakeholders from business & design
Purposes of CI
- To obtain data from users in their context
2. To help define requirements, plans and designs & prioritize
Obtaining data from users in their context
- Insights about the users’ environment
- Insights about their many tasks
- Insights about the people they work with
- Insights about cultural influences on work (expectations, desires, policies, values, etc.)
- Understanding of breakdowns in current processes
The CI Approach
- Actions speak louder than words
2. Have conversations with users in the context of their work
Actions speak louder than words
People usually cannot say what innovations they would like and, even when they can, are sometimes wrong about what would be helpful (X-ray example, Beyer & Holtzblatt, 1996).
“Users of an X-ray machine kept asking for more and more exact speed controls on their X-ray machines, trying to run the image at exactly 1/4 second per frame. It was not until someone studied the work they were doing that they realized the users just needed a timer—they were trying to run the tape at an exact speed so they could measure elapsed time. The customers requested a technical fix to the existing system, but the real issue was in the structure of the work they were doing.”
Have conversations with users in the context of their work
“Direct observation” when possible
When not possible
- Cued recall of past experience
- Re-creation of related experience (e.g., think-aloud)
Principles of CI
- Context
- Partnership
- Interpretation
- Focus
Context
Must be done in the setting of the participant.
Partnership
Master/apprentice model; investigator is humble.
Interpretation
Observed facts must be regarded for their design implications. Raw facts without interpretation aren’t very useful.
Focus
Themes that emerge during the inquiry. You can’t pay attention to all facets of someone’s work at all times!
Master/Apprentice Model: Avoid these relationships…
- Interviewer / Interviewee
- Expert / Novice
- Guest / Host
Why avoid the Interviewer/Interviewee relationship in master/apprentice model?
Not based on context or ongoing activities
Why avoid the Expert/Novice relationship in master/apprentice model?
You are not the expert in the user’s work, they are!
Why avoid the Guest/Host relationship in master/apprentice model?
You shouldn’t be too afraid of asking the wrong question
Interview Data
- Go for concrete details obtained in-context, not abstract generalities
- Have them “think aloud” as they work through their tasks.
- Pepper them with short, easy-to-answer questions
Go for concrete details obtained in-context, not abstract generalities
Don’t ask participants to summarize their work. Ask them specific details about real, concrete, observable things