Eye tracking measures gaze behaviour
Eye tracking records patterns of visual attention. It can show where someone looked, when they looked, how long they looked, and what they returned to.
That is useful.
But it is not the same as knowing what someone understood.
A fixation is not a thought. A gaze path is not a decision. A heat map is not an explanation.
The value comes from combining eye tracking with careful observation, good tasks and the right conversation afterwards.
Attention is shaped by the task
People do not look at an interface, a shelf, a sign or an exhibition panel in the abstract.
They look because they are trying to do something.
Change the task and you change the attention.
A customer comparing products behaves differently from someone checking delivery details. A visitor trying to find the café behaves differently from someone browsing interpretation. A passenger under time pressure behaves differently from someone exploring.
This is one reason I am cautious about treating eye tracking as a pure measurement tool. Context shapes attention.
Eye tracking shows behaviour before explanation
One of the reasons I still use eye tracking is that it gives us a record of what happened before the participant explains it.
That matters because people are often very good at explaining decisions they did not fully understand at the time.
The gaze replay helps us go back to specific moments:
- what they noticed
- what they missed
- what they expected to happen
- what confused them
- what they ignored completely
That is where retrospective recall becomes valuable. Not as a memory test, but as a way of grounding the conversation in observed behaviour.
It does not read minds
Eye tracking does not tell you what someone thinks.
It does not prove that someone liked something.
It does not prove they understood it.
It does not tell you why they made a decision.
It gives you evidence of visual behaviour. The interpretation still needs care.
This is where experience matters. The danger is not the eye tracker. The danger is overclaiming what the data can tell you.
Why this matters
The most useful findings often come from the gap between what a team expected people to do and what they actually did.
People miss things that looked obvious in a design review.
They hesitate where the team expected confidence.
They scan for words the organisation did not use.
They look for reassurance in places nobody had considered important.
Eye tracking makes those moments easier to find, replay and discuss.
The real value
Eye tracking is not valuable because it creates more data.
It is valuable because it can expose assumptions.
It can show where the task, the interface, the content, the physical environment or the research design itself is not behaving as expected.
That is why I still use it.
Not to decorate a report with heat maps.
To understand behaviour more carefully before making decisions.