What it is
A focused test that records the very first click participants make when attempting a task on an interface or image, because a correct first click predicts eventual success.
When to use it
During Prototype, to validate whether navigation, labels, or layout point users the right way at the first step.
Why (value)
The first click is a strong, cheap predictor of task success and highlights misleading labels and layouts early.
How to run it
- Choose screens and realistic tasks.
- Present the screen and ask where they would click.
- Record the first click location.
- Aggregate click maps and success rates.
- Fix misleading paths and retest.
Inputs and outputs
- Inputs: Screens or mockups, tasks, participants, a testing tool.
- Outputs: First-click heatmaps and success percentages.
Time and effort
Low. Fast to set up and run unmoderated.
Evidence and limitations
Produces quantitative direct-user evidence about initial orientation only; it does not evaluate the full task flow or deeper usability. See Evidence and limitations.
Tips and pitfalls
- Word tasks without the target label.
- Remember it measures the first step, not the whole journey.
- Pair with full usability testing for depth.
Variations
Static image tests, prototype-based tests, and comparative layouts.
Related methods
Need help planning research or facilitating this method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- NN/g, “First-Click Testing.”
Explore related methods
- Tree testing — Test whether people can find things in your structure, stripped of visual design.
- Unmoderated testing — Have participants complete tasks on their own while a tool records what they do.
- Usability testing — Watch representative users attempt real tasks to find where the design helps or gets in their way.
