In any successful user experience study, you’ll need to write a foolproof test plan to guide users through the tasks that will give you the insights you need.
Designing your test plan isn’t always easy. There are no hard-and-fast rules, and the tasks you should incorporate depend on your research goals.
A task is an action or activity that you want your user to accomplish. Sometimes it’s best to leave tasks open-ended, and in other situations, you need to be more specific.
This article will explain the difference between open-ended and specific tasks. It will also show you when to use each one, and potential pitfalls.
Open-ended tasks give your test participant minimal explanation about how to perform the task or answer the question. The key here is to watch users uncover the answer or solution on their own. Keep in mind, responses may vary drastically from one test participant to the next.
Imagine that you’re testing a fitness app. Here’s an example of what an open-ended task might look like:
- Open-Ended Task: Please spend 5 minutes exploring the app like you normally would.
When to use open-ended tasks
- Find Areas of Interest – When you’re not sure where to focus your test, try this: run a test using open-ended tasks. You’ll be sure to find areas of interest to study in a more targeted follow-up test.
- Exploratory Research – If you’re doing exploratory research, open-ended tasks can help you figure out how people are using your product and the kinds of problems they’re running into.
- Identify Usability Issues – If you want to find things that are broken or cause friction for your users, letting them explore freely will uncover issues you may not already be aware of.
Pitfalls to watch out for
- Clearly define your test objective: When you’re using open-ended tasks, you still need to make sure you have a clear objective in mind. Make sure that your tasks support the ultimate goal of your research.
- Keep participants talking: Make sure you keep participants talking while they’re performing open-ended tasks. You don’t want them to forget to speak their thoughts aloud as they explore freely, so remind them to explain why they’re doing what they’re doing.
Specific tasks will give users clear guidance on what actions to take and what features to speak about. This focuses your research on the exact issues you’re interested in investigating.
Again, imagine that you’re testing the same fitness app as above. Here’s an example of what a specific task might look like:
- Specific Task: Open up the heart rate tracking feature and try to track your heart rate.
When to use specific tasks
- Test specific features – Give test participants specific instructions if you want to test the usability of a certain feature of your product. For example, “Please use the search bar to find a pair of men’s black dress shoes in size 11.”
- Complex products – If you have a complicated, non-traditional, or unusual product that people won’t automatically know how to use, specific tasks will guide them through it and explain the context.
- Conversion optimization – If you know there’s a specific point in your conversion funnel where people are bouncing, use specific tasks to watch them go through the funnel. This will give you the context and insights to understand why they’re bouncing.
Pitfalls to watch out for
- Avoid giving exact instructions – Even if you’re giving your test participants specific tasks, you need to keep a balance. You don’t want to tell them every single thing to do because then you won’t learn anything. Let them do some of the work on their own, and try not to hand-hold them too much.
The key to a successful study is to ask users to perform tasks followed up by questions that will give you the type of insights you need. Once you’ve clearly defined your test objectives, you’ll be able to decide whether to use tasks that are either open-ended or specific.
Open-ended tasks help you learn how your users think. They can be useful when considering branding, content, and layouts, or any of the “intangibles” of the user experience. They’re also good for observing natural user behavior.
Specific tasks can help you pinpoint where users get confused or frustrated trying to do something specific on your site or app. They’re great for getting users to focus on a particular feature, tool, or portion of the product they might not otherwise interact with.
For more information visit the original blog post "Writing a great test plan: Open-ended vs. specific tasks and questions".