Quick answer
Good tester instructions state one goal, list numbered steps with one action each, say exactly what evidence to submit, ask specific questions, and give a time estimate. Clear instructions produce comparable, useful feedback and fewer rejected submissions.
The five rules
- Start with the goal in one sentence.
- Number each step and keep one action per step.
- Say exactly what to submit and in what format.
- Ask specific questions, not 'Any feedback?'.
- Give a realistic time estimate.
Example: weak vs strong
| Weak | Strong | |
|---|---|---|
| Goal | Test the app | Create an account and add your first expense |
| Evidence | Send screenshots | Screenshot of the expense list showing your entry |
| Question | Any feedback? | What, if anything, stopped you finishing sign-up? |
Checklist before you publish
- Could someone new to the product follow every step?
- Is any step ambiguous about which button to press?
- Are test accounts or credentials included?
- Is the evidence requirement possible on every allowed device?
Frequently asked questions
How long should a test task be?
Most single-session tasks work best at 10–30 minutes. Split longer work into days or separate tasks.
Should I tell testers what I expect to find?
No. Describe what to do, not what to think, so feedback stays honest.