User Interview Script Builder

Why Structure Matters in User Interviews

A user interview without a script is a conversation. A conversation is valuable – but it's hard to analyze, hard to replicate, and hard to compare across participants. Structure doesn't mean rigidity: a good script gives you a consistent backbone while leaving room to follow surprising threads. The introduction section ensures consent is always collected. The warm-up section builds rapport before you ask anything consequential. The core questions section is where real insight lives. The wrap-up section surfaces everything your questions didn't cover.

The biggest mistake researchers make is treating all research goals as interchangeable. A usability testing session and a discovery interview need completely different questions. Usability testing asks "can you complete this task?" Discovery asks "what are you even trying to accomplish?" Competitive research asks "what made you switch?" Each goal implies a different participant mindset, a different script structure, and different follow-up probes. Building your script around a specific goal – before writing a single question – is what separates insights from anecdotes.

Audience selection matters just as much. The warm-up questions that work for a churned user ("take me back to when you were using it regularly") would confuse a prospect who has never used your product. The probes that work for a domain expert ("what do most practitioners get wrong here?") would overwhelm a casual user. Matching your question vocabulary and assumptions to who you're talking to is the fastest way to improve interview quality. This is closely tied to mental model research – understanding not just what people do, but why they believe what they believe about a domain. Finally, a user persona is a useful anchor for deciding which audience to prioritize when your research budget is tight. See also qualitative vs. quantitative methods for when interviews are the right tool at all.