How to Talk to Users: Questions That Get Honest Answers
People are polite, so they often tell you what you want to hear. A practical guide to asking questions that reveal what users really think, need and would pay for.
October 18, 2026 2 min read
Talking to users is the most valuable thing you can do in the early days. But there is a catch: people are polite. Ask "would you use this?" and most will say yes, then never use it.
The fix is not to talk to more people. It is to ask better questions. Here is how.
Ask about the past, not the future
Questions about the future invite guesses and kindness. Questions about the past reveal what actually happens.
Future (unreliable)
Would you pay for a tool that does this?
Past (honest)
The last time this happened, what did you do about it?
If someone has never tried to solve the problem, it might not be painful enough for them to pay for a solution. That is important to know.
Talk about their problem, not your idea
The moment you describe your app, people start being polite about it. So hold off on mentioning it. Focus the whole conversation on their situation.
- "Tell me about the last time this was a problem."
- "What did you try? What was frustrating about it?"
- "How much time or money does this cost you now?"
- "Have you paid for anything to solve it?"
Listen more than you speak
Aim to talk for a small fraction of the conversation. When there is a pause, let it sit. People often fill silence with their most honest thoughts.
Ask "why?" and "can you give me an example?" more than you think is polite. The details are where the truth is.
Tell real signals from polite noise
| Polite noise | Real signal |
|---|---|
| "That's a great idea!" | They describe a real, recent struggle in detail |
| "I'd definitely use that." | They have already tried other tools or hacks |
| "Let me know when it's ready." | They ask when they can start, or offer to pay |
| "Sounds interesting." | They introduce you to someone else with the problem |
Compliments are not data. Actions are. Pay attention to what people have done and what they offer to do next.
After the conversation
- Write down what they said, in their own words, right after.
- Note the exact phrases they used. Use them in your headline.
- Look for patterns after five or more conversations.
- Thank them, and follow up if you build something they asked for.
The goal of a user conversation is not to hear that your idea is good. It is to learn what is true.
Your user-conversation checklist
- Questions about past behaviour, not future promises
- Your app not mentioned until the end, if at all
- You spoke far less than they did
- "Why?" and "for example?" asked often
- Their exact words written down afterwards
- Patterns looked for across several conversations