Have you ever wondered why users find your app frustrating? Why they don’t use some new feature(s) you’ve rolled out recently, or why they just seem to miss the blindingly obvious?
It’s not necessarily anything wrong with the application, but in the user’s ability to perceive it. Why? Because of Inattention Blindness. Let’s discuss this interesting phenomenon.
Consider a scenario
You mapped out a brilliant new feature, worked through it with your design and development teams, implemented it, tested it and rolled it out the door. Then, you waited; and waited; and waited – Nothing. Based on your application tracking, the feature is not even being touched – except perhaps – by your power users.
Alternatively, instead of a chorus of praise and well-wishes for the new options available in the app, users are voicing an increasing level of frustration to your helpdesk.
What’s going on?
Maybe users are suffering from Inattention Blindness. If you’ve not heard of it before, according to Wikipedia, Inattention Blindness, otherwise known as perceptual blindness, is:
… failure to notice an unexpected stimulus that is in one’s field of vision when other attention-demanding tasks are being performed … This typically happens because humans are overloaded with stimuli, and it is impossible to pay attention to all stimuli in one’s environment. This is due to the fact that they are unaware of the unattended stimuli.
There is a lot to the concept, so I’ll do my best to summarize it. Inattention Blindness is a phenomena that is related to people’s perception of the information they receive through their senses.
Irrespective of something clearly being in plain sight or–in slang terms–right in front of their eyes, people may not actually perceive it. They physically see it, whether it’s a new button, error message or warning notice, but they don’t consciously register it’s there (or that it’s important enough to them to warrant their attention).
End result? It is effectively forgotten about.
The Invisible Gorilla Test
One of the most famous tests on the subject is the Invisible Gorilla test, which was conducted by Daniel Simons and Christopher Chabris. If you’re not familiar with the test, watch this video.
Users are asked to watch the video, which has two teams passing balls between each other, and count the number of passes by one team.
What they’re not told is that during the video a person in a gorilla suit walks through the middle of the crowd, beats its chest, then walks off. You’d think this would be pretty obvious right? Well the reports differ, but around 50% of people don’t indicate they see the gorilla.
You might think this is strange right? A person in a gorilla suit walks clearly into view, struts around, and walks off. How could anyone miss something so obvious?
Well, without going in to too much depth, there are a number of theories as to why. The scientists have theorized a set of four possible reasons. These are:
- Conspicuity: If an item is not particularly obvious or lacks meaning to the beholder, it may be missed
- Mental Workload and Working Memory: People can only consciously concentrate on a limited amount of information at any given time
- Expectation: The gorilla being so unexpected, it’s filtered out
- Capacity: People only have a limited amount of ability to concentrate at any given time
With so much in our lives to concentrate and focus on, it only makes sense that we have to filter out a large percentage of stimuli, so we focus on the information that is both important and meaningful.
Here are some common examples for us as developers and consumers of web and mobile applications:
- We consume a lot of news from a wide variety of sources
- We send tweets and emails, post Facebook, Instagram, Google+ and other status updates
- There are always new apps or handhelds to try
- There’s new technology to learn or existing technology to improve at
Just from this small list, you can see it can be pretty demanding to know what’s important. And that’s not even including the normal day-to-day work and obligations we have, such as eating, chatting with colleagues and friends, cleaning, work and so on.
So it makes sense that the less we have to focus on, the easier it us for us to perceive the stimuli we receive. This then makes it easier to ensure we pay attention to it and give it the time it needs. Rather at odds with the modern world, wouldn’t you agree?
How does this relate to web applications?
The theory’s all well and good, but how does it relate to web development? Based on an awareness of this phenomena, I believe we need to keep three things in mind:
Consider a common aspect of a standard web application: Errors, Warnings and Informational Messages.
In any web application, the user will need to be notified at different times based on events occurring within it.
- They’ve put incorrect information in a form
- They’ve missed filling out a form field
- Something’s gone wrong in processing a form or page
- You have a new feature to announce
Each of these situations is outside of the normal course of events, so the user is not expecting it. Therefore, you need to bring it to their attention in a clear and meaningful way. I’m not a UI expert, nor am I a professional graphic designer, but here’s a starting set of suggestions for what to do:
Use colors that are synonymous with the intent of the notification:
- Red typically indicates danger or demands attention
- Yellow typically indicates a warning or to beware
- Green or blue typically indicate success or something not too serious
- Use icons which are synonymous with the intent of the notification
- A stop sign indicates something a user needs to know
- A lightbulb indicates helpful information, an update
- Don’t cram everything in at once.
- Too much information forces the user to filter things out (maybe your new feature)
- You increase the chance something will be overlooked
- Draw attention to the most essential choices the user has to make
- Play down the choices that aren’t really required or the user can skip over. This will help users be more efficient
- Provide a progress indicator, yet don’t make it the central focus of what’s required
- If something’s important, don’t make it subtle
- Consistently apply interface elements throughout your application
You may consider animations, fancy colors and icons a waste of time and energy. They may even seem too artistic for your application or client’s budget. But a proper use of them can draw a relevant change or UI element to your users attention. Through doing so, you make the application more meaningful and valuable to the user.
And isn’t the true goal of applications to help users?
Why Not Use a Framework?
Why not make it easy on yourself and use a framework, one that provides a lot of this functionality in-built. Some regularly cited ones are Twitter Bootstrap, HTML5 Boilerplate, Mobile Boilerplate and HTML KickStart.
Out of the box you’re provided with a series of UI components which you can reuse, through your application. You have layout, buttons, breadcrumbs, alerts, tables, forms and more. Additionally, they’re setup to use commonly accepted heuristics which people will understand.
Take a look at the examples below:
Here the buttons have a good size, weight and color choice which is semantically meaningful.
The alerts below are large without being overly generous, convey a clear indication of intent, and don’t look too bad to boot.
I hope this rather brief discussion about Inattention Blindness has helped open your eyes as to what may be limiting the use and user satisfaction of your application. I don’t know you nor your application personally, but I’d suggest if you’re having user interaction issues, Inattention Blindness may be a culprit.
The best thing about it however, is it’s not a disease, plus there are practical steps that can be taken to help alleviate it. If you have time, I encourage you to read the links below in the further reading section, as it is a truly fascinating field of study.
So, do you think your applications are being limited by IB? How can you revise your UX strategy to better reflect its impact on human cognitive processing? Add your thoughts in the comments and let’s get a healthy discussion going.
Matthew is a freelance technical writer who loves making tech content fun and engaging, even entertaining; a professional blogger; web application developer, and editor of Malt Blue, which teaches everything there is to know about the Zend Framework. In his spare time, he loves spending quality time with his two favourite ladies (wife and daughter) and exploring more of Germany, his adopted homeland.