User Interviews: Uncover Needs, Not Just Test Designs
User interviews are structured conversations to understand the 'why' behind user actions, not just 'what' they do. Use them in discovery to learn user motivations and pain points, informing personas and journey maps.
Why it exists
Teams need to understand the people they're building for, not just assume their needs or rely on analytics alone. User interviews were created to get deep, qualitative insights into users' lives, challenges, and motivations, ensuring products solve real-world problems.
The mental model
A user interview is a semi-structured conversation, not a quiz or a sales pitch. The goal is to uncover a user's world: their experiences, pain points, and mental models. It's about listening more than talking and following up on interesting threads to understand the 'why' behind their actions.
How it works
An interview starts with clear research goals, not vague questions like 'learn about users.' The facilitator asks a participant open-ended questions about a topic or experience, listens carefully, and asks follow-up questions to dig deeper. The interaction is warm and conversational to build rapport. No design or prototype is shown; the focus is entirely on the user's past experiences and feelings.
When to use it
Use interviews in the discovery or 'empathize' phase of a project, before you have a concrete design. They are perfect for generating new knowledge and building team empathy for users. The insights gathered are foundational for creating UX artifacts like personas, empathy maps, user-need statements, and customer-journey maps.
When not to use it
Do not use an interview to evaluate a design's effectiveness. That's a usability test. Interviews are attitudinal (what people say), while usability tests are behavioral (what people do with a product). If you want to see if users can complete a task in your app, conduct a usability test. If you want to know about their life journey that led them to need an app like yours in the first place, conduct an interview.
One canonical example
Imagine you're building a calorie-tracking app. A user interview would not involve showing them the app. Instead, you'd ask questions like, 'Tell me about your journey to become healthier,' 'What have been the biggest challenges in tracking your food intake in the past?' or 'Describe a time you felt successful in managing your diet.' This reveals their motivations and pain points, which are more valuable for initial design than feedback on a specific button.
Interview question
When is a user interview most effectively utilized in the product development process?
- a.To evaluate the effectiveness and ease of use of a new design prototype.
- b.After product launch to gather quantitative data on user engagement metrics.
- c.In the initial discovery phase to uncover user motivations and challenges.Correct
- d.During the final stages to validate a fully developed product's market fit.
Why? this is the answer
User interviews are best used in the discovery or 'empathize' phase to understand the 'why' behind user actions and inform initial design. Option A describes a usability test, which is explicitly stated as a scenario when not to use interviews.
Just read this? Test yourself on what you have been reading.
Read the original → nngroup.com
- #ux
- #user research
- #discovery
- #product management
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on ux — each one lists the topics its interview covers.
See open roles