Interviewing for Needs

Eliciting customer needs by collecting specific stories of actual past behavior rather than asking people what they want or would do. Instead of "would you use this?" you ask "tell me about the last time you faced this," and mine the concrete story for the needs, pains, and workarounds it reveals. What people did is evidence; what they say they want is opinion.

Why it Matters

Direct questions about preferences and future behavior produce confident, unreliable answers: people rationalize, speculate, and aim to please. Grounding the conversation in a specific remembered episode bypasses that, surfacing the real context and unmet needs that a hypothetical never would. It is how discovery gets trustworthy signal from customers instead of agreeable noise.

Signals

• Interviews full of "I would probably..." and "I think I'd like...".
• Feature requests taken at face value as statements of need.
• Findings that sound supportive but never translate into real behavior.

Benefits

Evidence grounded in what customers actually did, needs uncovered that they could not have articulated directly, and a defense against building for stated preferences that real behavior contradicts.

Risks

Leading questions that contaminate the story; generalizing from a vivid single account; collecting stories with no structure to turn them into needs.

Tensions

Specific stories are richer but slower to gather and harder to analyze than a quick survey of opinions, and customers often want to jump to solutions; the discipline is to keep pulling them back to what actually happened.

Examples

Asking a customer to walk through the last time they hit a problem, step by step, and extracting the unmet need from the workaround they describe, rather than asking whether they would like a proposed fix.