Guide6 min readUpdated
User Interview Questions to Test Your App Idea
User interview questions, a 30 minute script and ways to avoid leading questions, so you can validate an app idea before paying for design.
By Tithi Mondal, UI/UX Designer
Imagine you want to build an app for tiffin services in Durgapur. You call five tiffin owners and ask, "Would you use an app to manage your orders?" All five say yes. That yes comes from politeness. It tells you nothing about your idea.
A user interview is a one-to-one conversation where you ask a person about what they really did in the past, so you learn whether a problem exists before you pay for design. Good user interview questions ask about last week, not next year. This guide gives you a script, sample questions and a fix for leading questions. For the wider picture of research, read user research for startups.
What makes a good user interview question?
A good question asks about one real event in the past and lets the person answer in their own words. "Tell me about the last time you ordered lunch for your office" is a good question. "Do you like ordering lunch online?" is a poor one.
Use three rules:
- Ask about the past, not the future. People guess badly about what they will do. They remember well what they did yesterday.
- Ask for stories, not opinions. A story has names, places and steps. An opinion has none.
- Ask one thing at a time. Two questions in one sentence get one half-answer.
The best follow-up questions are very short: "Why?", "What happened next?", "Can you show me?" Then stay quiet. Silence makes people add the detail you need.
How do you avoid leading questions?
A leading question is a question that already contains the answer you want. The person hears your hope and agrees with it. To avoid leading questions, remove your idea from the question and ask about the person's behaviour instead.
| Leading question | Better question |
|---|---|
| Wouldn't it be useful if the app sent reminders? | How do you remember to follow up with customers today? |
| Would you use an app like this? | What have you tried so far to solve this? |
| Do you find the current process frustrating? | Walk me through the last time you did it. What happened first? |
| How much would you pay for this? | What do you spend on this today, in rupees per month? |
| Is price your main worry? | What made you choose the option you use now? |
Three more habits help. Do not pitch your idea in the first 20 minutes. Do not correct the person when they describe something you think is wrong. Do not say "great" after answers you like, because that teaches the person what to say next.
What does a simple customer interview script look like?
A customer interview script is a short list of questions in a fixed order that you read from a page, so every call covers the same ground. A 30 minute call needs six steps.
- Warm up (3 minutes). Say: "Thank you for your time. I am not selling anything, and there are no right or wrong answers. I want to understand how you do this today. May I take notes?"
- Context (5 minutes). "Tell me about your work. What does a normal day look like?"
- The last time (10 minutes). "Tell me about the last time you had to [do the task]. What happened first? Then what?"
- Workarounds (5 minutes). "What did you try to make this easier? What did you stop using, and why?"
- Cost (5 minutes). "What did this problem cost you in time, money or customers?"
- Close (2 minutes). "Is there anything I should have asked? Who else should I speak to?"
Notice that your idea does not appear anywhere in this script. The call is about their life. Your idea can come in the last five minutes, and only as a rough sketch for reaction.
Which questions help with validating an app idea?
Validating an app idea means checking three things: the problem is real, it happens often, and it costs the person something today. Questions that test these three things work better than any question about your app.
Try these, grouped by what you want to learn:
- Is the problem real? "When did this last go wrong for you?"
- How often does it happen? "How many times in the last month did this happen?"
- What does it cost? "What did you lose the last time? Money, time, a customer?"
- Do they already try to fix it? "What are you using today, even if it is a notebook or a WhatsApp group?"
- Who decides? "Who else has to agree before you try something new?"
Strong signals are a specific recent story, a messy workaround, money already spent and a willingness to give you a second call. Weak signals are compliments, "maybe later", "send it to me when it is ready" and answers about what other people might want.
On a seller app for a marketplace in Tanzania, the design work covered seller onboarding, verification and listings. Those are exactly the steps where I ask people to walk me through what they do today, because their real order of steps often differs from the order the team imagined.
Who should you interview, and how many people?
Interview people who have the problem right now, not friends and family. Friends want to protect your feelings, and family members often do not have the problem at all.
Find real users in places where they already talk. For a tiffin app, that is a local WhatsApp group of home cooks. For a farming app, that is a farmer producer group or a local input shop. Ask each person for one introduction at the end of the call.
You do not need a large number. A common sign to stop is when new calls stop teaching you new things and you hear the same stories again. If you hear completely different stories every time, you may have mixed two kinds of users, and you should split them into two groups.
Language matters. Hold the call in the language the person thinks in, whether Bengali, Hindi, Marathi or English. You can write your notes in English afterwards. A person who must translate in their head gives shorter and safer answers. For a thank-you, offer a small UPI payment or mobile recharge, and say so before the call.
How do you take notes and use the answers?
Write notes in three columns during or straight after each call: what the person said, what the person did, and what surprised you. Keep their exact words in quotation marks, because exact words are what you will later use as button labels and screen text.
| Call | Quote | Behaviour | Surprise |
|---|---|---|---|
| 1 | "I note orders in a diary and then forget Saturday's" | Uses diary plus WhatsApp | Does not trust phone memory |
| 2 | "Customers pay by UPI but I check the SMS" | Checks payment by SMS | Pays a helper to do it |
After 5 or 6 calls, read the table and underline anything that appears more than once. Repeated pains are your real problem list. Group them into one or two people types, as in what is a user persona, and draw the steps of the task, as in what is a customer journey map.
Then choose what to build first. The repeated pain with the highest cost is your first feature, as explained in MVP design: what to build first. When you reach screens, a small test of a clickable prototype is the next step, covered in usability testing on a small budget.
If you want help turning interview notes into a clear plan and screens, I can do that through mobile app design, or you can send me a message with what you have heard so far.
Frequently asked questions
How many questions should a user interview have?
Prepare about 8 to 10 questions for a 30 minute call, but expect to ask only 5 or 6 of them. The follow-up questions such as 'Why?' and 'What happened next?' will use most of the time.
Can I do user interviews on WhatsApp calls?
Yes. A WhatsApp voice or video call works well for most people in India, because they already use it daily. Ask permission before you record, and take notes either way.
What if people say they love my app idea?
Treat praise as a weak signal and ask for a story instead. Ask, 'When did you last face this problem, and what did you do?' If they cannot name a recent time, the problem may not be strong enough.
Should I show a prototype in the interview?
Not in the first round. First learn about the problem with no idea on the table. Show a rough prototype only in a later round, when you want reactions to a specific solution.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.