What are expected paths in prototype testing?

Expected path is a sequence of Figma screens representing the ideal flow that you expect your users to take to reach the end goal. For example, you can test a newly designed checkout process for a website and monitor what paths users take to complete it. Setting an expected path in your unmoderated study allows you to measure task success rates. Task completion will be captured in three different ways:

A task is considered a success as long as the end screen matches the final destination defined in the expected path.

• Direct success: is when a user follows the predefined expected path to complete a given task. You can set one direct success path. Any other paths that testers take to reach the end goal will be captured as indirect success paths. 
• Indirect success: is when a user completes a task by ending up in the desired end screen but through other paths that have not been defined in expected path.
• Incomplete: is when a user quits or determines the task is complete in a wrong end screen.

Follow the steps below to learn more about setting an expected path.

First, load the Figma prototype by pasting in the link.

The loaded Figma file on the right side is interactive. Click through the prototype to set the expected path.

As you click through the prototype, the right-bottom carousel will add the following screen.

You can add as many screens in the expected path. In this example, our desired end goals is to successfully submit an offer.

To remove or reorganize the flow, hovering over each screen will show a delete option as shown below.

You can review the flow in more detail by clicking on the expand button.

See related:

• I launched my unmoderated study. What's next?
• What are expected paths in prototype testing?