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 users take through your prototype.
At least one path should be defined for each mission. 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 as successful ways to complete that mission.
How the success metric is measured
- If the paths users take to complete a mission are the same as the paths you set, Maze records this as direct success.
- If users take an undefined path but still reach the last screen of the mission, Maze records this as indirect success.
- If users give up or leave the maze during a path, it's recorded as Give up / Bounce.
How to set the path of a mission
Setting the path of a mission is easy. Here is what you should do:
When you're done, it's time to set the path. Click the prototype screen on the right to set a path. You'll see screens appear in the path as you click.You'll only be able to click on predefined hotspots. If your prototype doesn't have any, go back to the prototyping tool you used and create them. Back in Maze, refresh your prototype. You should now be able to define paths.Note! The last screen should only be used once in a path at the end. Learn more about this.
If you want to change the start screen, click on click to change the start screen. This will display all screens in your prototype and allow you to select the one you need.
If you want to remove a screen, hover and click on the screen you want to delete.
- Click on Save Updates to save all changes.
How to add 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.