Jul 8, 2012

I Hate Stock Photography

The perfect stock photo for this article
"Hate" is a strong word, and while it's very difficult for me to say that I truly hate something, I like to throw that word around liberally to the point where it becomes devoid of any significant meaning.  With that said, I hate stock photography. I hate it, hate it, hate it. Given that I work in an industry that gives so much lip-service to the importance of presentation, user experience, and customer engagement, it's mildly mind-boggling that stock photography is so commonplace across the Web.  It is uninteresting, cliche-riddled, aesthetic-destroying and an overused, last-minute tool that's become the defacto standard when it comes image selection.


Everyone involved in the creation of a website understands this on some fundamental level because we (as the creators of a site) know where the images come from and know that the images we choose are just a paltry handful of a thousand others that represent or show the same thing. But do our end-users notice this? And, if they do, does it have any kind of effect on their ability to use or engage with a site? Of course it does! I wouldn't have asked those questions if the answer wasn't a solid "yes".


The Problem


People don't engage as much or as well with a site when the imagery doesn't line-up with the content or their expectations. To use a stupid example, it would be inconceivable to think that a site for a pet store would do as well if all of the imagery involved anything but fluffy, cute animals. If I replaced every puppy photo on the site to show a 1970 AMC Gremlin, the site's usefulness would come to a screeching halt and engagement would flat-line.

Of course no web designer worth their salt would ever disassociate the content and imagery to that extreme, but when it comes to real world scenarios it's not the extreme examples that are the problem; it's the subtle and often overlooked commonalities that people pick up on. Is that businessman on the home page a member of the organizationIs that lady with the headset really a customer service representativeIs that building shot tied in any way shape or form with the company itselfIn spite of what some people may say, the end-user definitely picks up on these common threads and subtle incongruities when they look at a website, even if they can't fully articulate what the problem is.

One of the biggest issues with stock photography is that people just "know" when something isn't right. This is especially true when it comes to shots of people.  Ever notice how the lighting in a photograph is just a little too clean or how the subjects' teeth are a little too white? Is the the angle of the shot just a bit off-center but not by so much that it would ruin the composition? These are all subtle signifiers that scream "fake" to users.

I won't get too far into the details as Jakob Nielsen over at UseIt.com did a more than suitable job of articulating this point 2-years ago in his study of photo content.

In Nielsen's own test, he found that when people were presented with biographies with both image and text content, users spent 10% more time examining employee portraits than they spent on reading biographical text. This is in spite of the fact that in terms of volume and space used, the biographical text was the predominant element. By comparison, generic stock photography was largely ignored to the point that it's placement and subject matter was largely irrelevant. Suffice it to say that if it isn't "real", it's not meaningful, and if you're a business that takes their web presence seriously, then it should concern you if large sections of your website are being wasted or ignored.

The Solution



Blow it up, start over, and really think about the real estate that's being wasted on your site.  In an age when illustrators, vector artists, and freelance photographers are plentiful, there's no rhyme or reason to saturate otherwise good web content with generic, ineffective stock photography.

Even in instances where budget is a concern and designers have to bite the bullet, there's absolutely no excuse for not putting in the time and effort to find stock imagery that "works". Whether it's because a particular image hasn't already been purchased by a thousand other people, or because it provides a better thematic fit, being able to deliver a final showpiece with imagery that works speaks volumes about the time and care that went into the initial build of a site.

May 19, 2012

Meer.li

The folks over Meer.li have setup a new mini-site to highlight some of the best examples of mobile application design. It's more or less another echo-chamber where other designers can spend their time showing off their work to other designers, but it's always nice to have a compartmentalized hub to go to see what others in the industry have been developing; especially in the mobile space, where we've only recently started to see uniform standards and REAL design innovation start to emerge.

Head on over if you're interested in gawking at the work of others, or if you want to sign-up and get your work gawked at.

May 6, 2012

Another One Bites the Dust...

Posted by: 

While I'm not one to make flippant, short-form blog posts, there are times when I'm so absolutely thrilled with a sea change in our industry that I cannot help but only comment on it due to overwhelming glee.

As both an independent consultant and an agency suit, I will not have to support IE7 anymore. That's right, folks, Internet Explorer 7 is dead to me.

IE 7 currently eats up around 2.5% of the browser market with IE 6 (the step-child of the family) covering approximately 0.9% of the market. In total, that's 3.4% of the market that's using browsers that are so outdated and bereft of any support for modern web technologies, that they may as well be functionally useless at this point in time.  And while I'm not necessarily thrilled at the prospect of having to drop 3.4% of the market, that 3.4% represented countless hours of support, workarounds, and a level of hack-fu nonsense that made supporting them impossible to sustain and costly from a development and post-launch support perspective.

In the end that means far fewer headaches during the development cycle, quicker turnarounds on projects, and lower costs for me and my clients. If some of the biggest websites (Facebook, Gmail) and some of the biggest development platforms (Drupal) refuse to support that beast, then I'm more than happy to follow suit to retain my sanity.