February 20, 2005
Donald Norman - "Why Interfaces Don't Work"
Norman, Donald. "Why Interfaces Don't Work" in The Art of Human-Computer Interface Design. Brenda Laurel (editor). Addision-Wesley. 1992. 209-219.
Notes:
"The real problem with the interface is that it is an interface. Interfaces get in the way. I don't want to focus my energies on an interface. I want to focus on the job" (210).
"What are computers for? The user, that's what - making life easier for the user" (217).
The bulk of this article focuses on how interfaces are problematic and how the computer is a terrible tool because it can be used for so much and doesn't specialize in anything particular. He talks about how game consoles are better for users because of their specialized nature.
Product design priorities (217):
1) The user - what does that person really need to have accomplished?
2) The task - analyze the task. How best can the job be done?, taking into account the whole setting in which it is embedded, including the other tasks to be accomplished, the social setting, the people, and the organization.
3) As much as possible, make the task dominate; make the tools invisible.
4) Then, get the interaction right...
Personal opinion:
Norman and i don't share the same opinion on interfaces. I do believe that they currently get in the way, but not for the same reasons. Our main site of disagreement concerns the task.
The bulk of my computer use is not task-oriented - i spend an absurd amount of time futzing, communicating or surfing. I would argue that i'm not in the minority, particularly of consumer users.
For me, it's great that i use the same device to communicate, surf information and write papers - it allows me to multitask in a meaningful way. I don't _want_ specialized devices for communicating and writing papers - i value the ability to procrastinate my paper by communicating with others (otherwise known as collaboration). What i love the most about the computer is its flexibility and the ability that i have to repurpose it over time and given a particular context.
The computer is not simply a tool that i approach with a task. It is a place AND a space and i enter it for its flexibility, just as i enter a cafe for its flexibility. If i could only go to a cafe to talk to people, i would rarely go. Instead, i go to work and complement my working with social interaction. Fantastic.
That said, i'm not a huge fan of most interface. Then again, i'm not a huge fan of the architecture of most cafes - they're simply not conducive for the diversity of uses i want. But this isn't because i don't want interfaces, bodies or architectures - they're all the site of performativity that allows me to interact with them. And they all affect the kinds of interaction that i want to have.
Interfaces affect the task and that's part of the point. Consider the differences in blogging styles that emerge from people who use Typepad interfaces vs. Blogger vs. LiveJournal - three different textbox styles and three different outcomes - the interface matters - it's not something that can simply go away.
Category: HCI
Posted by zephoria at February 20, 2005 5:42 PM
Trackback Pings
TrackBack URL for this entry:
http://www.zephoria.org/cgi-bin/mt/mt-tb.fcgi/3145
Comments
Just an association - "Swiss pattada" by Giorgio De Michelis on designing for multiplicity of uses
at http://portal.acm.org/citation.cfm?doid=769759.769760
Posted by: Lilia at April 19, 2005 1:13 PM
Hmm... I am going to try and argue that what Norman wrote about in 1992 is radically different from your experience in 2005 with an artifact that is "conceptually" the same, yet has shapeshifted into something different. In 1992, I would almost be tempted to agree with Norman, that a computer was a tool that was simply badly designed for almost everyone but the elite users. I would, however, argue that the flexibility of the artifact was not the problem, it was the amorphousness of that flexibility (come on, you had to learn DOS to make the thing do anything).
In 2005, I would agree with you, that a computer is a space because it allows a large number of simultaneous activities of a very different nature. However, this may have to do with a small addition to the computer - that of the Internet.
If you shift Normans discussion from computers in general to specific applications in particular, I think some of the ideas are extremely relevant, including those regarding the task. In 2005 I would say that we have a problem with task-oriented applications. Those still suffer from exactly the same deficiencies as in 1992. Their design tends to ignore the realities of the task at hand and, more importantly, the potential variety of contexts for this task. So maybe Norman is wrong about the computer, myopic even for a 1992 opinion, but I think he gets at least some things right if you shift the same point of view to applications.
Posted by: Irina at February 22, 2005 9:31 AM