Quick takeaways
- Clarify what you want to learn
- Treat surveys differently from usability tests
- Protect participants
- Keep feedback voluntary and unbiased
Clarify what you want to learn
Define the audience, research question, and what an effective response would help you change. Keep the request short and specific.
Treat surveys differently from usability tests
A usability tester explores a product; a survey participant answers questions. Explain eligibility, approximate time and how submitted responses will be used.
Protect participants
Avoid collecting names, private identifiers or unnecessary personal data. Include clear consent wording and follow your institution’s ethics process when applicable.
Keep feedback voluntary and unbiased
Do not suggest desired answers, demand favorable comments or reward specific findings. Tell participants they may decline sensitive questions.
Summarize limitations accurately
Describe sample size, recruitment bias and what the findings can and cannot establish. Community testers rarely represent a statistically random population.
Frequently asked questions
Can a PeerTry activity replace ethics approval?
No. Seek institutional approval when required before recruiting participants.
Can I say all users like my app after ten positive comments?
No. A small voluntary sample cannot establish that claim.
Use private feedback to find what works and what needs another iteration.