In unmoderated studies, you can test the flow of Figma prototypes with the Prototype Task. By setting an expected path in the task setup, you can measure task success and fail rates along with other data, such as click map.
What is success criteria in a prototype task?
You can define what task success looks like using two main options:
-
Following the expected path(s): The task is marked successful only if the participant follows the exact navigation path(s) you specify.
-
Reach a specific end screen: The task is considered successful as long as the participant lands on a designated end screen, regardless of the path taken. This option is ideal for evaluating more flexible or exploratory user flows.
A task is considered success as long as the end screen matches the final destination set in the expected path.
- Direct success: is when a user follows the predefined expected path to complete a given task.
- 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.
Learn more with the below reference:
What are expected paths in prototype testing?
Making sense of prototype task results in an unmoderated study
How to create unmoderated prototype tests using Hubble