Latest / 5 Minute UX / How To Structure a User Interview
Transcript
- 0:08This lesson is How To Structure a User Interview. Let's get
- 0:11started.
- 0:19You start by locking in a forty- five to sixty-minute window.
- 0:21That duration balances building rapport with avoiding
- 0:24participant fatigue, so the conversation stays productive
- 0:26without dragging. You then choose a semi-structured format,
- 0:29which means you begin with a list of questions but allow the
- 0:32conversation to follow a natural path. This flexibility lets you
- 0:35probe interesting comments without forcing a rigid script.
- 0:37Next, you select the environment from four options: over the
- 0:40phone, via video webconferencing tools like GoToMeeting or Skype,
- 0:43in a neutral in-person location, or ideally in the user's actual
- 0:46usage environment. Prioritizing that last option enables
- 0:48contextual inquiry alongside the interview. It grounds the
- 0:51discussion in the real settings where the user interacts with
- 0:54the site. This setup frames the session for rich qualitative
- 0:57data. With the scope and location defined, you can move
- 0:59to designing the questions that will drive the conversation.
- 1:08When you draft your question list, ground every item in the
- 1:10participant's personal past experiences. You want them to
- 1:13recall what actually happened, not predict what might happen.
- 1:16Speculation about future actions or other people’s behavior
- 1:19rarely predicts actual behavior, so you strip that out entirely.
- 1:22This means eliminating leading questions that push the
- 1:24participant toward a positive or negative answer. For example,
- 1:27asking "What do you like about pseudoCorporation.com?" implies
- 1:30there is something to like, which biases the data. Instead,
- 1:33keep your tone simple, neutral, and open-ended. This approach
- 1:36ensures you gather unbiased qualitative data without
- 1:38steering the conversation. By focusing strictly on past
- 1:41behavior and removing directional cues, you maintain
- 1:44the integrity of the insights you collect.
- 1:51The content of your interview rests on four distinct areas of
- 1:54inquiry. First, you need to uncover the participant's
- 1:57relevant experience with the site or the subject matter
- 1:59itself. You are looking for concrete history, not
- 2:01hypotheticals. Second, you assess the company’s brand
- 2:03exactly as the participant experiences it. This extends to
- 2:06their attitudes toward specific subject categories or the design
- 2:09process you are building. These are the mental models they are
- 2:12bringing to your table. Third, you identify the common goals or
- 2:14needs that drive users to your site, or to a competitor's.
- 2:17Understanding this motivation tells you why they are there in
- 2:20the first place. Finally, you map the common next steps users
- 2:22take after visiting. This includes identifying other
- 2:25people involved in the experience, such as whether the
- 2:27user collaborates with someone else to achieve a larger goal.
- 2:30These four areas form the backbone of your question list.
- 2:32Once you have drafted questions for each, you can begin the
- 2:35deeper work of probing.
- 2:42When a participant shares an unexpected detail, your job
- 2:44shifts from asking the next planned question to digging
- 2:46deeper. This is where follow-up probing questions earn their
- 2:49keep. You want to explore that interesting comment fully, which
- 2:51reveals the reasoning behind their behavior rather than just
- 2:54the behavior itself. Think about where this interview sits
- 2:56in your larger project. For task-based applications, you
- 2:58conduct these interviews before design to gather initial
- 3:01insights, then follow up later with usability testing on a
- 3:03prototype. If you are working on a content source, you pair the
- 3:06interview with card sorting exercises to inform
- 3:08categorization decisions before running tests on the final
- 3:10structure. As you wrap up the forty-five to sixty-minute
- 3:12session, you should ask the stakeholder if there is time for
- 3:15a follow-up interview. This allows you to cover additional
- 3:17topics that didn't get addressed or continue a discussion that
- 3:20felt too rushed. If the participant found value in the
- 3:22time you spent together, they will likely agree to that second
- 3:24session. With your probing strategy and closing protocol
- 3:27set, you can now draft a question list that covers all
- 3:29four core content areas: experience, brand, attitudes,
- 3:31and goals.
- 3:37[pause:1s] So, here is where the plan meets the participant.
- 3:40You draft a question list that covers the four core content
- 3:43areas: relevant experience, brand perception, attitudes, and
- 3:45shared goals. Then, you review each drafted question to ensure
- 3:48it is neutral, open-ended, and focused on past behavior. If a
- 3:51question sounds like "What do you like about
- 3:53pseudoCorporation.com?", it is leading, and you have to rewrite
- 3:56it. Instead, ask about the specific actions they took last
- 3:58time they visited. Next, you select the most appropriate
- 4:01environment from the four options. Phone, video, a neutral
- 4:03room, or the user's actual usage context. If you need to observe
- 4:06how they navigate the interface while using it, you have to
- 4:09prioritize that physical setting over a conference room.
- 4:11Finally, you plan the timeline. Forty-five to sixty minutes
- 4:14gives you room for rapport building, the core questioning,
- 4:16and the probing. At the end, you ask if there is time for a
- 4:19follow-up interview. When you execute this framework, the data
- 4:22you collect is rich, qualitative, and ready to shape
- 4:24your personas.
- 4:28Welcome to The Take. I'm joined by a fellow practitioner and
- 4:30together we're going to dig into How To Structure a User
- 4:33Interview — what it means in practice and what's worth
- 4:35remembering.
- 4:37[HOST] I keep coming back to the instruction to strip out future
- 4:40speculation. It feels counterintuitive because clients
- 4:43always wanna know what users will do next. [LEARNER] Exactly.
- 4:46But asking "what will you do" triggers their ideal self, not
- 4:50their actual behavior. [HOST] Right. And that gap between
- 4:53intent and action is where most of our design failures hide.
- 4:56[LEARNER] It’s tricky in practice, though. Sometimes the
- 4:59participant forgets a specific past action. [HOST] That’s where
- 5:02the probing comes in. You don’t accept the vague answer. You ask
- 5:05for the last time it happened. [LEARNER] I tried that recently.
- 5:09The user got defensive. They felt like I was auditing them.
- 5:12[HOST] That’s a common reaction. It helps if you frame it as
- 5:15trying to understand the context, not judging the action.
- 5:18[LEARNER] But how do you balance that with the neutral tone we
- 5:21discussed? [HOST] You stay curious, not inquisitive.
- 5:24Curiosity asks "how did that work for you?" Inquisitiveness
- 5:27asks "why did you do that?" [LEARNER] I like that
- 5:30distinction. It changes the energy in the room completely.
- 5:33[HOST] It does. And it makes the AI thread easier to handle, too.
- 5:36[LEARNER] How so? I’m still figuring out where AI fits in
- 5:39this specific workflow. [HOST] You can use AI to draft the
- 5:42initial neutral question list. It’s good at removing leading
- 5:45language. [LEARNER] That’s useful. I’ve been writing those
- 5:48from scratch and second-guessing every word. [HOST] Exactly. But
- 5:52you still have to filter the output. AI often misses the
- 5:55subtle brand nuances. [LEARNER] True. It might sound neutral,
- 5:58but it misses the specific pain points of our user base. [HOST]
- 6:01So you use it as a first pass, then you inject the human
- 6:04context. [LEARNER] That’s a solid way to work. It saves time
- 6:07without sacrificing depth. [HOST] And it keeps the focus on
- 6:11the actual user experience, not just the metrics. [LEARNER]
- 6:14Agreed. It’s about the story, not just the data points. [HOST]
- 6:17Exactly. The interview is where the story lives.