What is the expected path?
The expected path is the actions (clicks) you want a tester to do to complete your mission. Think of it as the flow you expect users to take through your prototype.
Each mission should have at least one defined path. A mission is considered complete once a tester reaches the end screen of a path. You can add as many paths as you want when you create a mission. All paths you set will be considered successful ways to complete the mission.
How success is measured
Maze records every path a tester takes.
- If the paths users take to complete a mission are the same as the paths you set, Maze records this as a direct success.
- If users take an undefined path but still reach the last screen of the mission, Maze records this as an indirect success.
- If users give up or leave the maze during a path, it's recorded as Give up / Bounce.
Setting the path of a mission
To set the path in a mission:
- In your draft maze, add a mission block.
- Write the mission task and an additional description.
- To set the path, navigate through the prototype on the right. You'll see screens appear in the path as you click.
To change the start screen:
- Before defining a path, click to change the start screen.
- This will display all screens in your prototype. Click the screen you need to select it.
To remove a screen from a path, hover and click the screen you want to remove. Deleting a screen from a path will remove any subsequent screens as well.
Adding multiple expected paths
If your mission has more than one valid way to be completed, you can add as many expected paths as you need. All expected paths you set will be used to measure the success metric in your maze results.
Learn how to add multiple paths to your missions.
- The last screen should only be used once in a path. Learn more in this article: Why can't I reuse the last screen in a path?
- Why am I getting an "Invalid mission path" error when I try to launch my maze live?