Structuring your UX research interview questions
What are some questions to ask in a UX design interview? There are a couple of ways one can structure your session. One possible flow is as follows: 1) Understanding user impressions or expectations; 2) User testing particular tasks; 3) End-of-session follow-up questions
1. Understanding impressions or expectations
The aim of these questions is to understand what sentiments users have towards the product, feature, or interface.
- What do you think about as you look at this?
- What is your impression of this?
- What do you think the product does?
- When will someone use this?
- What do you hope to gain from the use of this product?
- What stops you from using this product?
- When and where do you think someone will feel
More specific, goal-driven questions can also be considered:
- Descriptive: Could you walk me through your purchase decision as a customer?
(Experience-based answer shared in a form of a story)
- Intuitive: What frustrates you the most during the purchase process?
(Watch for shifts in emotional tone and facial expression)
- Validation driven: Does this product solve the problem you just described in the specific situation?
(Yes/No. Why not?)
- Data-driven: How often would you hire this product to get the job done? (Frequency-based response)
On a scale of 1 to 10, how likely will you recommend this product to a friend? (Metric based response)
- Comparative: What are the pros and cons of a competitor’s product?
How are you dealing with (the problem)?
- Open-ended: If I were to give you a magic wand to change anything in this product what will you change?
2. User testing particular tasks
During the session, you can also ask task-driven feedback questions or get your interviewees to perform specific tasks within the session. However, unlike the general questions from before, user testing questions require a product prototype for users to use or look through. Thus, this part is optional depending on the stage of the UX design process this interview is conducted at.
Some general task-driven questions are as follows:
- How will you approach the task?
- What did you expect to happen when you performed the task?
- How else will you approach the task?
- Did anything surprise you or fail to perform as expected?
- Was the interface intuitive and easy to access and understand?
- What was the most difficult task?
- What was the simplest task?
Getting users to execute scripted tasks provide insights on the usability of the product and the user’s comprehension of the product’s interface. Weaving in scripted tasks within your session identifies issues related to user interactions with interfaces and confirming perceptions towards how the interface is used and how it works. Some examples include:
- Locating information on a website or page.
- Navigating from one point to another within the interface
- Make edits to your profile
- Record a video of yourself utilising the interface.
Take note of the number of tasks that your user completes or fails and ask your user to rate and provide feedback after every task. This could be done using scaled responses.