The quality of your tester instructions directly determines the quality of your feedback. Here's how to write tasks and scenarios that get you useful results.
The Scenario (optional)
A scenario gives testers context. Instead of just dumping them into your app cold, a scenario tells them who they are or what they're trying to accomplish.
Example: "You're a small business owner looking for a tool to help you schedule social media posts. You've just landed on this website for the first time."
The Attention Note
The attention note is a specific thing you want the tester to focus on or look for during the session. Keep it short and direct.
Example: "Looking for the video upload page" or "Pay attention to how easy it is to find the pricing information."
Tasks
Tasks are the step-by-step actions you want testers to complete. Write them as a real user would think about them — not as developer instructions.
Good: "Try to sign up for a free account."
Good: "Find where you would go to upload a video."
Avoid: "Navigate to the /upload endpoint and test the multipart form."
💡 Tip: Aim for 2–4 tasks per test. Too many tasks overwhelm testers and reduce the quality of their observations.