Before reading further, watch the video. The goal is to count how many times people wearing white pass a ball around. The video is only 90 seconds. Go ahead, I'll wait.
If you watched at least 45 seconds of it, you should've noticed the gorilla. If you didn't watch past 45 seconds, you may have ADHD. If you didn't see the gorilla, don't worry, most people don't see the gorilla. All they see is amazing lack of athleticism by the people passing the ball (the Harlem Globetrotters they are not). This phenomenon is called "inattentional blindness." Basically, you only see what you expect to see and completely ignore the unexpected. Everybody does it.
Is the World of Analytics Blind?
This phenomenon is especially true in the world of analytics. With most analytics suites, you're not actually looking at what the users are doing. You're seeing only a small subset of those metrics that you have specifically instrumented your system to track (i.e. actions that you expected enough to instrument). Not only that, you're not even seeing the actual behavior, just abstract, numerical representations of the behavior. It gives new meaning to the term "double blind." The issue is that it is the unexpected issues that cause a large percentage of usability problems. Because if you knew something was a problem, you would’ve done something about it already, right?
For some companies, going to great lengths to satisfy customers is the stuff legends are made of. I'm sure you've heard of the department store that accepts the return of a shirt that is not only old and worn, but that wasn't even sold at the store. When every negative tweet can grow to be a PR disaster, it can seem easier to just give in and say the customer is always right.
Earlier this week we gave some suggested
The answer is very simple: struggle. Struggle in a digital context can be defined as: The tendency for a digital user/visitor to flounder or otherwise get lost or confused on your site or application and, as a result, to be unable to fully complete a process.

