Previous Up Next CHI 96 Workshop: HCI and the Web, Position Papers

Jakob Nielsen

Sun Microsystems
jakob@eng.sun.com

The need for HCI input to web design has been changing rapidly in tune with the change in dominating styles for websites over the last few years:

Not only will users have a relationship with a small number of key websites, the websites will also have to start treating their users as individuals rather than as a nestful of hungry GET-requests all of whose mouths get stuffed with bits of the same juicy worm.

The relationship between a website and a user can be enhanced, for example, by allowing the user to indicate an interest in a specific information object and then inform that user when the object changes or has been significantly updated (you don't want to bother users every time you fix a typo). We have done this at Sun for some time with our bug fixes. Subscribing customers who are particularly bothered by a certain bug can mark the SunSolve page for that specific problem and get notified when a patch is available.

Much as I dislike praising HotWired's user interface, they do deserve credit for their customized What's New page. Not only does HotWired keep track of when each user last visited so that new stories can be highlighted, they also allow users to customize the What's New page to list only stories within those sections of the site that interest them. An excellent way to cut through information overload and focus (and thus capture) a user's attention.

An even more interesting way of supporting user relationships is the personalized view of Ziff-Davis' ZD Net. Users can store an interest profile on the server so that subsequent visits will produce a list of new stories that match their interests. Of course, simplistic information filtering based on keyword matching will never do a perfect job, but they do seem to direct my attention to stories that mostly interest me, so the feature has succeeded in enhancing the relationship between me and Ziff. Future personalized view servers can be expected to use advanced information filtering methods like relevance feedback and various synonym matching ideas and may also allow users to help each other find relevant information.

In the early years, hacking HTML was the main requirement for doing a Web site, and user interface design was an afterthought. Recently, a real HCI contribution has become essential for Web design, with the need to draw upon our existing knowledge of icon design, knowledge elicitation (discovering appropriate information space structures), and usability testing. Users very easily get lost in hyperspace, and much existing hypertext research could benefit web designers as well as the designers of web software. The end of 1995 was probably the high tide for the value of traditional HCI research for the Web. Due to the change to relationship web design in 1996, we may now be more in need of task analysis techniques and ways of finding out what users would like to do even if they don't do it now.

At the time of the workshop, I expect the Web to span about 200,000 servers, and in two or three years we will have a million-site Web. One of the major implications of this cornucopia of webpages is a dramatically increased need for web designs to stand out in the crowd. Consider, for example, the home page for the Web magazine Word. The page is 766 by 1122 pixels large and thus cannot be seen in its entirety by users who do not have large workstation monitors. I would normally be hesitant to recommend such a large design for most user interfaces where one traditionally tries to design rather small dialogue elements that do not overwhelm the user or dominate the screen too much. But for its domain, the Word design may be appropriate. It is probably more important for them to look "cool" than to be highly usable: after all, people don't browse this kind of magazine for productivity reasons.

The implication of the need to be "cool" is that future HCI research must focus much more on what makes interfaces seductive and pleasant and less on what makes them easy to learn and fast to use. At the same time, the need for traditional HCI methods is not going away. On the contrary, Web sites are growing ever larger, with the resultant need for better navigation support and clearer information structure. I think, though, that most of the necessary HCI knowledge is already well-established in the more traditional areas and is simply waiting to be utilized. For example, there is a clear need for usability methods that will allow a large number of "gatekeepers" (business unit content providers) to enhance the quality of Web pages contributed by their local groups to a central corporate Web site. Heuristic evaluation would seem to be a perfect match for this need.

Participant Bio

Dr. Jakob Nielsen is a Sun Microsystems Distinguished Engineer currently serving as the Human Interface Architect for SunSoft Desktop Technology. His main project is strategic planning and design of SunSoft's Internet Desktop. He led the user interface team that designed Sun's WWW pages, co-designed Sun's internal WWW pages (SunWeb), and has contributed to user interfaces for several other WWW projects as well as pre-web hypertexts and online services. His other projects include the user interface to Sun's next online documentation system (AnswerBook2).

Jakob Nielsen's recent books include "Multimedia and Hypertext: The Internet and Beyond", "Usability Engineering", (with Bob Mack) "Usability Inspection Methods", and (with Elisa del Galdo) "International User Interfaces". He also writes the monthly Alert Box column on Internet user interface issues.

Dr. Nielsen's previous affiliations include Bell Communications Research (Bellcore), the Technical University of Denmark, and the IBM User Interface Institute at the T. J. Watson Research Center.


Previous Up Next CHI 96 Workshop: HCI and the Web, Position Papers