
User Interviews

Core Method
Collected by Google

Some Design Sprints may include user interviews in the Understand phase to inject first-hand user perspectives into the Sprint. User interviews rely on stories to explore emotions,understand user goals, and assess needs. The goal of the interview is to gain empathy for the user’s experience. Through that empathy, we can shape the design solutions to fit the use better.
For example, if you are working on a new project on digital watches, you might want to know how people currently keep track of time. What do they use? What do they like? What is a pain point?
Two other, similar interview types to consider for your Design Sprint are Expert Interviews and Stakeholder Interviews.
STATS
Time
30-45 mins
Activity
Researcher & Participant
Sprint Type
New Product
Directions
- Recruit the users in advance of the sprint and prepare interview questions
- Allow extra time depending on whether the interviews are in-person or over a video conference
- Craft a strong introduction for the user to clarify the context of the interview
- Concentrate on the user’s experience with your product
- Ask about their likes and dislikes
- Ask questions that will elicit user stories rather than yes or no responses
- Make sure ⅔ of the interview is devoted to the user talking with your team listening