UX Magazine

Defining and Informing the Complex Field of User Experience (UX)
Article No. 1166 January 6, 2014

Book Excerpt: Eye Tracking the User Experience

Many UX practitioners seem to be divided into two opposing camps: those who are pro eye tracking, and those who are against it. The proponents seem to want to use eye tracking for every study, regardless of its objectives. The opponents, on the other hand, claim that eye tracking is just “smoke and mirrors” and does not have much value. As is generally the case, the truth lies somewhere in the middle. Eye tracking can be a valuable addition to some UX research and ineffective, or even wasteful, in other cases.

The Three Questions

The decision about whether or not eye tracking is appropriate for a study boils down to three questions. Figure 2.1 illustrates the process I go through when considering eye tracking as a method for a study. Typically, this is an implicit exercise unless I have to explain to the stakeholders why using eye tracking is or isn’t a good idea.

Illustration from Eye Tracking the User Experience by Aga Bojko

Figure 2.1 - A set of questions to determine whether or not eye tracking is a suitable method for a research study.

The first and most important question is “Will eye tracking generate actionable insight that addresses my study objectives?” This is not to be mistaken for “Will eye tracking tell me something I don’t know?”

Eye tracking will almost always reveal something new and perhaps even interesting, which is undoubtedly tempting. However, that insight may not be able to inform any decisions that have to be made based on the research findings. To justify using eye tracking in your study, your answer to the first question should be “yes.” But that’s not enough. There are two more questions, and you need at least one more “yes” to proceed.

The second question encourages the researcher to reflect on the economy of the selected approach: “Is eye tracking the simplest method that would answer my study questions?” If other, more conventional research methods (e.g., observation and user interview) can answer the study questions (which is, in fact, often the case), the use of eye tracking may be unjustified.

The third and last question, “Does my study need a buy-in boost?” should resonate with many UX researchers. You can’t make a difference if you don’t have others on your side, and that sometimes requires adding “color” and perceived credibility to your results. Even if the answer to the second question is “no,” a “yes” to this one gives you the green light, as long as the first question is a “yes” (meaning you have made sure that actionable insight will result from eye tracking).

Actionable Eye Tracking

When eye tracking proponents state reasons for using eye tracking, they frequently frame them as “Here is what eye tracking can tell us.” For example, “Eye tracking can tell us about users’ search strategies and decision-making processes” or “Eye tracking can determine what users find interesting.” These statements are not incorrect. However, they are vague and not very helpful to those trying to figure out when to use eye tracking in their studies.

Rather than focusing on what eye tracking can tell you … ask yourself, “Why do I need to know this?”

Does it matter that you can identify a visual strategy employed by users to find the correct drug among others (see Figure 2.2)? Or that you can find out how interesting each area of a Web page is? While it is certainly true that some UX research (especially the more academic research) aims to explore how people interact with products and interfaces in general, as UX practitioners, we must often focus on gathering actionable information. We conduct research to inform decisions. “How can we improve this product?” or “Is this product ‘good enough’ to be launched?” are the high-level questions that our studies typically have to answer. Eye tracking can provide copious information, but most of it may never be useful for answering these kinds of practical questions.

Illustration from Eye Tracking the User Experience by Aga Bojko

Figure 2.2 - You could collect and analyze eye movement data from pharmacists looking at drug labels when filling prescriptions, but how can you make these findings actionable?

Let’s say that furniture assembly instructions were the object of your study (see Figure 2.3). Your eye tracking data revealed that participants spent 10 seconds looking at the front cover before opening the booklet and reading the instructions. If your study goal were to assess instruction comprehension, this is not a useful finding. The same information could be considered useful, however, if the goal of the study were to evaluate the effectiveness of new advertising placed on the cover.

The starting point is always the high-level study objectives. More specific research questions should be then developed to target each of these objectives. Once those are in place, the next step is to identify the appropriate methodology for the study, which could but does not have to include eye tracking. One unfortunate but common practice is to decide to conduct an eye tracking study before specifying the research questions. Don’t do it. You cannot possibly know which methods to use without knowing what the study is trying to accomplish!

Illustration from Eye Tracking the User Experience by Aga Bojko

Figure 2.3 - Eye movements of a person reading instructions can reveal both useful information and information that is of no use to the researcher and stakeholders. It all depends on the study objectives.

Just as bad as having no objectives or clear research questions is the infamous, “We just want to know where users are looking.” Let’s settle this once and for all: This is not a good enough reason to use eye tracking. Doing eye tracking just because you want to see where people are looking is like eating donuts for breakfast, lunch, and dinner just because you can.

So rather than just focusing on what eye tracking can tell you, you should ask yourself, “Why do I need to know this?” or even better, “What type of decisions do I want to be able to make based on the study results?” These questions will help you look for actionable insight and determine techniques that can gather it.

Figure 2.4 shows an overview of the actionable insights that eye tracking can generate and the kinds of decisions it can help you make. This information will help you answer the first question from Figure 2.1, “Will eye tracking generate actionable insight that addresses the study objectives?” If there is no overlap between your research questions and what you see in Figure 2.4, you should consider employing methods other than eye tracking to find your answers.

Illustration from Eye Tracking the User Experience by Aga Bojko

Figure 2.4 - Types of actionable insight that eye tracking can generate.

 

Cover of Eye Tracking the User Experience by Aga Bojko

To read about actionable qualitative and quantitative research findings that can result from eye tracking and find examples of effective eye tracking in action, pick up a copy of Eye Tracking the User Experience by Aga Bojko. You can use the code "EYETRACKUXMAG" for a 20% discount when buying a copy from Rosenfeld Media.

ABOUT THE AUTHOR(S)

User Profile

Aga Bojko is a UX researcher with a passion for designing studies to answer difficult design- and business-related questions. Currently, she is a VP of User Experience at GfK Custom Research North America, where she leads the Bay Area UX team.

Aga has over ten years of experience with various types of eye trackers that she has used to conduct UX research with software applications, websites, instructional material, pharmaceutical labels, and consumer product packaging. She's tracked (for a good reason) a wide range of visuals, from butterflies flying across the screen to fresh meat in grocery stores.

Aga holds a BS in Psychology from the University of North Carolina at Charlotte, an MS in Human-Computer Interaction from DePaul University, and an MS in Human Factors from the University of Illinois at Urbana-Champaign.

Add new comment

Comments