The short answer
Ask about a real attempt, not a general opinion. Give the person one task, let them work without coaching, and ask what they expected at the moment they stopped. Useful feedback describes behaviour. Polite feedback describes your product back to you.
Why “What do you think?” fails
The question is too large. A helpful person has to decide whether you want reassurance, design criticism, a feature list or a buying decision. Most people choose reassurance because it is socially safe.
Narrow the job. You are not asking them to judge the business. You are trying to understand one moment in the product.
Start with a task
Choose the first action that proves the product can help:
- Create the first project.
- Import one real file.
- Find a product that fits a stated need.
- Invite a collaborator.
- Publish the first result.
Say what the person should try, but do not explain the route. If your instructions contain the missing product guidance, the test cannot reveal that it is missing.
Five questions that produce evidence
What were you trying to do?
Ask this after the attempt. Their wording tells you whether the promise on the page matched the job in their head.
What did you expect to happen next?
Use this at the first hesitation. It reveals the label, placement or mental model they were looking for without asking them to design the fix.
What did you try before this?
The answer names the real alternative. It may be a spreadsheet, a manual habit or doing nothing. That is more useful than a competitor list copied from a search result.
What would stop you using this again next week?
This makes the cost concrete. “Needs more features” is vague. “I would have to re-enter every client” gives you something to fix or consciously decline.
Who else has this problem?
Ask only after the person has used the product. A good answer sharpens the audience. A vague answer tells you the problem may not be urgent enough to travel by word of mouth.
Keep the founder out of the way
Do not explain a screen while somebody is trying it. Write down the urge to help. Every sentence you nearly said is a candidate for clearer copy, a better default or a removed step.
When the attempt ends, ask about the moment that surprised you. Do not defend the design. You can decide what to change later.
Turn one conversation into a decision
After each session, record four lines:
- The task they attempted.
- The first place they hesitated.
- What they expected instead.
- The smallest change you will test.
Wait for a pattern before rebuilding the product. One person can reveal a broken button. Three people getting lost in the same place usually reveals a broken path.
If you need a place to ask one sharp question, claim your product page and set its feedback prompt. Private notes will appear in your founder dashboard.