User Interview GPT

Create structured, unbiased user interview scripts that uncover genuine insights instead of just confirming what you already believe.

Why This Matters

Most founders and product teams inadvertently bias their user interviews by:

• Asking leading questions
• Pitching instead of listening
• Focusing only on validating their idea
• Missing critical context about current behaviours

This tool helps you create interview scripts that surface real needs and pain points, giving you trustworthy data for product decisions.

How to Use This Tool

1. Copy the prompt template below
2. Paste it into ChatGPT
3. Fill in the details about your product, target users, and what you’re trying to learn
4. Generate a complete interview script
5. Review and customise for your specific context
6. Conduct interviews following the script

Example Output

Here’s a sample of what the tool produces:

Introduction Section

Script: “Thank you for taking the time to speak with me today. I’m researching how people manage their personal finances and budgeting. This conversation is purely for research—there are no right or wrong answers, and I’m interested in your honest thoughts and experiences. Everything you share will be kept confidential. This should take about 20 minutes, and feel free to ask me to clarify anything that’s not clear.”

Note: This introduction doesn’t mention any specific solution or hypothesis about budgeting tools, which keeps responses unbiased. It also establishes safety for honest answers.

Current Behaviour Questions

Script: “Walk me through how you currently keep track of your spending and income.”

Note: This open-ended question reveals their existing workflow without assuming they use any particular method. Their answer will show how sophisticated their current system is and potential friction points.

Script: “When was the last time you felt you needed to check or adjust your budget? What prompted that?”

Note: This gets at trigger moments and contexts when budgeting becomes relevant, revealing potential activation points for a product.

Pain Point Exploration

Script: “Tell me about a time when managing your finances felt particularly frustrating or challenging.”

Note: This open question allows them to surface their most significant pain points in their own words rather than responding to your assumptions.

Script: “When you think about your financial goals, what makes them difficult to achieve?”

Note: This question explores obstacles without assuming what those obstacles might be.

Scenario Questions

Script: “Imagine you just received an unexpected expense of $500. How would you handle determining if and how you can afford it?”

Note: This scenario reveals their decision-making process and tools used in a realistic situation without directly asking about features they might want.

Running Effective Interviews

After generating your script:

1. Test it with 1-2 people and refine
2. Conduct 5-8 interviews with your target users
3. Look for patterns across multiple interviews
4. Pay special attention to surprising responses
5. Note exact language users use to describe problems

Common Mistakes to Avoid

• Don’t explain your product idea until the very end
• Avoid nodding excessively at certain answers
• Don’t skip questions that seem irrelevant - they may reveal unexpected insights
• Resist the urge to problem-solve during the interview

The best user interviews leave you surprised by at least some of what you learn. If all you hear is validation, you’re probably not asking the right questions.

You are a user research expert specialising in creating unbiased interview scripts that gather genuine insights rather than leading questions.

I need to create an interview script for the following purpose:

Product/service: [DESCRIBE YOUR PRODUCT/IDEA]

Target users: [DESCRIBE WHO YOU WANT TO INTERVIEW]

What I want to learn: [KEY QUESTIONS YOU WANT ANSWERED]

Create a 20-minute interview script with:

1. A neutral introduction that doesn't reveal your hypothesis
2. Open-ended questions that avoid leading the participant
3. Follow-up probe questions to dig deeper
4. Questions that explore the user's current behaviour/workflows
5. Questions about past experiences and pain points
6. Scenario-based questions that reveal preferences without mentioning your solution
7. A closing question that leaves room for unexpected insights

For each question, provide a brief note explaining why you're asking it and what insights it might reveal. Structure the interview to flow naturally from general to specific topics.