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."

24 of 248 comments (clear)

  1. Thankfully by Anonymous Coward · · Score: 5, Informative

    His website, http://www.useit.com/, hasn't been redesigned and is still as useable and pretty as ever.

    1. Re:Thankfully by 0racle · · Score: 4, Funny

      My eyes! The goggles, they do nothing!

      --
      "I use a Mac because I'm just better than you are."
    2. Re:Thankfully by c0ldfusi0n · · Score: 5, Interesting

      Pretty? Please, his site is ugly. I'm a webdesigner and i can tell you that if i'd deliver such a product to pretty much any customer, they'd slap me back to my office. I think all those pro-WAI critics need a reality check. True, a website such as his will probably never have any compatiblity issues with any current, past or future browsers. But it's just plain ugly. They need to realize that you can make a pretty websites (even with a thing they call images!) AND still be compatible for all computer browsers and platforms, you don't need to lower the eye pleasure to raise respect. How often have you heard "Oh, that site is pretty damn nice" compared to "Oh, that site is sooo compatible with Lynx!"?

      --
      A computer makes it possible to do, in half an hour, tasks which were completely unnecessary to do before.
    3. Re:Thankfully by Anonymous Coward · · Score: 5, Insightful

      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:

      1. Aesthetic appeal
      2. Browser compatibility
      3. Accessibility
      4. Usability

      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.

    4. Re:Thankfully by beakerMeep · · Score: 4, Insightful

      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
  2. Why should we listen to Jakob Nielsen? by veddermatic · · Score: 5, Insightful

    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
    1. Re:Why should we listen to Jakob Nielsen? by occamboy · · Score: 4, Interesting

      I know I'll get modded to Hades for this, but I can't help but asking: Am I the only person who finds Mr. Nielson's site to be painful to use?

  3. Slashdot's (lack of) search capabilities by MrBlue+VT · · Score: 5, Insightful

    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!

  4. Redesign... useit.com! by mikis · · Score: 4, Informative

    With all due respect to Mr. Nielsen, he could have started by redesigning his own site, useit.com. It may be "usable", but it is... less than beautiful, to say so. He could take clue from this guys:

    Design Eye for the Usability Guy and
    Reuseit: useit.com redesign competition

  5. favorite usability resource by Nspace13 · · Score: 4, Informative

    the w3c tip index is my favorite usability resource. the word of mr nielsen is second. not quite everything nielsen says is right in every situation but everything the w3c suggests is a suggest worth the weight of my toshiba laptop (a hefty 7 pounds) in gold.

    --
    steal this sig
  6. PDFs by Bongo+the+Monkiii · · Score: 4, Insightful

    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!

    1. Re:PDFs by Jeff+DeMaagd · · Score: 4, Insightful

      I'm not sure if web designers necessarily understand PDFs.

      I think PDFs are essential for datasheets and manuals. For a datasheet which has hundreds of pages of text and images, having a reasonable expectation that it will look consistent no matter the display medium is important. HTML doesn't even seem to have a consistent page break, footnote or header mechanism for each page. Also, for fill-in forms, you get WYSIWYG text entry, which is especially nice for government forms.

      Searching in a PDF is easy enough, Google does it by default. Acrobat reader's Find utility finds it reasonably quickly enough.

      Which isn't to say that web sites should rely on PDFs.

  7. Re:Fras by Violet+Null · · Score: 4, Interesting

    Basically, because it breaks how people navigate pages.

    1) You can't bookmark an individual page. In that scenario, you can only bookmark the page that holds the frameset.

    2) Similarly, you can't link to an individual page. If you do, they'll get that _just_ that page, no table of contents.

    3) If you hit the refresh button, it refreshes the frameset page, which puts you back at the "default" page, not the one you were looking at.

    4) Doesn't work with the "History" that browsers keep.

  8. link to Tattered Cover instead, please by ClarkEvans · · Score: 4, Informative

    You can also buy this at the Tattered Cover -- the bookstore which did not turn over purchase records to the government when asked; and defended the right to privacy in
    court.

    (I'm not in any way associated with the cover, and this is not a referrer link)

  9. liquid? by spottedkangaroo · · Score: 4, Insightful
    Neglect to use a liquid layout that lets users adjust the home page size.

    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
    1. Re:liquid? by trisweb · · Score: 5, Insightful
      "There is never a good reason to use a fixed width."

      Never is a strong word... the biggest argument I have against this is that my eyes hate to read a line of text which spans across my monitor. This is just my preference, but I have a feeling many people share this pet peeve -- if I find a site which is too wide for my eyes, I have to resize my browser window, which is not something a user should have to do to view a site.

      Most designs rely on fixed widths because the page can be controlled; otherwise the widths are unknown and all sorts of things start looking like crap -- images, for instance. Lets say you have a 400 pixel wide image, and your fluid page is *usually* big enough (on my monitor) so that whatever design element it sits in is large enough to contain it. Now let's say someone looks at it in 640x480 -- the image probably overflows the design.

      When you just have text data, and it looks like crap (Nielsen's site being the prime example), then yes, fluid designs are preferable. But when you start trying to make a site look good, be more usable, be more accessible, and work well while providing useful content in a very eye-pleasing form, then you need some measure of control of the look, and fixed designs can provide some of that. Now of course there are fixed pages which are absoulutely horrible -- just like any design, using fixed width requires thought, and some designers don't have that capability, and I'm sorry if you come accross one; but fixed widths can be useful in making a web site look better, which in my opinion improves the user experience as much as any of Nielsen's tips.

      --
      "!"
  10. slashdot redisigned? by Divlje+Jagode · · Score: 5, Interesting
    Website a list apart did the exercise of redesigning slashdot using CSS. The article was called Retooling Slashdot with Web Standards. A more detailed version is available here: Slashdot Web Standards Example.

    This is the most interesting claim:

    Most Slashdot visitors would have the CSS file cached, so we could ballpark the daily savings at ~10 GB bandwidth. A high volume of bandwidth from an ISP could be anywhere from $1 - $5 cost per GB of transfer, but let's calculate it at $1 per GB for an entire year. For this example, the total savings for Slashdot would be: $3650! All of that for just a couple of KB.
    The article has even been discussed in slashcode. Gathered from the discussion, there appears to be at least one engine (elixss) which uses CSS templates.
  11. I'll never forgive him! by autopr0n · · Score: 4, Interesting

    for comming up with the "split long documents into seperate pages, because users don't understand how the scrollbar works, and would much rather wait a minute or two while their slow-ass modem loads up the next page" advice. Which ungodly numbers of people followed.

    --
    autopr0n is like, down and stuff.
  12. Re:Personal pet gripe... by thulsey · · Score: 5, Insightful
    I'm guessing you've never seen a Chinese Newspaper (or a Chinese portal site, for that matter... yikes!)

    Seriously, turn on your Chinese Fonts and take a mozy over to check some of these out:

    -- http://tw.yahoo.com
    -- http://pchome.com.tw
    -- http://www.appledaily.com.tw/template/twapple/inde x.cfm (Just to see what a typical newspaper looks like...)

    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..

  13. overdesign by sdedeo · · Score: 5, Insightful

    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
  14. Pet Peeves by Tojosan · · Score: 5, Interesting

    He mentioned a couple of my favorite pet peeves including PDFs. But I've got a few others:
    1) Site inconsistency - having totally different designs between pages at the same site. This is often a navigation change, but could include color schemes, font choices, and text/graphic alignment.
    2) Links off the page you are on - often missing are links to the main site page, as well as links to pages within the section of the site you are currently visiting.
    3) Inconsistent content - one time a link is html, the next a text file, and the third a PDF. That is worse than every link being a PDF.
    4) Lack of a link to send the site maintainer an email.
    5) Lack of links to send anyone in the company an email. See this quite frequently.
    6) Overall lack of anything but marketting buzz on a website, not a usability issue per se but makes the site worthless.
    7) Inconsistent link behavoir - some links open a seperate browser, some don't.
    8) Failure to warn about popups! Personal opinion here, but a site should warn you to expect a popup and what your expected action should be if it is at all going to be unclear.
    9) Webforms for submitting a contact request that are just plain broken or don't point to a valid address.

    Also I've got to put in my vote for getting rid of long long long pages, experience has shown, most users won't scroll or as he said, won't retain if they do scroll.

    I'll second that motion on search being broken, heck, my company's internal and external websites are worthless in that respect.

    I've ranted enough, be well.
    Tojosan

  15. Frames Weren't Practical by SeinJunkie · · Score: 4, Insightful
    The worst part about frames was that they quickly became a novelty item for everyone getting a page out there. This was mainly because it was the cheap and easy way to split up your navigation from your content. Because frames were so easy to use, they were often left alone and amateur site designers assumed that their existing non-framed pages could be left alone to work with their new framed layout. The result was framed pages often externally linking to more framed pages and ending up with non-relevant frames over or beside other frames. Nobody was properly breaking their sites frames when visiting a new frame (the proper element to use in an a href tag was target="_top"). In short: framed chaos.

    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:
    ... to name just a few. Oh, and the time you save in loading the framed index page only once can't begin to compare to the time you save loading a single style sheet for layout rather than loading tons of table alignment data.
  16. I like this guy 50% of the time... by pVoid · · Score: 4, Insightful
    Sometimes, he makes good points. Other times he makes ignorant points.

    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.

  17. you have a point, here's why. by vena · · Score: 4, Insightful

    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.