Contextual Inquiry Flashcards
Goals of CI
Get inside users head
see tasks the way that they do
pros of ci
rich data, context
cons ci
more intrusive, harder to analyze
Describe the master and apprentice model
master (user) works and talks
we interrupt to ask questions as they go
each step reminds master of the next
- data gathering in context
- better than asking user to summarize habits
skill knowledhe is usually not possible to write down
sometimes literal apprenticeship is best
How to gain context
conduct inquiry in a normal work environment
want details
keep it concrete
look for skipped steps and ask user to fill it in
describe the principles of partnership
stick with master apprentice
- dont teach
allows for more apprentice interaction
alternate watching and probing
How to interpret correctly
good facts are only the starting point
validate and rephrase
- check with user
- user is right by definition
- user uncomfortable until the phrasing is correct
commit to hear what is actually being said
Describe the principle of focus
steer converstation to stay on useful topics
respect triggers
Ways to take recording observations
audio/video recording
jottings
field not reflection
Analysis process of CI
start with notes and trasnscripts highlight interesting things tag quotes group organize - codes merge tags
How to go about task analysis
real tasks users have faced - collect required material
should provide reasonable coverahe
mixture of simple and complex tasks
How to use tasks in design
Write description of each task produce scenarios - task based - elaborated - full scale rough out interface - discard unnecesary interfaces - sketch majot screens and functions - not too detailed
Output of a task analysis
list of taks - description - easy/head - persona List of scenarios in which tasks will be performed - task based or more elaborate -consider uml scenarios - sketch
how to produce scenarios
task based
elaborate on task
