Slashdot Mirror
Jakob Nielsen Interview on Web Site Redesigns
securitas writes "CIO Insight's executive editor Brad Wieners interviews Web site design usability evangelist Jakob Nielsen about design mistakes like poor search, discusses organizational resistance and common barriers to doing usability reviews, concluding with Nielsen's Adobe PDF and pop-up pet peeves, common redesign errors and budget advice when it's time for a redesign, either for your Web site or company intranet. And just to make it more usable and readable (so you don't have to click through multiple pages), you can read the entire Jakob Nielsen interview on one printer-friendly page with fewer graphics and a bandwidth-saving document size for people using dial-up Internet connections. You might also like to read a previous Ask Slashdot from March 2000 and Jakob Nielsen's answers to those questions."
Honestly?
WHY??
His site violates tons of usability ideas, and while I support his in general KISS (Keep It Simple Stupid) ideas which have been in practice in Industrial Design for decades, he is very much a Luddite.
Grow up Jakob, you make a lot of money ranting against everything, but for the love of god, give it a rest and let the market decide what works and what doesn't.
Department of Homeland Security: Removing the rights real patriots fought and died for since 2001
Talk about relevant. CmdrTaco should take to heart the comment about poor search. The search capabilities of Slashdot are absolutely terrible. You can't specify any options, like searching just artitle titles, article content, or comments. Heaven forbid you want to search for two words together, you can't do it.
Now, when I need to search Slashdot now I just go to Google and do "site:slashdot.org (query)" and pray that something relevant comes up.
Come on Slashdot, upgrade that search function already!
Well, the problem is that PDF documents are just not very suitable for online access because they are optimized for print, and they're big linear documents, and, therefore, they're not very good for search.
Thank you! I've been saying this for YEARS!
Web development should be about developing relevance and usability, not about putting every document you have on an HTTP server. PDF files are fine for e-mail, FTP, etc. where you pull them down and view them locally, but they just shouldn't be on the web. HTML was invented for a reason! Use it!
I'm not sure I've ever heard it called liquid, but I'd like to agree with this particular pet peeve.
There's absolutely no excuse (ever) for forcing the user to view your web page at $arbitrary_page_width. Designers that think they need to force the width to a certian number -- for roundness, right hand menus, or whatever dumbass excuse -- are WRONG. Dead wrong. There is never a good reason to use a fixed width.
It shows complete ignorance of the subject they claim to master by calling themselves site designers.
Imagine if you weren't allowed to use roads because a bus company complained about your driving 3 times. --skunkpussy
Seriously, turn on your Chinese Fonts and take a mozy over to check some of these out:
-- http://tw.yahoo.come x.cfm
(Just to see what a typical newspaper looks like...)
-- http://pchome.com.tw
-- http://www.appledaily.com.tw/template/twapple/ind
This is TYPICAL of the type of design happening in Chinese-speaking contries -- FILL IN EVERY SPACE AVAILABLE WITH TEXT OR IMAGE TO THE POINT THAT NOTHING SEEMS TO HAVE ANY PRIORITY. Blink tags often save the day, believe it or not... A typical TV news channel is a CNN-scrolling-banner-induced NIGHTMARE... To say this happens in ALL Asian countries is a generalization and incorrect, but there is a definite preference and inclination toward simplicity and minimalism in Japan (and Korea to some extent...)
That isn't to say that sophisticated design is not happening in these places -- far from it. It's just that the cultural expectations placed upon design, especially one that is information-based (any media) is different in different cultures.
To me, clutter is confusing and makes the user experience difficult, at best. To others, it is expected and doesn't slow anything down.
So really, who's to say what's usable?
I've once attended a weekend seminar with Mr. Neilsen and other web-usability gurus (Tog comes to mind) and was impressed with what they had to say regarding testing and testing and testing again, so ultimately you could have a cluttered, to-my-own-eyes unorganized mess that could test positive for usability in the right market.
Go figure..
The greatest barrier to usability still seems to be site overdesign. Pages are far more complicated than they need to be (thankfully, much of the blog software is well designed in this regard, giving ample space to the actual content of each page.) Once you pack in a left and right column, and fill the rest of the space with ads, it takes a good deal of concentration to focus on the actual material you came for.
Why are sites overdesigned? Why don't site designers trust the user more? (Overdesigned sites tend to crowd all of their content on to every page via hyperlinks, as if the user can't be trusted to figure out the "back" button.)
To a point, it is about ego: a designer wants to brand every single page in a unique fashion, and that usually means marking up the content and squeezing it down. But there are plenty of ways a designer can satisfy her own ego, and present the content well, with minimalistic designs. The wikipedia is an excellent example of how a lot of features can be made unobtrusive and helpful, letting the content shine through.
In the end, it is really more about company psychology. For the same reason that a bank wants to have a gigantic storefront to assure customers that their money is safe, a company wants its web pages to look expensive and permanent, and the quickest route ends up being a cluttered visual experience as the company shows off the various clever "features" it is rich enough to pay for. A "bare" page bereft of logos and menus and news from other pages seems like an admission of poverty.
But this ends up making the user experience frenetic and disjointed. Oftentimes you can get around this problem by going to the "printer friendly" page where the article or information is presented in a traditional and human-readable fashion.
Protect your liberties. Donate to the ACLU
I think all those pro-WAI critics need a reality check.
The reason why the site is ugly is because he's a crap graphic designer. He says so all the time. It's perfectly possible to produce a website that is both accessible and pretty.
How often have you heard "Oh, that site is pretty damn nice" compared to "Oh, that site is sooo compatible with Lynx!"?
Every time I talk to somebody who uses Lynx? Every time a visitor finds a website through Google (the Googlebot is hardly a state-of-the-art browser, you know).
In any case, you are confusing four separate issues here:
These are all mostly separate issues. Jakob Neilsen talks about usability, not browser compatibility, accessibility or aesthetic appeal. If you don't understand the difference between the issues, perhaps you aren't in a position to criticise. If you think you can have a go at him without even being able to distinguish between these different issues, it is you who needs the reality check.
Bad Panda! No Bamboo for you! In matters of importance ACs will not be responded to. Want to say something critical,OK
I own it too, and I agree. However, I still think that it's a worthwhile read.
The trouble is, when people learn how to design websites, they inevitably copy everyone else. Including everyone else's mistakes. Not only that, but they make a few of their own.
The ones that go on to be professionals inevitably get caught up in doing the actual work and don't think about how to improve their practices enough. So the mistakes get ingrained and replicated across hundreds of designs.
Nielsen's book is good because he has a knack for showing people their designs from a user's perspective. It challenges those ingrained bad habits and gives you ideas on how to approach the field from a better angle.
If you read the book expecting some revolutionary new techniques for web design, then you will be disappointed. But if you read the book expecting a refreshing new perspective and a starting point for improving your work, then it's a damn good read.
I hope he never takes a "clue" from either of them. Design Eye took a minute to load over a fast calbe connection, and Reuseit fills almost half of my browser window with crap that I just need to scroll past.
Why are long flash animations so stupid? THey hardly ever show the company logo or product upfront and think you want to see the entire boring ad.
..tell me the company name and product EARLY ON.
I always close those down.
Annoying me prior to letting me see the content isn't a good way to make me choose your product.
Word to internet advertisers, if your advertisement takes up the whole window
After years of many site authors putting links up on their pages labeled "Stuck in a frame? Break out of it" (which was just a target="_top" self link) and after many authorites just like Dr. Nielsen warning to not use frames, the popular web pages finally stopped using them and moved on to other annoying practices like triple-columned portal sites and static table-based layouts. Once the popular web pages left frames beaten and crying in the corner, most of the amateur designers followed suit and also abused the table-based layouts.
Now, it seems like we've been waiting an eternity for CSS to enjoy the huge popularity that table-based design has been basking in for way too long. Many sites have gone a long way to further that cause. Namely:
Just wanted to say that I absolutely agree with you on this one. A good desiner's eye would make any site more usable. Fonts, colors, font spacing, paragraph spacing, paragraph width, etc etc all affect how usable the page is -- a nice looking page just makes the whole experience more pleasing. Heck, it's why people put art in their homes. It's why we have "interior decorators" and "landscape artists" -- yes, our home would be more functional if instead we spent all that money on useful things like changing around the lightswitches or buying new appliances, but in the end, the beauty of the home plays as large (if not larger) a role as the usability in the overall experience. I for one would absolutely hate to live in a house without plants, without good-looking furniture, without some art on the walls (even just my own photography) -- it would be bland and boring, regardless of how usable it is. The best homes I've seen balance utility and design incredibly -- the best web designers do the same thing to the same effect. Jacob Nielsen has only half the picture.
"!"
And his site, as another poster mentionned, is a sight for sore eyes...
A point he mentions in this article that peeves me is drop downs:
The reason I think that drop-downs are so common is that the programmers want to avoid having to validate the input, but it's not really that difficult to write a little routine that checks that you have one of the authorized abbreviations.
I've had this exact problem arise on one of the systems I'm working on. It's entering a country for your practice location. We started out by leaving it as a text input field, but soon found out that our mapquest links were working only part of the time. Investigation revealed that the country variable in the Mapquest URL can only be US. United States, USA, United States of America, America, U.S. all don't work.
So, do I write an algorithm that goes and heuristically guesses what the country of the user is, or do I friggin use a drop down? - I use a drop down.
So I'm peeved that he feels all proud and manly by stating that programmers are being lazy about validation. Sometimes, a drop down is what is needed. After all, the countries of this planet aren't in a constant flux. There is a domain of acceptable values, so using a drop down is legit.
Especially in this case, when he's basically saying that it's impossible to make a good user experience on top of any operating system...
"!"
it's typography 101. wide columns make for bad readability. the mind loses track of its row and scanning back and forth for each line of text is straining on the eye. for instance, on slashdot, the text would have to be more than 200% its size in order for this simple rule of typography to be obeyed. there are several cases in which Nielsen's recommendations fly in the face of decades and sometimes (as in this case) centuries of applied experience have taught us.
Nielsen, much to his chagrin, is not the voice of god, and he is often flatly wrong if not disrespectful. while it would be nice, as i believe is his goal, to allow the reader to resize their browser to the column width they are comfortable with, the prospect of asking a reader to change their browser window's width for every other page they visit is simply laughable in its utter disregard for the viewer's time and patience.
perhaps if monitors were longer than they are wide, this wouldn't be as much of an issue, but then you run into usability on the desktop where a wider desktop is more conductive to productivity, lessens strain on the neck, and a host of other factors.
mr Nielsen sees things too often in black and white and appears to form many of his opinions in a vaccuum, imho.
He might be confusing the issues but I think you are missing the point and trying to call him on semantics. What I think he was trying to say was that usability can be improved with the proper use of style (and even -eek!- graphics). Browser compatibility and accessibility BOTH fall under usability. And, aesthetic appeal and usability are not mutually exclusive. Rather good aesthetic appeal can increase usability just as often as it decreases it.
Jacob Nielsen, while being excellent at some parts of usability is a real loss at others, namely graphics and visual style. Like it or not there are ways of using graphics and style to HELP the user discern important information from unimportant, headline from sub header, story text from link. And you can see his site uses the bare basics of this.
This is EXACTLY the kind of thinking inside of the box that got us poor websites in the first place. He mentions how programmers use drop down menus because they are easier to verify in his article. And I am sure at the time the programmer though this would be a good thing for the user (things are nice and organized and uncluttered, the user is able to quickly select something without typing it etc. etc..) But in practice it proved to be a problem. And I think this is the case with Nielsen's site.
When I go to his site the first thing I notice is the colors are horrific, unmatching and purposeless. Now you may think I am a crackpot and that color is subjective but it has been scientifically proven that certain colors elicit certain emotions. The next thing I notice is that the text seems unorganized and basically in a big blob. Things most people would look for as navigation links (such as about this site) are at the bottom left of the site mixed in with articles and are generally indistinct. News on the left has the news organization bolded while articles on the left have authors and dates. His use of bullet points is wrong, he doesn't indent the second line of the bullet which is automatically done in html with lists. Anyways I could go on and on.
My point really is this -- we need to open up our minds and stop thinking about things from our own perspective. JN is VERY good at this but, like us all, he blocks out portions of the picture and sometimes those portions are big.
meep
Less work for me to type in NL or nl or Nl or nL or holland or holand or netherlands or neetherlands or the netherlands. (and if you can't limit a text field to accept only 2 letters and in upper case you shouldn't be building websites)
Now it is up to you to program your site in a way that it can work with this. Isn't too hard. In fact is pretty easy. Mysql and PHP already come with tools for this. they can check for similarity between words.
You can argue if dropdowns or text input are better but saying that you are to lazy as a programmer just proves his point.
MMO Quests are like orgasms:
You may solo them, I prefer them in a group.
I've read a few books from this same author and he does have some good points. I don't agree with everything personally, but reading carefully I found quite a bit of information about perspectives that I wouldn't have thought of.
In my experience however, there is a crucial step that is missing. In most of the places where I have worked the "webmaster" is more the artsy type and is not interested in the technical side of the design at all. Where I'm working now, if I showed this article to our primary web designer, he would basically ignore it and continue doing things the same old way because he isn't interested in what he considers to be the technical aspects of web design (OT, once he even told me "I don't care about all that HTML stuff"). I'm sure this is different in large organizations where there are teams of people dedicated to the maintenance of the web site, but in smaller organizations where there are only one or two web designers it is important that the web designer understands *why* he must care about this information (and I'm not talking about nebulous mentions of "you'll save this much $"). Most of the designers I've worked with are not interested in perusing articles/books of what they consider to be "technical" information in an effort to improve the usability and effectivess of the web site they are maintaining.
That is why this seems like only half the story. IMO, it would be very useful to have a good preface on why it is so important to apply these techniques, and only then begin to explain exactly what these techniques are and how to implement them. This would make this kind of information useful to both the artsy, visual web designer and the more code oriented, professional webmaster.