Why Eye tracking?
Eye tracking has always seemed very promising. After all, in our profession we spend a lot of our time trying to read users’ minds. One of our most powerful tools—usability testing—consists simply of asking users to think aloud while they use our products so that we can understand where they’re getting confused. I describe it as trying to see the thought balloons forming over users’ heads, especially the balloons that have question marks in them. They’re the ones that tell us what needs fixing.
Eye tracking is naturally appealing to us because it holds out the promise of another window into the mind: the semi-magical ability to know what people are looking at. And since there seems to be a strong (though not absolute) connection between what people are looking at and what they’re paying attention to, eye tracking can provide another set of useful clues about what they’re thinking and why the product is confusing them.At the very least, it promises to answer questions like “Did they even see that big button that says ‘Download?’” If the eye tracking shows that people aren’t seeing it, then we know that they can’t possibly act on it, and we should probably give some thought to making it more prominent somehow.
Fifteen years ago eye trackers were for specialists who spent all their time feeding them their specially prepared fuel pellets, writing their own analysis software, and trying to read the resulting runes. Then came the millennium and a quantum leap forward by the manufacturers.
All of a sudden, instead of requiring programming skills, bailing wire, and a soldering iron, eye trackers worked right out of the box. And they came with software that let almost anyone—anyone with $30,000— generate impressive output, especially (God help us!) heatmaps.
Over the years, I’ve sat through countless demos and presentations, and tried to read everything that was written about eye tracking and UX. At one point, one of the manufacturers was even nice enough to give me a loaner for a few months, so I had the chance to do a little experimenting myself. The upshot is that I’ve always known a lot about eye tracking for someone who doesn’t actually do eye tracking.
And here’s what I know: Eye tracking is sexy.
Harry Brignull once did a presentation that drew an analogy between eye trackers and the shoe-fitting fluoroscopes that were used in shoe stores from the 1920s to the 1960s.2 Your child would put his or her feet in an opening at the bottom of the machine, and you could peer in and see the bones inside, giving you the comforting knowledge that the shoes weren’t going to warp your child’s tender feet. It was fascinating, it was science (not opinion), and it offered the promise of proof. And it had lots of sizzle. Heatmaps have the same kind of sizzle.
It sells. Even though we can all agree in retrospect that the shoe-fitting fluoroscope was probably not a good idea, it sold shoes. And blinding people with science still works: eye trackers sell UX services. You can probably charge more if your deliverables include some heatmaps, whether they show anything that’s useful or not.
It seems easy. But it’s not. It’s no trick nowadays to do some eye tracking and create compelling graphics that make it seem like you’re proving something. But actually knowing what you’re doing takes time, experience, and learning.
It’s hard to learn how to do it well. There have been tons of academic papers and manufacturers’ white papers, but no one has produced a how-to book for practitioners.
Name of the book: Eye Tracking the user experience
Author: Ago Bojko foreword by Steve Krug