A mission is a task your testers will have to complete. To create a mission, you have to define a title, a description, and an expected path.
- The title defines the user goal
- The description gives a general instruction
- The expected path is the path you want users to take. It will serve as the benchmark against which the success metrics will be measured. You can add as many paths as needed.
To get the most accurate results, there are certain best practices to follow when creating missions. Here are three tips for writing the best mission descriptions.
1. Give a general instruction
The mission description should give a general instruction to the tester about the task they have to do. As with titles, use clear and easy to understand language, keeping in mind that not every tester may be familiar with your internal language.
You've forgotten the password to your account. Reset your password.
2. Avoid leading words
Avoid telling testers the exact steps they have to take to complete the mission. This will severely influence your results.
Remember: you’re testing whether users will be able to use your product as it is. It’s vital to approximate real-life scenarios as close as possible because, in a live product, there are no detailed instructions on how to use your product.
3. Keep descriptions short
Don’t overwhelm testers with a lot of information and details. If you find yourself writing more than 140-280 characters, check if you’re either:
- Giving too many details or
- Creating a mission that should be separated into two different missions.
Think of your mission description as a tweet: it gives a general purpose without going into too much detail.