quartz/content/notes/interviewing.md

title	tags
interviewing	info203

1 Use Cases

• evaluating-designs
• requirements-elicitation
• needfinding

2 Overview

• direct and stuctured
• semi structured
• usually top down
• effective for high level interface evaluation
• need careful planning, experts, difficult to analyse
• not a controlled experiment technique

3 Conducting an interview

3.1 Choosing participants

• some is better than none
• get pople who are representive of users
  • users of existing similar system
  • non-users -> why people arent using a system
  • e.g., lecture support system
    • teachers
    • students
    • staff
    • admins
    • parents
    • freshman
    • phd
    • international domestic
    • stronger and weaker

3.1.1 Recruiting

• Craiglist (in US)
• your network
• cheaper for less speciales users
• if you can convince people you are imporving the world they might volunteer
• if they think is is for profict they will expect to be paid
• if you cant pay -> you cant use a token of appreciation

3.2 Process

• introduce yourself explaint he purpose
• the interview is about them, not you?
• begin with open, unbiased questions-> then follow up
• ask the questions, and let them answer
• have breaks and give them time
• have a clear separation between the general introduction, the actual interview, and post inteview discussions

3.3 Questions to avoid:

• leading questions
• what would they do / like / want in a hypothetical scenario
• how often they do things
• how much they like things on an absolute scale
• avoid binary questions

4 Pros/cons

• free and open answers
• sense of active contribution
• oppportunity for follow up

• time consuming and resource intensive
• dependent of commication skills of analyst
• location/schedule can make this impractical