What it is
A technique using specialized hardware to record where and how long participants look on screen, producing gaze paths and heatmaps of visual attention.
When to use it
During Prototype or Implement, for high-stakes questions about attention, scanning, and what users overlook.
Why (value)
Shows attention objectively rather than relying on what users think they looked at, revealing overlooked elements and scanning patterns.
How to run it
- Define attention questions and stimuli.
- Calibrate the eyetracker per participant.
- Have participants perform tasks while gaze is recorded.
- Generate heatmaps and gaze plots.
- Interpret with task performance, not alone.
Inputs and outputs
- Inputs: Eyetracking hardware, stimuli, participants, a controlled setting.
- Outputs: Heatmaps, gaze plots, fixation metrics.
Time and effort
High. Specialized equipment, calibration, and analysis.
Evidence and limitations
Gives direct-user behavioral evidence of attention, but looking is not understanding; gaze data needs careful interpretation and is costly and lab-bound. See Evidence and limitations.
Tips and pitfalls
- Do not equate fixation with comprehension.
- Combine with think-aloud and task metrics.
- Watch for calibration drift.
Variations
Screen-based trackers, wearable glasses, and webcam-based approximations.
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, “Eyetracking in UX Research.”
Explore related methods
- Usability testing — Watch representative users attempt real tasks to find where the design helps or gets in their way.
- First-click testing — Measure where people click first on a task, since that first move strongly predicts success.
- Analytics review — Examine real usage data to see what large numbers of users actually do.
