Conduct customer interviews

[Almenon]

trafficstars

I don't fully understand who is using AREPL or why, or why they stop using AREPL. By conducting some interviews I'm hoping to get a better sense of the audience and more confidence in AREPL, or at least a understanding of what I did wrong.

I saw a customer interview at my work and I was like "oh snap I should be doing this!"

[Almenon]

If you want to validate your product/market fit, you’ll need to talk to more customers than you normally would. Typically, between 10-20 is a good place to start, keeping in mind you may have to do customer validation interviews more than once, if your first idea’s a flop.

https://www.userinterviews.com/blog/the-ultimate-guide-to-doing-kickass-customer-interviews

How many people should you interview? Shoot for about 5 people per customer category or persona — but no more than a dozen. After five or six interviews, you’ll likely start to see trends and themes emerging in the responses.

https://www.crazyegg.com/blog/start-talking/

[Almenon]

My initial thoughts are questions like so:

• When you used AREPL what did you do? Student? Profession?
• How did you hear of AREPL?
• What made you interested in it?
• How easy was it to get started with?
• What did you use it for?
• How often did you use it?
• Did you find it useful?
• Why did you stop using it, if so?

This website suggests the following: Asking about motivations: What was going on that made you seek out our software? Asking about problems & struggling moments: Tell me about when you were trying to write your business plan? What was that like? Asking about the value they receive from your product: Exactly what does our software help you do? But the most insightful responses — especially for copywriting and messaging — will often come from asking your customer how they feel.

What were you feeling while using the product? When you found our solution, how did that make you feel? What were you feeling when you decided to switch to us?

So keeping article in mind:

Introduction/warmup:

• Chit-chat (very informal, try to cover some of below):
• What got you into programming? What are you doing now? What were you doing when you used arepl?

Problem / motivations:

• How did you like [profession]? What do you think about writing and debugging python code? Do you have any frustrations with it?

Motivations:

• How did you hear of AREPL? What did you think when you saw it?

Value:

• What was your experience of using AREPL? How did you feel using it?
• What lead you to stop using AREPL:
• Clarifying Questions -> How often did you use it? What did you use it for? What libraries did you use it with? Did you run into any bugs?

What I can add:

• Are you still doing python coding? How do you feel about it now? What could I add to AREPL that you would use consistently?

[Almenon]

Another interesting thing https://www.crazyegg.com/blog/start-talking/ talks about is that if you ask "why" it can backfire, in that a customer might invent a rational ad-hoc explanation for their decision, when the real reason was more emotion-based.

This question might be a good one to add near the beginning:

• How do you feel about writing python code?

[Almenon]

no response yet, need to send out more requests :|