|
Learn how to analyze Figma task results using key metrics, path visualizations, and participant behavior insights to improve your prototype's usability and design. |
This article applies to: UserTesting
On this page:
Overview
- Metrics and prototype path flow visualizations help speed up time to insights for Figma tasks.
- By combining quantitative data with visual tools like path flows and heat maps, you can quickly uncover how participants navigate your design — and where they run into friction.
Analyzing results
Use Figma test results to validate findings and improve your prototype based on real user behavior. Here's how:
- View quantitative metrics, including success rates (if a success path is defined), time on task, and participant ratings.
- Use heat maps to explore how users navigate the prototype and identify patterns in their interactions.
- Understand user journeys with path flow visualizations that show each step taken during the task.
- Analyze large participant samples quickly through automated path grouping and aggregated screen-level interactions. This is especially useful when working with high-volume test data.
- Iterate confidently — based on the feedback, continue refining your Figma prototype to resolve usability issues or enhance the design.
-
Watch the participants' recordings. Switch to the Response tab and you'll see a play icon next to each entry—clicking it lets you watch the participant’s recording as they complete the task, so you can drill deeper into the data if something interesting stands out.
Key metrics
- The following metrics help you understand participant behavior and task performance during your Figma test.
- Use this information to validate your design, identify usability issues, and uncover unexpected interactions.
Paths
- The sequence of interactions the participant followed through the prototype.
- This helps compare behavior to the expected flow.
Success rate
The percentage of the total number of participants who achieved either direct or indirect success.
Steps
- This displays the average number of screens all participants viewed on the prototype.
- Switch to the Responses tab of the Figma results to see the number of screens by participant.
Clicks
- This displays the average number of clicks on a prototype across all participants.
- Switch to the Responses tab of the Figma results to see the number of clicks by participant.
Time on task
- This displays the average time spent on a task across all participants at the top level.
- Switch to the Responses tab of the Figma results to see the time spent on task by participant.
Success paths
- Success Paths allow you to define the ideal interaction sequence a participant should take, perfect for validating designs and identifying blockers.
- Pro tip: This is also a great chance to preview your prototype’s behavior before launch. Use the Preview to check for scrolling, loading, or display issues that could impact the participant’s experience.
| Success | Reaching the last screen in the researcher’s defined path when creating the test. |
| Direct success | A scenario where participants took the exact steps and path defined by the researcher when creating the test. |
| Indirect success | This is a scenario in which participants reach the last screen of the researcher’s defined path, even if they take extra steps or deviate along the way. |
| Non-success | Scenarios where participants failed to reach the last screen of the researcher’s defined path. |
| Undefined | Scenarios where no success path was set for this task, so no direct or indirect success is measured. |
Related content
|
|
|
|
Want to learn more? Check out these Knowledge Base articles... |
Interested in growing your skills? Check out our University courses... |
|
|
|
|
Need hands-on training?
|
Can't find your answer?
|