Skip to content

Instantly share code, notes, and snippets.

@jconroy
Created November 7, 2017 05:09
Show Gist options
  • Save jconroy/edb6f8c5dfc7bdbd63f1a3e64b142533 to your computer and use it in GitHub Desktop.
Save jconroy/edb6f8c5dfc7bdbd63f1a3e64b142533 to your computer and use it in GitHub Desktop.
Customer Interview Script Template

Customer Interview Script Template

Interviewer Customer Date
[name] [name] [DD/MM/YYYY 00:00am]

Remember

Do not talk about the idea/solution

These interviews are about the customers and their problems. Do your best to keep the conversation focused there.

Do not ask about the future

No hypotheticals, no projections, no guesses. Never ask a question with the word “would” in it like:

  • “If we built a product that solved X problem, would you use it?”
  • “How much would you pay for something that did X?”
  • Would you like your existing solution better if it did X?”

When you use the word “would”, you’re making a thinly veiled attempt to validate your product…not their problem. Don’t do that.

Empathise

This helps build rapport with the customer and leads to better/easier communication.

Statements that demonstrate empathy include:

  • “I’ve experienced exactly the same problems myself”
  • “You’re not alone there. I’ve talked to several other people who have said the same thing.”
  • “That makes sense”
  • “I can see why that’d be hard”

Warm Up

Make a little small talk, it’ll help make everyone (including you) more comfortable.

Examples:

I heard the weather there is [Google the weather in their location - insert here]. How’s that been?

Did you catch the [insert a sports team in their location] game?

How’s your week been so far?

Tell me a little more about what you do...

Introduction and Background

Before beginning it is important to start with some background information and outline the purpose of the conversion in addition to acknowledging and addressing any concerns people may have about privacy etc.

An example introduction that can be used/adapted is:

Firstly thank you so much for taking the time to talk today - we really appreciate you taking the time out of your busy schedule - we're hoping this will only take around 30 mins of your time at most but don't feel like you need to rush.

We're doing some market research and talking to a number of individuals such as yourself to help us understand what problems you may face as a [Customer Role].

Any notes we take or information we collect will ONLY ever be accessible/used by our small team and NEVER shared with or published for people outside of our organisation.

Lastly, if there are questions you don't want to answer we'll also respect that.

Do you have any questions first before we dive in?

Demographics

We'll start with some of the generic demographic questions. If customers are not comfortable answering all or some of them that is fine - simply make a note and move on. It is important to be conscious of peoples privacy concerns with these ones.

Example introduction for these questions:

To start we're going to ask some really basic questions covering generic demographics such as age. Again, if you don't want to answer any please just let us know. Here we go...

Ask Guide Response
Age Bands: 13-29, 30-39, 40-49, 50-59, 60-69, 70+
Gender Identity Use your judgement on whether to ask this one - politely ask if necessary
Location Country, State etc. if not already known
Education Bachelor's degree etc.
Income Bands: < 30k, 30-50k, 50-100k, >100k
Marital Status Single, Married, Divorced etc.
Job/Role Entrepreneur, Founder etc.

Technology Usage

Some quick questions to help us understand and validate our hypotheses around customer technology usage.

Example introduction for these questions:

Next up we're going to ask some quick questions to help us get some insight into your technology usage.

Ask Response
Mac or PC?
Desktop or Laptop?
Apple or Android?
Do you own/use a tablet?
What social media platforms do you use?
Are you the type of person that eagerly awaits and updates to the latest technology as soon as it comes out or someone that waits?
Do you have any experience writing/editing HTML or CSS?
Do you know any programming languages?

Problem Exploration

This is the most important part of the interview and aims to help us learn about the customer’s problems, if they’re worth solving and just maybe...how to solve them.

Key points:

  • Involves iterating through 6 key questions.
  • It is ok to rephrase them or to ask follow up questions if there is a train of thought worth exploring.
  • Using follow up questions like "and why is that important to you?" will help identify benefits / what customers value.

Example introduction.

Awesome, thanks so much for answering all of those. We now have a series of questions that will hopefully help us understand a little more about the sorts of problems/challenges people in your situation/position/industry regularly face. It's these sorts of problems/challenges that we're looking to help people solve.

1. What's the biggest challenge you're facing as a [Customer Role]?

Listen for:

  • The words they use to describe the problem.

Notes:

  • If they try to deflect or avoid the question keep exploring it with them, rephrasing if necessary.
  • Remember to empathise.

Iteration 1 Response:






Iteration 2 Response:







2. Why is it a problem for you?

Listen for:

  • The real problem they're trying to solve.
  • Emotions you can evoke in your marketing copy.

Notes:

  • May just be answered as part of the natural flow of question 1.
  • As you talk with the customer, you can keep asking them, “Why?" or "And why is that important?" until it doesn’t lead to any new answers. This is a useful technique in helping to determining benefits ladders (Refer to 5 Why's / Benefits Ladders in LPP - pg 41 / 5 Whys - Game Storming.

Iteration 1 Response:






Iteration 2 Response:







3. Can you tell me about the last time that problem happened?

Listen for:

  • Opportunities to clarify - this is your chance to ask "dumb" questions.
  • Phrases and jargon you can turn into marketing copy.

Iteration 1 Response:






Iteration 2 Response:







4. When was the last time you tried to solve that problem?

Listen for:

  • Have they tried to solve it in the last 6-12 months?
  • If not, it can't be that important to them - start over asking about a different challenge.

Notes:

  • Even if they have simply reached out to a support channel or asked on twitter - the act of searching can give us some indication of how deep the problem is.
  • If we have to bring the problem up and they’re not taking steps to solve it, it's reasonable to assume they won't use our solution. If they've never looked for a solution the problem is probably not a big enough concern for this customer to find it, pay for it, learn it, or use it.

Iteration 1 Response:






Iteration 2 Response:







5. How did you go about finding a solution?

Listen for:

  • The channels you can use to find other customers like this one.
  • Why they settled on a specific solution? Their values i.e. was it because it had specific level of support, was it cheaper than other solutions etc.

Notes:

  • Another good opportunity to explore why some things are important/valuable to them.

Iteration 1 Response:






Iteration 2 Response:







6. What isn’t ideal about current solutions?

Listen for:

  • How to differentiate your solution from the competition.

Notes:

  • Again this is another good opportunity to explore why some things are important/valuable to them.

Iteration 1 Response:






Iteration 2 Response:







No mention of the problem you hypothesised? Time to Ask…

If our hypothesised problem doesn’t get mentioned, start again with question 1 and iteration #2.

BUT rephrase to be:

What's the biggest challenge you're facing as a [Customer Role] with respect to [Context/Problem] ?



Problem or Other Follow Up Questions

This is an ideal time once talking through problems to raise any additional questions that may be relevant to our hypothetical problem.

Other follow up questions may be:

  • How much are you spending to solve this problem now?

Wrap Up Questions

We're actually exploring a solution to [insert problem] problem/s. Can we contact you if we find a viable solution?

Listen for:

  • Contact Information

Notes:

  • Depending on responses and the customer, they may fit into a couple of the problems we are looking at.

Response:






Do you know 1 or 2 other people who are struggling with [insert the problem] that you think might talk with us?

Listen for:

  • More customers to interview.

Response:






Fin

Thank them for their time etc.

Example that can be adapted:

This has been incredibly helpful, thank you so much for taking the time to talk today. If you have any questions later please do not hesitate to get in touch. I hope you have a good rest of the day.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment