User First Marketing Blog

User First Development Blog

Development vs. Marketing Blog

client login
  • Tobii Eye Tracking
  • Web Analytics 2.0
  • UI / UX Development

Blog posts for May, 2010

Mobile eye tracking - part 2 of 3

Monday, May 31st, 2010

Challenge 1: Make the eye tracker small enough to carry about, secure enough to prevent shifting with movement and discrete enough to not make a scene.

Desktop eye trackers include a monitor, a series of cameras trained on the eyes that either stand alone or are built into the monitor, and a recording unit of some kind, both for a steady stream of eye data and video capture of the monitor screen. Mobile trackers include the same, but now a monitor is not needed; instead, there is an additional camera unit, the scene camera. This camera records the scene as the participant encounters it and needs to be ‘attached’ to the user close to same plane and position as the eyes. This is potentially a lot of equipment that now needs to be carried around by the participant.

SR EyeLink w/ scene camera

SR EyeLink w/ scene camera

One of the earlier mobile tracking systems that became available and was reasonably accurate was a modification of the desktop eye tracking system. SR Research took their EyeLink system and added a scene camera. This worked because EyeLink was not a remote system; it was a head-mounted unit and had room along the headband to host a scene camera. This head-mounted unit did not include the recording system and thus was tethered to a processor and hard drive. The cable was rather thick (thickness of a finger) and was limited to 40 feet. The recording system could be placed on a cart and with a long extension cord, could be pushed around after the participant. This system was certainly secure enough, but not designed for mobility or discretion. It was effective for small spaces, such as flipping through magazines, considering a display stand, or evaluating a single shelf set or package in hand. Nonetheless, the headgear was rather cumbersome and definitely drew attention.

Courtesy SMI

Courtesy SMI

Luckily in the last 1-2 years there have been tremendous developments. Scene and eye cameras are significantly smaller and lighter and can be attached either to a cap or to a pair of glasses. Mobile trackers are still tethered; wireless systems are in the works, but so far the data streams are too heavy (with up to 100 data points per second and video from 2 cameras at 30 frames per second). Nonetheless, the cables are small, not much larger than those to your ear buds on your iPod. And, more importantly, they are tethered to equipment that is substantially less bulky - usually a recording device less than half the size of your typical laptop. This can be easily carried in a pouch that hangs over the shoulder of the participant or is otherwise attached.

Courtesy ASL

Courtesy ASL

Which approach is more effective - glasses or wearing a cap? Glasses have certain appeal because they are smaller and less noticeable. With proper straps these glasses can be secured so vigorous head movement does not shift the cameras about. Camera movement can result in a significant and undesirable shift in the calibration (i.e. what the data or video indicates the user is looking at is no longer what the user is really looking at). Glasses are more easy to secure than a baseball cap.

But glasses pose certain problems. They cannot be used if the participant wears prescription glasses (believe me, we’ve tried!). Further, the positioning of the eye camera and cut of the glasses is designed for a certain face structure. Deviate from this standard and the edge of the opening cut into the lens falls between the camera and the eye, distorting the camera’s view of the pupil.

Wearing a baseball cap with cameras attached offers solutions for both of these

Courtesy SMI

Courtesy SMI

challenges. The camera units attached to a cap are more flexible and offer more options for adjustment, allowing for accurate tracking of virtually any type of participant, young and old, with or without glasses, and any nationality. What about the camera shift? We’ve been reassured by the manufacturer that camera shift is monitored and seamlessly corrected via the tracking of the corneal reflection. If this is indeed the case, we’re sold! We have the opportunity to test out such a system in the coming weeks.

There are different mobile trackers available, and they differ not only in the hardware; some use dark pupil, some light, some with or without corneal reflection. Steps to calibrate, record and monitor in real-time varies by manufacturer. The robustness of the systems, especially if tracking in daylight or in particularly ‘bumpy’ environments (such as road car rallies!) varies. Detailed discussion of this will be dealt with in another post. For now, let me just say that not all mobile trackers are the same and do need to be carefully evaluated.

Call to Action Buttons: Designed to Impact User Experience

Friday, May 21st, 2010

I recently finished up an un-moderated usability test; I usually ask open ended questions after every task. Part of the fun and the blog-image-6madness is making sense of the all the juicy comments. For this particular study, I was taken aback by how many respondents mentioned that the website task longer took because all of the” good links” were on the bottom of the page or some were confused by the links themselves.

This got me thinking about Seth Godin (The Big Red Fez) helping users find the banana in less than 3 seconds.

What the website needed were call to action buttons (CTA) above the fold, and the links needed intuitive labels names (“read more” wasn’t cutting here). Calls to action in web design are meant to make people take an action and in user experience they are meant to make a task easier. Creating effective call to action buttons that grab the user’s attention and entice them to click can be challenging. This post will share some quick effective techniques. (For best practices read Smash Magazine’s post on design awesome CTA’s)

blog-image-5

Location, Location, Location,

Just like real estate, placing CTA’s in a prominent location such as the top section of a web page can lead to higher return of investment because users will likely notice it or remember it later, after they have looked at the site’s content. Another way, that CTA’s can be utilized is within the content itself. Why would a user want to read and scroll through the whole page if they have enough information and ready to proceed?  Call to actions buttons within the content in my experience result in user taking action because  they have already skimmed enough content. If you need more than one page to convince your visitors to take action, feel free to repeat yourself. If you offer a product tour or use several pages to explain complex features and options, place your call to action in a consistent position. This way visitors will know where to go when they are ready to take action.

blog-image-32

Language

Having a great call-to-action buttons is not as easy as just designing one from the best practices CTA guide (i.e. using irregular shapes, color contrast, larger sizes),  a great design  with the right language will help  guide users to follow a particular path and get to the valuable information they seek.  Labels on the buttons includes everything from simple things like “buy now” or “add to shopping cart”  and if you’re in the B2B vertical to  ”Download This Whitepaper”  or more specific wording.  A big pink button is pretty hard to miss but the example used design to catch the readers eye but the language of the offer  helps the user make the descions on whether or not they should download this software.

Have you been testing your call to actions? What combination has worked for you, would love to hear your experiences.

Mobile eye tracking - part 1 of 3

Tuesday, May 18th, 2010

For many years eye tracking has been limited to a controlled, virtual environment, making precise data collection and analysis relatively simple:

  • the computer screen doesn’t move,
  • participant movement is limited,
  • and stimulus presentations on screen are generally consistent across participants.

The biggest challenge researchers face is correcting for head movement (turning sideways or leaning forward) and managing point of gaze data on sometimes unexpected dynamic stimuli (pop-ups, animated ads, video, scrolling, etc.).

Nonetheless, it was relatively simple to track samples of 100 or more and evaluate their viewing pattern as they looked at on-screen presentations. Dynamic backgrounds posed a challenge, but as long as all participants looked at the same stimulus, it wasn’t too big of a deal to analyze this. It was time consuming to identify the areas of interest (AOI) for a background that is constantly changing, but once they are identified, everyone’s data can be run against the same AOIs (as identified, for example, in a television commercial). The output is then the same as for static backgrounds: precise dwell time and fixation information for areas of interest that can be aggregated across all participants. And this can easily be plotted on a static image of the background for visualization.

This type of testing was great for websites, TV commercials and software usability testing to name a few, but was less realistic when evaluating stimuli such as shelf displays, package designs, magazines or products in hand. This posed a problem; a golden rule in user research is to test real users in real environments. Eye tracking participants looking at virtual shelf displays on a computer screen just isn’t the same as eye tracking them as they look at actual packages on a shelf (though this certainly is up for debate).

Mobile eye tracker - image courtesy http://www.mangold-international.comThus came the shift to mobile eye tracking - recording a person’s point of gaze as he or she is moving about in a real, 3-D environment. This could be selecting magazines off of a shelf and reading them, moving about a store selecting products off of a shelf, or interacting with signage at a baseball game. The same technology could apply and has been modified for this type of testing, but there have been a number of obstacles along the way involving either the hardware or the software:

  1. Hardware: While hardware has been reduced in scope and size, a fast processor with a big enough hard drive is still needed, as are at least two cameras (one for the eye, one for the scene). The connection between computer and cameras needs to be wireless or all be so lightweight that it’s easily portable. The cameras have to be secured to the head in a way to limit any shift between camera and eye. How to manage these limitations effectively?

  1. Software: The calibration process and recording the data is much the same. The challenge is in the follow-up analysis. How do you identify regions and analyze point of gaze data when the background is constantly changing and is unique for each and every participant? How can you identify AOI rapidly and accurately with such variability? How can we aggregate data across participants when the stimuli varies so significantly? Can it be done to match the stable scene analysis that we are accustomed to, or is it necessary to make a significant paradigm shift in how we approach mobile eye data?

Different manufacturers and engineers have approached and managed these obstacles in unique ways. With the next few blogs I plan to explore that a bit further. I can only provide information based on personal research and experience, and am eager to hear more about experiences others have had. It’s an exciting new technology; although it has been around for years, there have been and continue to be substantial developments that bring this research approach more to the forefront.

Testing Assumptions-Eye Tracking Approach

Monday, May 17th, 2010

 Testing assumptions can be challenging; it can be difficult to put some of our strongly held beliefs under a microscope to evaluate and question. However, being able to discover a wrongly held belief and subsequently improve design or user experience because of this new information is extremely valuable. 

Eyetracking data visualization

Eyetracking data visualization

Recently we tested our and our clients’ assumptions. We conducted a study on how consumers develop their perceptions: what features do they look at and evaluate as they consider a product on a given dimension, such as size or functionality. In this case our client was interested in:

  • perceive the width of a product.
  • how consumers perceive the height of a product.
  • what aspects are looked at as a judgment is made.

Participants were asked to evaluate a hamburger on the dimension of” height”. The assumptions were that users would scan the hamburger from top to bottom; that makes intuitive sense. If you want to determine how tall something is, wouldn’t you look from the bottom to the top and evaluate the distance? A fair assumption, but in this case, incorrect.
*We simulated the desktop eye-tracking portion of the study with the hamburger images.

 
Here is a heat map from our hamburger study; it is very similar to the output from the actual study. The areas in red indicate a high concentration of viewing attention; this is what users spent most of the time looking at. The areas in yellow, or those that have no color, were looked at less. This heat map clearly suggests users spent their time evaluating the center of the hamburger, not the top and bottom.
A closer look shows that there are a few hot spots near the top and bottom of the bun, but they are small and likely due to viewing attention of only a small portion of participants. This is confirmed by a different type of heat map. This output plots the number of participants who looked at a particular element. Notice the concentration of participants who looked at the center of the burger, rather than the top or bottom.burger heat map

 These surprising results prompted us to start asking questions; we followed up with participants and asked them why they were looking at the center of the burger. They explained that without a reference to compare the height of one to another, they instead evaluated each component – the height of the patty, the thickness of the tomato and layer of lettuce, the scope of each bun half. A fat patty would suggest a taller burger.
A few caveats and new questions (good research always raises new questions). These are considerations to investigate further; some also underscore the importance of thorough pilot testing (another topic for another time).
1). Did the wording of the question somehow inadvertently guide them to evaluate the center of the burger more than the overall height?
2). Should the image be presented differently so that the center of the burger isn’t in the center of the screen (thus automatically grabbing attention)?
3). How would viewing patterns differ if burgers were presented side-by-side and how could that output be interpreted?
4). If we had asked participants, without eye tracking, how they evaluate the height of a hamburger, how would they have responded differently? That is, were they aware of their own viewing patterns?

What do think? Have you ever been challenged to test an assumption, what were the outcomes?