First-click testing, where you upload an image and track where participants would click first to complete a given task, isn’t directly supported in Maze at the moment.
This article shows a workaround using a prototype block and a two-screen prototype. The test ends right after the first click, no matter where the click is. This is needed because each mission on Maze must have at least one defined path with at least two screens. It is only considered complete once a tester reaches the end screen of the path.
In this article:
Before you start
- All tester interactions will be recorded as a direct success. Misclicks won’t be captured. Learn more
Set up your design file
In the design, include a single hotspot covering the entire screen image that you want to test, leading to a generic success screen.
The test screen doesn’t have to be too complex. It can be a frame from your design file, a screenshot, or even a wireframe or sketch. This will allow you to test design choices throughout your development cycle.
Set up a first-click test in Maze
- Write the mission task: On the prototype test block (it can also be a prototype test inside a variant comparison), write down the situation to be presented to your users. You can also add a context screen for added clarity.
- Set up the path: After importing the prototype into Maze, set up a single two-screen path that leads from the screen you’re testing to the generic success screen.
- Add follow-up questions: Optionally, include any follow-up questions you want to ask your testers about the screen they just saw (using, for example, an opinion scale or a question block).
Analyze your results
The Results dashboard isn’t optimized for first-click tests.
The setup for this workaround “forces” participants into the two-screen success path you’ve defined. As such, all interactions are recorded as a direct success, and grouped under a single aggregated path.
As a result, usability metrics will be skewed. The misclick rate will always be 0%, whereas the success rate will always be 100%. For this reason, you may want to consider keeping your first-click testing on a separate maze/prototype from the rest of your regular usability testing.
Quantitative results: Heatmap & time spent
Using this workaround, you’ll be able to analyze participant behavior by looking into the heatmap data, both at the path/screen level and at the individual tester level.
Open the heatmap to see where your testers clicked first on the screen.
The average time spent on the screen may also be a helpful indicator. Too much time spent on the task suggests that the current design may not be effective.
At the bottom of the page, you can also see the details of each participant session.
Qualitative results: Clips analysis
If you enabled Clips on your first test, you can also see your recordings in the Results dashboard.
Learn more about finding Clips data in the Results dashboard