A mission is a task your testers will have to complete. To create a mission, you have to define the task, a description, and the expected path(s) inside a prototype.
- The task 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 success is 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 mission tasks:
1. Write clearly
The task is the first thing that testers will read when they begin a mission. You should use language that is clear and easy to understand. Keep in mind your testers when writing tasks: who they are and how familiar they are with your product.
Unless you're testing your UI copy, avoid your internal company language.
For example:
Create a maze vs Create a test
The first example may be unclear for people not familiar with Maze.
2. Keep 'em short
Tasks should be kept as short as possible. Anything that is a detail should be included in the mission description.
Examples:
1. Locate the place on the map
2. Change password
3. Filter list selection
4. Create a profile
3. Define an action
The task should define the mission goal. Because a mission is an exercise that needs to be completed, the task usually describes an action to be taken by testers. Use verbs to give instructions.
*Examples of action verbs: *
Complete, write, create, go to, subscribe, add, filter, etc.