Protocol
Test where people start, not where you tell them to click
The first wrong turn may happen before any form appears.
When it fits
- People cannot find how to begin an important task.
When to avoid it
- A correct first click does not show that the task can be completed. A static screenshot cannot reveal later interaction failures.
Why it matters
Show the interface with a realistic goal, but no navigation hints. Ask the participant to choose where they would begin. Preserve the actual first choice before asking for an explanation; a reason supplied afterwards is not the click itself.
Steps
- Write the need in the participant’s language without repeating the target label.
- Record the first selected area and any uncertainty.
- Compare choices with the intended start, then test the rest of the journey separately.
An example
Ask where someone would go to practise a difficult conversation, rather than asking them to click Practice.
Check your result
Does the proposed label or placement change help a fresh participant choose a workable starting point?
Keep this limit in mind
- A correct first click does not show that the task can be completed. A static screenshot cannot reveal later interaction failures.
Connected ideas
Useful withGive the user a goal and keep your instructions out of the result
Evidence and sources
Supports
A first-click test records where a participant begins a stated task on an interface or image.
It measures the starting choice, not completion or overall usability.
First click testing guide · Definition and limitations.