| ||||||||||||||||||||||||||||||
Donald Norman, a retired professor of cognitive science, is bothered to no end by the fact that grappling with unfriendly objects now takes up so many of our hours. Over the course of several books, of which The Psychology of Everyday Things was the first, he has railed against bad design. He scrutinizes a range of artifacts that are supposed to make our daily living a little easier, and he finds most of them wanting. Why, he asks, does a door need instructions that say "push" or "pull"? A well-designed object, he argues, is self-explanatory. But well-designed objects are increasingly rare, for the present culture places a higher value on aesthetics than utility, even with such items as cordless screwdrivers, dresser drawers, and kitchen cabinets. In their concern for creating "art," many designers don't seem to consider what people actually do with things. Such disregard, Norman suggests, leads to few objects being standardized: think of all the different kinds of unsynchronized clocks that lurk in microwave ovens, VCRs, coffee makers, and the like--and of all the different kinds of batteries needed to drive them. Why, he wonders, must we reset all those clocks whenever the power goes off? Some designer somewhere, he ventures, ought to develop a master clock that communicates with all other electric clocks in a home--one that, when reset, synchronizes its slave units.
You don't need to be especially interested in technological matters to enjoy Norman's arguments. The book's underlying question is aimed at a global audience: will the design of everyday things improve? If this entertaining and, yes, well-designed book changes even a few minds, perhaps it will. --Gregory McNamee
Product Details
Would you like to update product info or give feedback on images?
|
I highly recommend this book for anyone interested in the design and creation of software, architecture, or consumer products. You will find some dated, quaint information within its pages, such as the descriptions of the "computer notepad" and hypertext (both of which came to fruition with Palm Computers and the Web), but, as a whole, the book is a collection of relevant, interesting material. It is an excellent starting point for the study of design.
For those interested in additional study on software and user interface design (programmers, such as I), I recommend Alan Cooper's books on user interface design, and ANY of Jakob Nielsen's books. In addition, the Edward Tufte trilogy on visual representations is extremely good, although not software-specific.
Norman does a great job of describing why and how we successfully and unsuccessfully use everyday objects with relevant anecdotes. His stories are usually accompanied with lists of principles that explain good design and account for human behavior. For example, the fundamental principals of designing for people are to: Provide a good conceptual model, make controls visible and to constantly provide feedback to the user.
So how does one employ good user-centered design? Norman recapitulates his points at the end of the book by listing the seven UCD principles for transforming difficult tasks into easy ones:
1. Use both knowledge in the world and in the head
2. Simplify the structure of tasks
3. Make things visible
4. Get the mappings right
5. Exploit the powers of constraints-Natural & Artificial
6. Design for Error
7. When all else fails, standardize
It's mandatory reading for any usability software engineer but also an interesting and well written book for anyone who's ever pushed a "pull door" or scalded themselves in the shower (which is all of us).
The central point is simple-- the needs of the user are different from the needs of the designer. The designer might want everyone's actions with his system to be precise, the user might need to have a "good enough" range of precision approximation. The designer wants to make the knobs the same so they look good together, the user wants to be able to tell quickly which knob applies to which function. It's a basic concept that can't (particularly on the Internet today) be repeated often enough.
Norman looks at the kinds of errors people make in usage and discusses how designers can plan to prevent these kind of errors. He discusses some of the basic things that users find valuable and walks the reader through some classic (and often funny, because so recognizable) design errors.
The writing is clean and (with the exception of the aforementioned rambling) very clear. Norman's voice is full of humor and a real passion for the subject, and that voice is conveyed very well by the book.
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|