Contents
How do you conduct a user interview for product management?
How to Conduct User Interviews for UX Research and Product Development
- Communicate the need for user interviews to stakeholders.
- Find users to interview.
- Prepare the questions and an interview workflow. Create a field guide. Make respondents comfortable.
- Extract insights. Create a Topline Report.
- Final word.
How do you conduct a good user interview?
Make your interviewee comfortable – dress in a manner similar to them (you in a suit them in a tracksuit is going to make it feel like a job interview rather than a user test), make sure they understand you are testing a product or an idea and not the user themselves, offer them a drink (non-alcoholic), conduct a …
How many participants do you need for user interview?
There’s no industry consensus on this. Generally, most researchers find that they get what they need after somewhere between 6–12 interviews. Personally, I’ve found that after 5 or 6, you just start hearing the same things over and over. If you’re not sure how many to do, I would start with 5 and then see how you feel.
What comes after user interviews?
After all of the interviews and observations have been carried out, schedule a time for you and your team to enter a space for debriefing. Debriefing is meant to be carried out in an informal environment. It’s a conversation to learn from each other’s experience and improve the fundamental UX process as a team.
How long is a user interview?
Interviews should, ideally, be less than 1 hour long and the majority of the time spent should be the interviewee talking and the researcher listening.
When to conduct an interview with a user?
This is an interview which is conducted after (or during) the observation of a user using the actual product. It’s an interview “in context” with usage. These are very common in usability testing and assessment of products and even in information visualization. Author/Copyright holder: RezScore.
How many questions to ask in a user interview?
Our user interview scripts range from about 15 questions to upwards of 40. This will depend on how complex the product is, or if we are doing an interview about the entire product or just part of the product. Previously I mentioned that user interviews are more valuable earlier on in the user-centered design process.
How are user interviews used in the UX industry?
UX Interviews tend to be a quick and easy way to collect user data, so they are often used, especially in Lean and Agile environments. They are closely related to journalistic interviews and to the somewhat narrower and more formal HCI method called the critical incident technique, which was introduced in 1954 by John Flanagan.
Why are user interviews important in interaction design?
Interviews, even if they are contextual (e.g. based on observing the interviewee using the product prior to interview), tend to give insights into what people say they will do and this is sometimes (often even) not the same as what they actually do. Human beings have memory issues and can often not recall details as clearly as they would like.