How to Run First Click Testing

You’ve designed a new interface. You’ve tested it with users. You’ve even run a few rounds of card sorting or affinity mapping to make sure your structure makes sense. But you’re still not sure whether users can find what they’re looking for - quickly, confidently, and without frustration. That’s where first click testing comes in.

It’s a simple, fast way to measure how well your interface supports users’ goals. You show users a task, and you record which element they click on first - even if it’s wrong. The goal isn’t to catch every mistake. It’s to see where users are going wrong - and why.

What is first click testing?

First click testing is a usability method where you observe users’ first interaction with a task. You don’t ask them to complete the task - you simply ask them to “find the [X]” and record which element they click on first. You may run multiple tasks and multiple users to build a picture of how your interface performs under real-world conditions.

This technique is especially useful for testing navigation, menus, and search features - places where users expect to find something quickly. It’s also helpful when you’re validating assumptions about how users will interpret your interface - for example, whether a button is labelled clearly, or whether a menu item is placed where users expect it.

How to set it up

Start by identifying your key user tasks. These should be realistic, common actions your users would take - such as “Find the contact page” or “Book a flight”. You’ll need at least three to five tasks to get a meaningful result.

Next, recruit users. Aim for 5 - 10 participants - enough to spot patterns, but not so many that you’re drowning in data. Try to recruit users who match your target audience - if your app is for UK-based small business owners, recruit people who fit that profile. Avoid recruiting people who already know your product.

Set up your testing environment. You can do this in person, remotely, or via a tool like Lookback or Maze. Make sure you have a screen recording and a way to capture user input - ideally, you’ll also record their voice or facial expressions if you’re going for qualitative insights.

The test itself

When you’re ready, present each user with a task. Don’t tell them what to click - just say, “I’d like you to find [X]. You can use the interface however you like.” Then, watch.

Record the first click - even if it’s wrong. Don’t interrupt. Don’t guide them. Let them go. If they click something that’s not relevant, note it. If they click the right thing, note that too.

After each task, ask them: “What did you think you were clicking?” or “Why did you click that?” This helps you understand the user’s mental model - not just their action.

What to look for

First click testing doesn’t measure success - it measures intention. So, look for patterns.

If most users click the wrong element, that’s a red flag. If users click the correct element but then get lost, that’s a different kind of problem - one you’ll need to investigate with other methods, like think-aloud protocols or task completion rates.

You may also notice that users click on elements they don’t understand - for example, a button that says “Submit” but has no clear context. Or you may find that users are clicking on links that aren’t visible - perhaps because the design is too dense or the text is too small.

These are not just usability issues - they’re cognitive load issues. Users are trying to make sense of your interface, and your design isn’t helping them. That’s where first click testing becomes valuable - it reveals where users are confused, and where your interface is failing to guide them.

Limitations - and when to use it

First click testing has limits. It doesn’t tell you whether users can complete a task - only whether they click the right thing first. It doesn’t measure satisfaction or performance - only intention.

It’s not a substitute for task completion testing or usability testing with full task scenarios. Use it as a quick diagnostic tool - to validate your navigation, to test assumptions, to check whether your interface is intuitive.

It’s also not suitable for testing complex or multi-step tasks - for example, booking a flight or filling out a form. For those, you’ll need more structured testing.

Practical takeaway

If you’re designing a website or app, and you’re unsure whether users can find what they’re looking for - run first click testing.

Set up 3 - 5 tasks, recruit 5 - 10 users, and watch their first clicks. Record what they click, and why. Look for patterns - and fix the ones that matter.

It’s fast, cheap, and highly revealing. It doesn’t replace other methods - but it’s a powerful tool for spotting early usability issues, especially around navigation and interface structure.

And remember: the goal isn’t to make users click the right thing - it’s to make them feel confident that they can. That’s the real test of a good interface.

If you’re new to UX, start with first click testing. It’s a gentle, low-risk way to learn how users think - and how your design can help them.