Ask Eric: Questions & Answers

October 22 , 2001 – submitted anonymously

Question: What is ergonomics in graphics?

Eric's response: There are a large number of ergonomic principles that apply to the design of graphic elements for Web sites. There are issues of text legibility. You have seen images were there is insufficient contrast to allow users to easily read the labels. There are issues of affordance. You have seen images where it is not obvious if they are clickable or not. There are issues of visual noise. You have seen images that clutter the page and distract the user. These are all ergonomic issues with a body of research guiding our approach.

Beyond the classical usability issues there are a set of psychological effects associated with images. The graphic work does much to create our impression of the site. At HFI we have evolved a whole methodology for systematically testing the graphics against branding objectives. We can make alternative graphic treatments and collect user data to determine which is the most "cluttered," "professional," "warm," and "cute" (or whatever branding terms apply). I consider this psychological component a major aspect of the ergonomics of graphic design.

May 18, 2001 – submitted by Jeff Tar of Northbrook, IL

Question: In your opinion, what are the differences between an Information Architect and a Usability Architect?

Eric's response: To begin with the obvious, you can find people with all sorts of titles. But what really matters is a person's skills and the knowledge they possess.

Having said that, let me generalize about the "Information Architect" title. Information Architect is a fairly new term. It usually means someone who organizes material, most often for presentation on the Web. Unfortunately, most of the practitioners I have seen have inadequate training. I have usually seen work based on intuition, with limited scientific basis or systematic methodology.

A "Usability Architect" is more commonly called a usability engineer, human factors specialist, software ergonomist, personal subsystem designer, or engineering psychologist. All these titles refer to a profession that goes back to World War II. The profession requires a substantial education. It deals with issues of organization, but also with a far-reaching set of issues concerning task flow design and navigational mechanisms. It uses a massive body of scientific research to address detailed issues of color, layout, operation, and wording. It provides a systematic methodology, incorporating data gathering and usability testing. Practitioners generally have advanced degrees in the field and are often board certified.

Again, I certainly do not care about titles – what counts are skills and performance. But the title "information architect," in my experience so far, has been a warning light. If I seem strong on this issue, it is because I have seen the work of many Information Architects and found it to be a poor reflection on the user-centered design world.

March 1, 2001 – submitted by Raymond LaBrecque of Holyoke, MA

Question: OK, so everybody is going "Web wise" and touting all the latest buzz words and acronyms. Nothing new. The S/W industry has always been about the latest and greatest. After all if you're not on the 'bleeding edge' you get left behind... Fast.

As a S/W engineer focusing in process control and user interfaces, I've been on the practical side of usability testing and U/I design for years. The latest newsletters were real enticing (even though I am doing MMI vs. Web Pages...) But I still stutter & stumble over words/phrases like 'Heuristic Evaluation". Just what does this mean? In plain English please...

Eric's response: Hey, process control is one of my FAVORITE types of project. It is a wonderful and valuable application of usability engineering. There is often so much to offer. I remember working with a glass factory and seeing that oil, water, and air were all controlled by identical-looking valves, resembling the kind you use for a garden hose. For this factory, it was an insight that the valves should be labeled. Before, the staff would just trace the tangled tubing to see where it came from. They thought they should have markings so they could reset the valves to their original position after the equipment was turned down!

Anyway, I'll stop digressing and answer your question. Heuristic evaluation is a review of a design based on a set of rules of thumb. These general principles include things like "Be Consistent" and "Provide Feedback." You are supposed to review the application, asking yourself if it is consistent, if it gives feedback, and so forth. It is not terribly useful because it is so general, but it is better then nothing. The web-oriented principles are not bad for factory automation. But you need to include a set of issues about safety and very frequent usage.