Semi-Structured Interviews: Uncover User Needs Through Conversation
A semi-structured interview is a guided conversation, not a rigid script, to uncover the 'why' behind user needs. Use it in discovery to define problems before designing.
Why it exists
To solve the problem of designing solutions without deeply understanding the people who will use them. Teams need to know users' lives, challenges, and motivations to create products that genuinely help. Without this foundational insight, you are just guessing at what users need.
The mental model
Think of it as being a journalist, not an interrogator. You have a topic and key questions, but the goal is to let the user's story unfold. You follow interesting threads with unplanned questions. It's a flexible structure that prioritizes depth and context over a rigid, uniform checklist.
How it works
The interviewer prepares a guide with open-ended questions but does not stick to it rigidly. During the one-on-one session, the interviewer asks questions, listens actively, and asks follow-up questions to probe deeper into the participant's experiences, feelings, and motivations. The focus is on creating a natural, warm conversation to gather rich qualitative data. This data is then analyzed to identify themes and insights, which can be used to create artifacts like personas or journey maps.
When to use it
Use this method in the early discovery or empathize stages of a project, before you have a design or even a clear solution. It's ideal for exploring a problem space, understanding user pain points, learning about their mental models, and gathering foundational knowledge to build from. For example, if you're building a calorie-tracking app, you'd interview people about their health journeys, not just about app features.
When not to use it
Do not use a semi-structured interview to evaluate a design. If you want to see if users can successfully complete a task in your prototype or find out what's not working in an existing interface, you need a usability test. Interviews gather what people say (attitudinal data), while usability tests observe what people do (behavioral data). Using an interview to ask "Do you think this button is easy to find?" is less reliable than watching if they can actually find it.
One canonical example
A team is tasked with improving a hospital's appointment scheduling system. Instead of immediately designing a new interface, they conduct semi-structured interviews with patients. They ask questions like, "Tell me about the last time you had to book a doctor's appointment. What was that experience like?" Through these conversations, they discover the primary pain point isn't the website, but the anxiety of not knowing if their insurance is accepted before booking. This insight shifts the project's focus from just UI tweaks to integrating insurance information upfront, a much more valuable solution.
Interview question
In which scenario would a semi-structured interview be the most appropriate research method?
- a.To assess the effectiveness of a new feature in a live product.
- b.To validate specific design choices by observing users interacting with a prototype.
- c.To gather statistical data on user satisfaction with an existing service.
- d.To uncover the underlying motivations and challenges users face before designing a solution.Correct
Why? this is the answer
Semi-structured interviews are designed to explore user motivations and challenges in the early discovery phase, before a solution is designed. Options A, B, and D describe scenarios better suited for usability testing, quantitative surveys, or post-launch evaluation, which focus on existing designs or statistical data rather than deep, qualitative understanding of user needs.
Just read this? Test yourself on what you have been reading.
Read the original → nngroup.com
- #ux research
- #qualitative research
- #discovery
- #user interviews
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 research — each one lists the topics its interview covers.
See open roles