June 7th, 2004
The Dangers of Judging Web Designs Superficially
People judge things because it is efficient. We judge everything, and we do it as quickly as possible. We look at newspaper headlines to judge which stories we should read. We judge the speed of oncoming cars so we know if we can cross an intersection. We judge movie trailers to see if we should bother. The faster we can judge, and judge correctly, the more problems we can solve, and the more efficient we become.
Being a web designer I tend to judge a lot of web design. I browse through several dozen familiar web sites each day and a few sites I’ve never been to before. I judge them each in turn. I’m not sure how I judge them: my judgments aren’t always definitive, but I know I’m making judgments because I have a general sense of “I like this” or “I don’t like this”.
It seems that other designers do, too. Many designers with blogs often post comments about other sites. Two recent redesigns, those of mezzoblue.com and blogger.com, started countless conversations on the merits of each. Designers were making judgments like “looks great” or “the white space needs to be rethought”.
Too many of these judgments are superficial, focusing only on a quick visual inspection of the site. They use terms like “look” and “feel”. They also focus on things like color palette choices, validation, which tags were used, or which technique was used to round the corners. They deal with how the site looks or how the code looks.
Yet, we know better. We know that this sort of thing isn’t very accurate or even helpful. First impressions are trivial, and rarely provide insight into the work that was done. We even have this idea crystallized into hackneyed sayings like “don’t judge a book by its cover”.
But, we often do. While making quick judgments is a normal part of being human (and certainly an accepted part of blogging), I think it’s dangerous to do in the web design world. It does the following:
Ignores real usage of the site
Many designers who make quick judgments about a site aren’t even in the target audience of that site, and therefore lack even the most basic criteria for effective feedback. Many designers who critiqued the blogger.com redesign are undoubtedly more advanced than the relatively novice audience the site is intended for. They might as well be critiquing an un-subtitled movie spoken in a language they don’t understand. They can react all they want to, but they’re not experiencing the whole of it.
On the other hand, the mezzoblue.com redesign had a few examples of real usage in action. A few comments written in reaction to the redesign focused on the new commenting system that Dave Shea had implemented. The controversy was that Dave chose to highlight certain comments of people he knew while leaving the rest untouched. This angered some visitors who pointed out that it was placing undue emphasis on those comments without first knowing how valuable they were. The arguments, written by actual users of the site, provided more than enough feedback for Dave to ponder over. This is the sort of non-superficial feedback that many designers could only wish for.
Promotes trivial topics to higher levels of importance
Dismissing a site (and subsequently a product) because it doesn’t validate is an example of one of the most distressing consequences of the worthy movement to code with web standards. Right now, validating code does very little to increase the value of a site to any user, even users who might be designers. Most users simply don’t know and don’t care.
As he was done for several other projects, Douglas Bowman wrote a detailed post in his blog detailing the blogger.com redesign. Worried about how designers might react to the new site not validating, he pre-empted them by saying, “I’ll save you the time and tell you it won’t validate right now�If you’ve already visited Blogger and hit your Validate HTML favelet within a minute of seeing the new design, shame on you. Don’t you have better things to do?”
This comment illustrates the weight with which designers mistakenly endow validation, while perfectly summing up the frustration of a designer and team dealing with real world constraints called users.
Gives new designers the wrong idea
What do new designers think when they read superficial commentary? They emulate it, of course. They incorporate the same thinking into their burgeoning web design skill set. If they hear that this site is good, they’ll assume it is without much thought. This is yet another way to be efficient, but it is a very dangerous way to learn.
In practice, every project has it’s own avalanche of issues. There is no one right way to do anything, and because each site has a different user group then each site has a different set of issues it must deal with. Swift dismissals (or swift acceptance) of web sites suggest a superficial scan is adequate to judge web design.
In a perfect web, we should be able to listen to those who have much more experience than us because they should know better. But even a comment made on a whim can be detrimental to someone looking for solid advice on their current design problems. And beginners are everywhere on the web!
Erodes the credibility of professional web designers
Professional web designers already have a difficult enough job justifying that existence. They’re often seen as simply implementing designs at the whim of their client and not as professionals who help their client create effective designs. How many designers have to justify their decisions to people who have no experience in the design field?
Superficial comments make this worse. It allows others to observe design with the same triviality. Potential clients will take notice, and eventually seek out and hire those designers who create trivial designs. Saying it is so is the first step in making it so.
The overall effect
If designers judge each other superficially it brings down the circus tent on everybody. It lowers expectations and creates a market where looking good is the same as being good. It devaluates user experience to the point where non-audience members have a voice that is just as powerful (if not more powerful) than real audience members. And over time it serves to pull the rug out from under the web design profession.
The judgments we make as designers are important. We should not make any superficially.
Anything we say is everything we say.
Links to this Post
Comments
1. pixelkitty 10:49pm, Tue 15th, 2004
This is a wonderfully written post on a topic I’ve not seen covered elsewhere.
Too many times the casual site visitor or user has an opinion on a design that only encapsulates what they thought something should look like or that it doesn’t pass validation.
There are so many more important things, like making your client happy.
2. Adrian 5:39pm, Mon 21st, 2004
I’ll echo Pixelkitty there. A well thought out article, that has made me thing about my own ‘judgement’ of websites.
3. Gordon 3:49am, Tue 22nd, 2004
I agree to a point. Well… actually I agree completely.
Thankfully I have a day job that involves a fair amount of information design which has given me a good enough understanding of the ’sweet spot’ that content and design have to hit to work for the USERS of the information.
It’s the same whether it’s a website, a leaflet for your VCR or a heavily technical specification.
Need to ponder this more I think.. but not in a comment box.
4. Richard 6:03am, Tue 22nd, 2004
I’m a real fan of balancing usability against design – making something intuitive to use, as well as nice to look at.
I imagine that a lot of people (whether it’s a personal blog or corporate site) use design to express themselves – to try to convey to the reader something about them. And sometimes that expression is not always pleasing to everyone.
But I guess one of the principle characteristics of a really great design is that hardly anyone notices it – it just works, first time, every time, straight out of the box, without placing any demands on the user to learn how it works.
5. Josh 1:18pm, Wed 23rd, 2004
Mark Bernstein, the author of my favorite Alistapart article: Ten Tips for Writing the Living Web, suggest a possible cause for superficial comments:
“One reason design discussion gets reduced to bumper sticker duels is that so much of it has to be typed into bumper-sticker-sized comment forms, instead of posted in thoughtful weblog essays.”
You can find his post here.
6. Adam 9:34am, Thu 24th, 2004
Interesting idea of Mark’s, Josh. Would emphasising the comment form go some way to solving this problem? Overall commenting could increase, and perhaps through averages the mean quality would go down? Or would commenters be stimulated to craft more meaningful comments? Who knows!
Jeff Veen devotes a chapter to ‘barriers to entry’ in his book, Design for Community. It really resonates with me on this issue.
When a visitor comes to your website, does a screen capture, crops, resizes, savesAs, then uploads the graphic to their website, you expect them to be interested in what the visuals of your site represent. You would hope they would also be interested in other aspects of your site, but sometimes words can’t do it justice.
If this was to happen to me, I would be gratified to see someone write more than a flippant one liner to accompany the graphic. Wouldn’t it make sense to invest the same or more effort in expressing your impression of the design?
Some people choose to take their time to tell a story, others are more prolific, perhaps at the expense of quality. Each seems to serve a separate, valid purpose to me. But we all know which we would prefer.
7. Josh 9:51am, Thu 24th, 2004
Adam,
Thanks for the comment. I think you’re right.
I’d like to point out, however, that I think you meant Derek Powazek and not Jeffrey Veen. (I’m assuming this is the Design for Community book you’re referring to)
I’ve heard Derek give a full-day talk on community design, and it was one of the best days of learning I’ve had!
One thing I remember (and deals with barriers of entry) is the “online community’s answer to Fitts’s law” (for lack of a better term) wherein the quality of a post is directly proportional to the difficulty in making it.
8. adam 8:51pm, Sun 27th, 2004
D’oh! yes of course it’s Derek Powazek – i even had the book in front of me but got it wrong. cheers!
9. Michael Almond 9:49pm, Wed 30th, 2004
I like Richard’s Posting:
“I’m a real fan of balancing usability against design – making something intuitive to use, as well as nice to look at”
But, I don’t think the wording is quite right or I may be misinterpretting. I agree with him if he is saying that design is an important aspect of usability. Much more than is credited these days I believe.
Design adds credibility to a site (good, professional design), creates a compelling or pleasant experience for a user, and basically forms the backbone of a Web site interface. Any one out there old enough to remeber DOS? Ughh.
Design is not the same as “art”, though it certainly has a distinctive aethetic style or look that some may like or not based on their own tastes.
But when a design becomes “expressive” as Richard says, it no longer functions as a means of communicating and organizing information (solving problems visually through an interface).
It becomes “art” which, as the snobs at my old job used to say “causes problems instead of solves them”…
I think the kinder way of putting it is that design should aid and not interfere in the primary purpose the user has in your site: to find information or complete a task or set of tasks.
As in all the various mediums, this is called “transparent design” and Richard is correct when he says that when done well, it is a thing of beauty in many ways!
10. Olli Joel 4:26am, Tue 28th, 2004
I just surfed in this great place. But it’s really a pleasure being here. Go on
with this good work.