What are User Interviews?

A user interview is a one-to-one, semi-structured conversation between a researcher and a participant, designed to explore experiences, motivations, behaviours, and context around a product or problem space. Unlike a survey, an interview can follow the interesting answer wherever it goes; unlike usability testing, it deals in what people think and have done rather than what they can do on screen. It is the workhorse of qualitative research: flexible enough for discovery work before anything exists, and precise enough to dig into why a shipped feature is being ignored.

"Semi-structured" is the operative word. A fully scripted interview is a spoken survey and wastes the format's one advantage; a fully unscripted one drifts. The standard instrument is a discussion guide: a set of topics and open questions, held loosely, with the discipline to abandon it when the participant says something more interesting than your next question.

Why It Matters

Interviews answer the questions that behavioural data cannot. Analytics can tell you that half your users abandon onboarding at step three; only a conversation reveals that step three asks for information people don't have to hand, or don't trust you with. Interviews expose the vocabulary customers actually use (fuel for micro-copy and marketing alike), the workarounds they have quietly built, and the jobs they are hiring your product to do. Early in a project, a dozen interviews can redirect months of engineering; late in one, they explain the numbers everyone is arguing about.

A Brief History

The research interview long predates software. Social scientists formalised it through the early 20th century, and in the 1940s Robert K. Merton's "focused interview", developed to study audience reactions to wartime broadcasts, established much of the technique that user research later inherited, including the focus on specific, concrete experiences rather than general opinion. As human-computer interaction matured in the 1980s and 90s, interviewing migrated from academia into product development. Two modern books then shaped how practitioners actually work: Steve Portigal's Interviewing Users (2013), which professionalised the craft, and Rob Fitzpatrick's The Mom Test (2013), which gave founders a brutal, memorable rule set for getting honest answers from anyone, even your mother.

How to Run Good Interviews

1. Define what you need to learn.
Write down the two or three decisions this research will inform. Interview questions flow from research questions, not the other way round.

2. Recruit deliberately.
Five rich conversations with the right people beat twenty with whoever was available. Use screeners built on behaviour ("How many times have you done X this month?") rather than self-assessment, and mix new, tenured, and churned users when the topic warrants it.

3. Ask about the past, not the future.
The Mom Test's central rule: people are unreliable narrators of their future selves. "Would you use this?" invites polite fiction. "Walk me through the last time you tried to do this" produces evidence, with specifics, sequence, emotion, and workarounds attached.

4. Ask open questions, then shut up.
Lead with "how", "what", and "tell me about"; avoid "do you", "would you", and anything containing the answer. Then tolerate silence. The second half of an answer, the part after the pause, is routinely more honest than the first.

5. Probe with the participant's own words.
"You said the report was 'a nightmare', what made it a nightmare?" keeps the conversation in their frame rather than yours, and signals that you are actually listening.

6. Record, transcribe, and analyse properly.
Notes taken mid-conversation are partial and biased toward what you expected to hear. Record (with consent), transcribe, and analyse across interviews with a systematic method such as thematic analysis. Patterns across participants are the finding, not any single memorable quote.

Remote, Moderated, and In Between

The classic interview is live, in person or on a video call, and that remains the gold standard for depth and rapport. But a growing middle ground trades some of that depth for reach and speed: asynchronous video questions, where participants record spoken answers in their own time, capture tone, hesitation, and verbatim language at a scale live scheduling cannot match. Platforms like Ballpark support both ends, live video interview sessions and self-guided video or audio questions, which in practice lets teams interview across time zones and busy audiences without a fortnight of calendar Tetris. The honest trade-off: asynchronous formats cannot chase a surprising answer with a follow-up, so they work best once you already know which questions matter.

Common Mistakes

The failure modes are well documented and depressingly durable. Leading questions ("How much easier is the new version?") manufacture agreement. Pitching instead of listening, describing your idea and collecting compliments, is the error The Mom Test exists to kill: people will lie to you to be kind, and the more they like you, the more they will lie. Interviewing only enthusiasts produces a rosy consensus that churned users would demolish in minutes. And stopping at what people say, without triangulating against what they do through analytics, usability tests, or purchase behaviour, mistakes testimony for truth.

The Benefits

Interviews produce understanding no other method matches: context, motivation, emotion, and language, straight from the source. They are cheap relative to their influence, they generate the quotes and clips that make research findings travel inside an organisation, and they compound. A team that interviews continuously builds a mental model of its customers that gets sharper with every conversation.

The Limitations

Interviews report perception, filtered through memory and social desirability. What people tell you is real data about how they think, but weak data about what they objectively did. Samples are small, so findings suggest hypotheses rather than measure prevalence; pairing interviews with quantitative research covers that flank. They are also skill-intensive: a poor interviewer harvests politeness, and the transcript looks identical to insight until you act on it. Analysis, done honestly, takes at least as long as the conversations themselves.

The Takeaway

User interviews are deceptively simple: two people talking. The craft is in the discipline of asking about the past, following the participant's language, and treating your own product idea as the thing under test rather than the thing being sold. Teams that master that discipline get the closest thing product development offers to seeing through their customers' eyes.