A good product test asks the same handful of questions every time, so you can compare answers across people and spot patterns instead of drowning in one-off comments. Six prompts cover the ground that actually matters: whether people understand it, where they struggle, whether it’s useful, whether they’d pay, who it’s for, and what to fix first. Asked well — neutrally, one thing at a time — they turn scattered reactions into a ranked list of what to change. Here are the six, why each earns its place, and how to ask them without leading the witness.
1. In one sentence, what does this do?
This tests comprehension and positioning at the same time. If testers can’t describe your product back to you, no feature will save it — the message isn’t landing. Ask it before they explore too much, so you catch the first impression rather than a rationalised one.
2. Where did you get stuck or confused?
The friction question. It surfaces the onboarding dead-ends and unclear moments you’re too close to see. Keep it open and specific to what they just did — don’t list the places you suspect are broken, or you’ll only hear about those.
3. Is this useful to you? Why or why not?
Usefulness is the heart of validation. The “why” matters more than the yes or no — it tells you whether you’re solving a real problem or a nice-to-have. Invite the “no,” explicitly, so people don’t default to a polite yes.
4. Would you pay for it?
Willingness to pay is the signal that’s hardest to fake. You’re not fixing a price here — you’re learning whether the value is real enough that money enters the conversation at all. “I’d pay if…” answers are gold; they hand you the exact gap between nice-to-have and must-have.
5. Who is this for?
Ask testers who they think the ideal user is. When their answer doesn’t match who you built it for, you’ve found a positioning problem — or a better audience than the one you were aiming at. Either way it’s worth knowing before you spend on marketing.
6. What one thing would you change first?
This forces a priority. Anyone can list ten complaints; making them pick the single most important one tells you where to spend your next week. Across several testers, the “one thing” answers cluster fast — and that cluster is your roadmap.
How to ask them
Ask one thing at a time — a double-barrelled question gets a half-answer. Stay neutral: “where did you get stuck?” not “wasn’t the checkout confusing?” Explicitly allow “nothing” and “no,” so you don’t manufacture problems that weren’t there. And wherever you can, pair the answers with watching people use the product — what they do and what they say rarely match perfectly.
Why the same six, every time
Consistency is the whole point. When every tester answers the same prompts, you can line up their responses, count how often each issue comes up, and rank what to fix by frequency and severity. One person saying the pricing is confusing is a note; six of eight saying it is a launch blocker. The structure is what turns opinions into a decision.
This is exactly the structure Dayzero runs on: every tester answers the same core prompts, and you get back a ranked report of what to fix — not a comment box.