# Test where people start, not where you tell them to click

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Test where people start, not where you tell them to click

ID: MHC-D-RESEARCH-1091 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/test-where-people-start-not-where-you-tell-them-to-click

The first wrong turn may happen before any form appears.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- People cannot find how to begin an important task.

### Avoid when

- A correct first click does not show that the task can be completed. A static screenshot cannot reveal later interaction failures.

### Explanation

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

1. Write the need in the participant’s language without repeating the target label.
2. Record the first selected area and any uncertainty.
3. Compare choices with the intended start, then test the rest of the journey separately.

### Example

Ask where someone would go to practise a difficult conversation, rather than asking them to click Practice.

### Check

Does the proposed label or placement change help a fresh participant choose a workable starting point?

### Limits

- A correct first click does not show that the task can be completed. A static screenshot cannot reveal later interaction failures.

### Evidence and sources

- supports: A first-click test records where a participant begins a stated task on an interface or image. — RS-3940FF26CDAFFDE4. It measures the starting choice, not completion or overall usability. (Definition and limitations.)
- RS-3940FF26CDAFFDE4: First click testing guide — https://www.lyssna.com/guides/first-click-testing-guide/

### Vedokrok editorial review

A first click diagnoses the route, not the whole task

A first-click test is useful because it isolates the opening route choice before recovery, search, or moderator help changes the path. That makes it a sharp diagnostic for labels and information scent. It does not show that the rest of the task works, and the result can move when the task wording, available routes, or interface state changes.

#### The first choice is a routing signal

People tend to choose links and regions that appear semantically close to their goal. Blackmon's web-navigation studies found much higher success when one information patch clearly matched the user's goal, while competing patches reduced success when only one led to the answer. This supports a narrow use of first-click testing: it can reveal whether the opening choice has strong information scent or whether several routes look equally plausible. The paper also warns against generalising the model too broadly, so a first click should be read as evidence about this task and this interface, not as a universal law of navigation.

#### The headline effect depends on how the test is built

A famous first-click claim is that choosing the right first path makes eventual success dramatically more likely. A later MeasuringU analysis found a much smaller gap on five live websites: average completion was 78% after an optimal first choice and 70% after a non-optimal one. In separate tree tests, where search and other alternative routes were removed, the gap was far larger: 80% versus 14%. The useful lesson is not one fixed multiplier. The strength of the first-choice signal changes with the task, the available recovery routes, and how 'optimal' is defined.

#### A screenshot removes some of the interface

Static click tests can still be informative, but they are not a perfect stand-in for live use. In a 2023 randomized study of 130 participants across five websites, first-click patterns on screenshots and live sites were broadly similar on average. Yet dynamic functionality produced important local differences, with the largest first-click gap reaching 40% under the stricter coding scheme. Use a static image when the research question is mainly 'where would you start?'. If hover states, search, expanding menus, loading, or later decisions matter, follow with an interactive test.

#### Task wording is part of the measuring instrument

A route can look successful simply because the task text supplied the answer. Nielsen Norman Group's guidance recommends realistic, actionable scenarios that do not repeat the exact interface wording when that wording would give away the path. The opposite mistake is also possible: replacing a normal term with an unnatural synonym can make the task harder for the wrong reason. Write the goal in language a real participant could plausibly use, then check whether the scenario itself points toward one label before treating the click distribution as a design finding.

#### Record the click before you ask for the story

The observed first choice and the participant's later explanation answer different questions. Preserve the click, hesitation, or change of direction first; then ask what the participant expected to find. Post-task explanation is not automatically unreliable. Guan and colleagues compared stimulated retrospective reports with eye movements and found that the reports could give a valid account of attended information and useful detail about strategies, with a low risk of fabrication in their protocol. Treat the explanation as interpretation around the behavior, not as a replacement for the behavior itself.

#### Three questions before you trust the heatmap

Q: Is every non-target first click an error? A: No. Search, in-page links, shortcuts, and alternate navigation can all be valid routes. Define success around a workable path, not only the route the design team expected.

Q: Is a strong first-click score enough? A: No. It says little about later comprehension, form completion, recovery, or dynamic interaction. Test the rest of the journey separately when those outcomes matter.

Q: Should task wording avoid every word that appears in the interface? A: No. Avoid wording that gives away the route, but keep normal domain language when paraphrasing it would make the scenario artificial or confusing.

**Editorial takeaway:** Use first-click testing to diagnose the opening route, not to certify the whole journey. Give a realistic goal without handing over the answer, preserve the first choice before discussion, and treat plausible alternative routes as data rather than automatic errors. When downstream completion or dynamic behavior matters, follow the first-click result with a live interaction test.

#### Editorial evidence

- supports: Initial route choice is strongly influenced by the semantic similarity between the user's goal and available information patches. — blackmon-2011. The studies support information scent as a useful mechanism for interpreting opening navigation choices. (Abstract; Study 1 and Study 2 summary.)
- limits: The information-scent findings should not be treated as a universal model of navigation across all interfaces and tasks. — blackmon-2011. The author explicitly cautions against generalising too broadly from the reported studies. (Abstract conclusion.)
- challenges: The relationship between an optimal first choice and eventual success varies substantially with the testing method and available routes. — sauro-2013. Live-site studies showed a much smaller completion gap than tree tests, challenging any single universal first-click multiplier. (Table 1; First Choices in Navigation Only; conclusions.)
- limits: Static click tests can approximate live-site first-click patterns, but dynamic functionality can produce meaningful local differences. — sauro-et-al-2023. The randomized comparison found broadly similar distributions on average while still observing substantial differences for some interactive regions. (Study Overview; Summary and Discussion.)
- contextualizes: Task scenarios should be realistic and actionable without giving away the interface path through the wording itself. — mccloskey-2014. Task wording is therefore part of the measurement setup rather than a neutral wrapper around the interface. (Summary and task-scenario guidelines.)
- contextualizes: Stimulated retrospective reports can provide useful information about what users attended to and how they reasoned after a task. — guan-et-al-2006. This supports using post-task explanation as a second source of evidence while keeping it distinct from the observed first click. (Abstract.)
- blackmon-2011: Information scent determines attention allocation and link selection among multiple information patches on a webpage — https://doi.org/10.1080/0144929X.2011.599041 — Marilyn Hughes Blackmon
- sauro-2013: The Importance of the First Choice in Website Navigation — https://measuringu.com/first-choice/ — Jeff Sauro
- sauro-et-al-2023: Do Click Tests Predict Live Site Clicks? — https://measuringu.com/do-click-tests-predict-live-site-clicks/ — Jeff Sauro, Will Schiavone, David Du, Jim Lewis
- mccloskey-2014: Turn User Goals into Task Scenarios for Usability Testing — https://www.nngroup.com/articles/task-scenarios-usability-testing/ — Marieke McCloskey
- guan-et-al-2006: The validity of the stimulated retrospective think-aloud method as measured by eye tracking — https://doi.org/10.1145/1124772.1124961 — Zhiwei Guan, Shirley Lee, Elisabeth Cuddihy, Judith Ramey

Editorial version: 1.0.0 · evidence checked 2026-09-26 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/give-the-user-a-goal-and-keep-your-instructions-out-of-the-result
