User Interview¶
User-research method — instantiates User Context Validation
Surfaces users' own goals, constraints, and felt needs in guided conversation, so the design's beliefs about who the user is and what they lack can be tested against their own account.
A User Interview is a structured or semi-structured conversation that draws out what a user is trying to do, what gets in their way, and what they feel they need — in their own words and reasoning. Among the archetype's mechanisms it is the self-report instrument: its distinctive reach is into goals, motivations, mental models, and felt needs that no amount of watching a screen will explain, because they live in why a person acts, not only in what they do. That same reach is its hazard — an interview captures what people say, which is not always what they do — so its whole discipline is to ask in ways that can be contradicted, and to treat the account as a claim to be checked, not a finding.
Example¶
A fintech team building a budgeting app for gig workers holds the assumption that drivers want their transactions categorized automatically — less manual work, obviously better. Before committing the roadmap to it, they interview a dozen drivers across ridesharing, delivery, and freelance trades. The conversations don't stay on the feature; they ladder down to the goal. What emerges is that many drivers distrust automatic categorization: a fuel purchase mislabeled as personal could quietly cost them a tax deduction at year-end, and they have no easy way to catch it. The felt need is not "do it for me" but "let me trust and correct it."
The interview's output is not a redesign — that belongs to other mechanisms — but a corrected picture of the user and a falsified assumption: the target user is a tax-sensitive sole proprietor, and the unmet need is verifiable categorization, not automatic categorization. That single reframing is what keeps the team from shipping a feature users would have quietly switched off.
How it works¶
What distinguishes the interview from its observational siblings is that it works through elicitation, not observation. Open questions and gentle laddering move from a surface complaint ("the app is confusing") to the goal beneath it ("I need to prove these were work expenses"). It reaches retrospective episodes ("tell me about the last time…") and reasoning ("why did you do it that way?") that behavior alone leaves mute. It does not put users in front of a task (that is a usability test) or watch them in their setting (that is field observation); it asks, and then works to separate what is reported from what is merely agreed to.
Tuning parameters¶
- Structure — from a fixed script to a free-flowing conversation. More structure makes interviews comparable across participants; less structure lets an unexpected need surface, at the cost of consistency.
- Segment spread — how many distinct user types you talk to. Widening the spread guards against designing for the first articulate user you meet; narrowing it buys depth in one segment.
- Question framing — open and neutral versus leading. Neutral framing is slower and can feel unproductive, but leading questions manufacture the agreement they seem to discover.
- Probing depth — how hard you ladder toward underlying goals versus accepting the first answer. Deeper probing reaches motivation but risks over-interpreting a single remark.
- Recall horizon — asking about a specific recent episode versus general habits. Concrete episodes resist rosy self-reporting; general habits are faster but vaguer.
When it helps, and when it misleads¶
Its strength is that it reaches the why — goals, trust, fears, and felt needs that behavioral data can only hint at — and it does so early and cheaply, before a design hardens. It is often the fastest way to falsify a confident assumption about what users want.
Its central failure mode is the say-do gap: people report intentions, ideals, and tidied-up habits that diverge from what they actually do, and interviews are also prone to recall error, social desirability, and — most damagingly — leading questions that let an interviewer hear the answer they came for.[n1] The classic misuse is running interviews to confirm a decision already made: recruit friendly users, ask agreeable questions, and collect quotes for the deck. The discipline that guards against this is to triangulate every reported need against observed behavior, keep "what they said" and "what they do" in separate columns, and recruit for the range of users rather than the reachable ones.
How it implements the components¶
target_user— the interview recruits and characterizes the actual people (segment, role, motivation, relationship to the solution) whose account is used to validate, replacing a generic persona label with a specific one.user_assumption— each interview is aimed at an explicit design belief the questions are built to confirm or contradict.unmet_need— laddering from surface complaints to underlying goals surfaces the felt gaps the current design leaves unmet.
It does not capture what users actually do in their setting — observed_behavior and context_of_use belong to Field Observation — nor task-level friction (usability_feedback, which is Usability Test), nor whether the accounts cover the whole population (representative_coverage_check, which is Analytics Behavior Review).
Related¶
- Instantiates: User Context Validation — the interview supplies the self-reported goals and needs the validation loop then tests against behavior.
- Sibling mechanisms: Field Observation · Usability Test · Contextual Inquiry · Diary Study · Journey Map · Participatory Design Session · Service Pilot · Analytics Behavior Review · Accessibility Review
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: User Interview operates as a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding because it surfaces users' own goals, constraints, and felt needs in guided conversation, so the design's beliefs about who the user is and what they lack can be tested against their own account.
Independent corroboration: The frozen evidence defines User Interview as 'Surfaces users' own goals, constraints, and felt needs in guided conversation, so the design's beliefs about who the user is and what they lack can be tested against their own account', so its operative form is Communication, Facilitation & Learning.
Nearest alternative: Assessment, Review & Assurance — User Interview includes features of a bounded evaluation of existing evidence or work that produces a finding or disposition, but its defining operation is a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Ethnography & Qualitative Methods
Origin pattern: Single lineage
Present-day reach: Universal
Rationale: HHS, The Belmont Report documents that human-subject inquiry elicits participant experience under consent, respect, and context-sensitive observation. This is direct, mechanism-specific evidence for ethnography qualitative methods as the best-evidenced historical home of the operation—Surfaces users' own goals, constraints, and felt needs in guided conversation, so the design's beliefs about who the user is and what they lack can be tested against their own account.—rather than evidence merely that the operation is useful there. The retained alternates record genuine adjacent lineages; later portability is represented separately by domain_reach=universal.
Related originating lineages:
- Human-Computer Interaction — Human Computer Interaction supplies a historically relevant adjacent lineage or formative practice for the operation—Surfaces users' own goals, constraints, and felt needs in guided conversation, so the design's beliefs about who the user is and what they lack can be tested against their own account.—but the adjudicated evidence more directly locates the defining lineage in ethnography qualitative methods.
- Psychology — Psychology's perception, cognition, behavior, and risk-communication tradition contributes a separate formative lineage to the mechanism's user interview logic.
- Sociology & Anthropology — Sociology and anthropological study of institutions and social relations supplies a parallel or contributing lineage for the mechanism's defining operation: surfaces users' own goals, constraints, and felt needs in guided conversation, so the design's beliefs about who the user is and what they lack can be tested against their own account.
Review resolution: The blind reviewers disagree on primary lineage (human_computer_interaction versus ethnography_qualitative_methods). The defining operation is: Surfaces users' own goals, constraints, and felt needs in guided conversation, so the design's beliefs about who the user is and what they lack can be tested against their own account. The researched HHS, The Belmont Report establishes that human-subject inquiry elicits participant experience under consent, respect, and context-sensitive observation. That source therefore supports ethnography qualitative methods as the historical origin. human computer interaction remains in the uncapped alternates where it contributes a formative practice, but application or governance is not itself proof of origin. origin_mode=single_lineage records lineage construction; domain_reach=universal separately records later applicability.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
An interview is necessary but never sufficient: on its own it validates only what users are willing and able to say. Its findings become User Context Validation only when a reported need is carried forward and checked against observed behavior — which is why it pairs most naturally with Field Observation rather than standing alone.
[n1] The well-documented divergence between what people report doing or wanting and what they actually do — the "say-do gap" (or attitude–behavior gap). It is the standard reason self-report evidence must be triangulated against observed behavior rather than trusted on its own. ↩