Definition

The user interview discipline of keeping intellectual flow running from interviewee to interviewer — the interviewer's job is to have their mind shaped, not to shape the interviewee's.

The articulation is the data

The interviewee's exact wording is what gets used downstream. How they describe their situation, the words they reach for, the order they remember things in, the connections they make that the interviewer wouldn't have constructed — all of it becomes raw material for intent clustering, route modeling, and copy that translates back to scale at the moment of acquisition. The interview is producing this material; anything the interviewer adds to the conversation displaces it.

Interrupting, filling silence, redirecting, or inserting interpretation all reverse the direction intellectual value should be flowing. Once the interviewer's framing enters the conversation, the interviewee starts responding to it rather than continuing their own thinking. Polite agreement replaces unfiltered articulation, and what reaches downstream becomes a record of the interviewer's hypotheses confirmed back, not the interviewee's mind surfaced.

Five moves in practice

• Make them comfortable; you can still speak. The discipline is on direction of intellectual flow, not silence as rule. Warming the interviewee up, asking for clarification, summarizing back, prompting continuation, backtracking — all fine. The vigilance is about whose mind is being shaped.

• Don't ask pre-scripted questions. Use the situation explorer's regions instead — sought state, prior states, route, what comes after, completion criteria. Pre-decided regions give the interview shape without imposing the interviewer's framework on the interviewee's content before the interview starts. Especially avoid offering-feedback questions ("what would you change about feature X?"), which route the conversation onto the company's timeline rather than the user's.

• Follow the wandering. Interviewees go in directions the interviewer hadn't considered, and that's the point. The wandering reveals what they treat as relevant, what connects to what in their mind, and their natural altitude band. Redirecting forces the interviewee's narrative onto the interviewer's track and loses the upstream signal.

• Avoid inserting your own thoughts. Distinct from following the wandering: that move forbids redirecting the path; this one forbids adding interviewer-content along the path. Hypotheses, interpretations, and mid-stream verifications ("so when you said X, were you thinking Y?") corrupt the data even when the interviewer isn't redirecting. Hold hypotheses in notes and test them against the interviewee's continued narrative — if a hypothesis is right, the narrative will support it indirectly; if it's wrong, asking for confirmation just gets polite agreement.

• Lean into dead air, sparingly. When silence emerges naturally, leave it — sometimes past the point of comfort. Interviewees often blurt unfiltered, subconscious material to break silence, and that's content the interviewer wouldn't have known to ask for. But this is a sparing tool against a baseline of warmth; used too freely, held silence produces anxious filler rather than insight.

What it preserves

Three things get preserved that the interview would otherwise lose:

• Vocabulary — words and phrases captured verbatim for downstream use as folk vocabulary, sticky-note exercise output, and marketing copy that translates back to scale.
• Sequence — the order in which the interviewee remembers and connects things, which reveals their natural narrative structure and altitude band.
• Connections — links the interviewer wouldn't have constructed, which often reveal the core logic of the user's pursuit.

Example

A recent paying customer of a project-management tool is asked what was happening at their company when they signed up. They start describing a board meeting, a hiring push, the team doubling in six weeks. The interviewer is tempted to ask "so you needed better task tracking?" but holds back and just prompts continuation. The interviewee keeps going: "I just couldn't tell who was supposed to do what anymore." That phrase — "who was supposed to do what" — is what gets captured verbatim, and it ends up in the headline of the acquisition page six months later. Had the interviewer asked the task-tracking question, the interviewee would likely have agreed ("yeah, exactly") and the original phrasing would never have surfaced.

See also

• User value research
• Hand-sent-feeling
• Approximate intent