A mission is a task testers have to complete. To create a mission, you have to define the following: a title, a description, and a path.

The title defines the mission purpose.
The description gives a general instruction.
The path is the expected path you expect users to take; it will serve as the benchmark against which success is measured.

In order to get the most accurate results, there are certain best practices to follow when creating missions. Here’s what you should keep in mind when defining mission descriptions.

You can also check out best practices for mission titles.

Give a clear, but general instruction

The mission description should give a general instruction to the tester about the task at hand. As with titles, use clear and understandable language, keeping in mind that not every tester may be familiar with your internal language.

Example

You've forgotten the password to your account. Reset your password.

Avoid giving exact instructions

Avoid telling testers the exact steps they have to take to complete the mission. This will bias your results.

Examples

Don’t:

Click on the Create Profile button, fill in all information about yourself, then upload your picture and click on the Save button.

Do:

Create a profile on the website and save your information.

Remember: you’re testing whether users will be able to use your application or website as intended without any additional instructions. It’s vital to approximate real-life scenarios as close as possible.

Keep ‘em short

Don’t overwhelm testers with a lot of information and details. If you find yourself writing more than 140 characters or so, check if you’re either:

giving too much details, as described above or
creating a mission that should be separated into two different ones.

You should think of your mission description as a tweet: it gives a general purpose without going into too much detail.
Was this article helpful?
Cancel
Thank you!