1. Home
  2. Templates
  3. Conversation guide

Customer interview questions

The conversation guide

Five questions for talking to people who have the problem you want to solve, and a scale for scoring what you heard. Every question asks about what people have done, not what they would do, because nobody can politely invent a detailed history. Use it before you build, for five to ten conversations per problem.

Type straight into the sheet or print it blank. What you type stays in this browser and is never sent anywhere.

The Code Was Never the Hard Part

The conversation guide

Ask about what people have done, not what they would do. Don't pitch. Your product barely comes up, and early on it shouldn't come up at all.

Who

Date

The problem

  1. When did you last run into this? Tell me about that time.

  2. What did you do about it, step by step?

  3. What have you tried before? Why did you stop?

  4. What does this cost you, in time or money or stress?

  5. If you could wave a magic wand at one part of this, which part?

Score the conversation

Weakest to strongest. Pick the highest one that really happened.

You're looking for a problem where most conversations land at three or higher. A candidate whose conversations cluster at one and two is telling you to let it go.

neverthehardpart.com/templates/conversation-guide

How to use it

  1. Find five to ten people per problem. Not fifty. Patterns show up early, and after seven or eight conversations you'll be hearing repeats. Look in the same places your signals came from: the communities, forums and groups where people have already described the problem in public.
  2. Send a short, plain message. You're researching how people handle the problem, you aren't selling anything, and you'd love twenty minutes of their experience. People enjoy being treated as experts on their own pain.
  3. Before any results come in, write down what counts as a yes. Something like: at least half the conversations reach three or higher, and at least one reaches five.
  4. Ask the five questions. Twenty minutes is enough. Stay in the past tense and don't pitch, because the moment you pitch, people start being kind instead of accurate.
  5. Score each conversation on the scale, then judge the problem against the numbers you wrote down.

Why the past tense

A question in the future tense invites fantasy, because "Would you pay for this?" costs nothing to answer generously. A question in the past tense asks for facts. "What do you do about this today?" "When did it last happen?" "Walk me through it." "What have you tried?" "What did that cost you?" Nobody can politely invent a detailed history, so the past tense gets you truth almost by accident.

Be careful with friends. Friends are the least reliable sources on earth when it comes to this, because they're rooting for you. If you use friends, use the past-tense questions with extra discipline.

If nobody responds at all, that's data too. If you can't reach the people who have this problem for a conversation, you won't reach them for a sale either.

What counts as evidence

A pull is the strongest signal a conversation can produce, because you didn't ask for it. Polite interest is worth nothing, however warm it sounds. Every candidate you drop because its conversations stay at one and two saves you the months it would have cost to learn the same thing from a launch.

Where AI fits

AI speeds up the work around the conversations: finding where your people gather, drafting outreach, preparing questions, transcribing calls, and sorting your notes for recurring pains and the exact phrases people used. The conversation itself is the part I don't hand over. Simulated users and AI-generated "customer feedback" will happily validate anything, because there's no pain behind the words. An AI interviewing a real person is different, though, and I'm happy to let AI ask the questions, as long as the person answering has the problem.

From chapter 4, "Evidence". To see where these conversations fit, read How to validate an app idea before you build it.

Kindle ebook · Out now

Out now. Read it this weekend.

$9.99

Read it on a Kindle or in the free Kindle app on your phone, tablet or computer. The paperback comes later.