The quality of your feedback depends entirely on the quality of your questions. Here's a practical, example-driven guide to writing tasks that get useful answers.
1. Write open-ended scenarios
Scenarios set the context for testers. They should be open enough to let testers behave naturally, but specific enough to focus their attention.
Bad: "Click the sign up button."
Why: This tells the tester exactly what to do. You learn nothing about whether they'd find it on their own.
Good: "You're interested in this product. See if you can figure out how to get started."
Why: This reveals whether the sign-up path is discoverable and intuitive.
Bad: "Test my website."
Why: Too vague. Testers won't know what to focus on.
Good: "You're a busy parent looking for a meal prep service. Explore the homepage and see if you can figure out what's offered and how much it costs."
Why: Gives a persona, a goal, and specific things to look for.
2. Ask what they understood, not what they did
The most valuable questions reveal perception, not just behavior.
Bad: "Did you find the pricing page?" (yes/no, leading)
Why: Tests navigation, not understanding. A "yes" tells you nothing about what they thought of the pricing.
Good: "What do you think this product does?" (open, perception-based)
Why: Reveals whether your messaging actually communicates your value proposition.
Good: "What was your first impression of the homepage?" (open, emotional)
Why: Captures gut reactions that often predict behavior.
3. Keep questions specific but not leading
Leading questions bias responses. Specific questions get actionable answers.
Leading: "Was the homepage clear?" (implies it should be clear, encourages "yes")
Specific & open: "What stood out to you on the homepage? Was there anything that confused you?"
Leading: "Did you like the design?" (encourages positive response)
Specific & open: "What's one thing you'd change about the homepage?"
4. Use the "Help me..." format for your landing page headline
Frame your test landing page as a personal request from you (the founder) to the tester. This feels human and gets better engagement than a clinical test description.
Good headlines:
- "Help me understand if my landing page is clear."
- "Help me see if people can sign up without getting stuck."
- "Help me figure out if my pricing makes sense."
Don't mention rewards or credits in the headline — the tester reward is shown separately. Keep the focus on the help you need.
5. Order your flow logically
People form opinions in stages. Mirror that in your test flow:
- Broad first impressions — "What do you think this product does?" (before they've explored much)
- Task-based exploration — "Try to find the pricing page." + "How was that experience?"
- Reflection — "If you were going to sign up, what's one thing that would make you hesitate?"
This mirrors how real users form opinions: first impression → exploration → decision.
6. Don't overdo it
Three to five well-crafted questions beats ten rushed ones. Testers have limited attention — respect it.
Too many: 12 questions and 8 instructions = tester fatigue, rushed answers, lower quality feedback.
Just right: 3 instructions + 4 questions = focused, thoughtful, detailed responses.
7. Quick checklist before you publish
- ✅ Is my scenario open-ended with a clear goal?
- ✅ Are my questions perception-based, not just behavior-based?
- ✅ Are any of my questions leading? (If so, rewrite them.)
- ✅ Does my flow go broad → specific → reflection?
- ✅ Do I have 3–6 blocks total?
- ✅ Is my landing page headline in the "Help me..." format?
If you can check all these boxes, you're ready to publish.