---
title: Interviews
sr-due: 2022-04-22
sr-interval: 30
sr-ease: 247
---

#review 
#### Review questions

0. what type of questions should you avoid

2.  when/how are interviews used in needfinding

2. when/how are interview used in requirements elicitaion

3. when/how are interviews used in evaluating designs

---------------------------------
# Interviews
## Use Cases
- [Evaluating designs](content/notes/evaluating-designs.md)
- [Requirements elicitation](content/notes/requirements-elicitation.md)
- [Needfinding](content/notes/needfinding.md)

## 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

## Conducting an interview
### 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
		
#### 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

### 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

### 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

## 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