Rating: 
Summary: Good Info but needs a rewrite
Review: This book contains some good information but needs to be rewritten making it more to the point. It also needs more clear definitions of what it is talking about. It sure did seem to go on and on about things that I think about all the time anyway. Sure does not deserve a 5 rating and a 3 damns it too much so finally I end up with a 4 that seems a bit too high... 3.5 would be fair.
Rating: 
Summary: From the standpoint of an early design student
Review: This book is an incredible examination of the lack of audience research in industrial design. It cites many different examples of things such as digital watches and even seemingly simple faucets, looking into how these new innovations are complicated to its users. How many times have you heard someone blame themselves for being too "stupid" to work their newest digital gadget? Norman looks into these problems from a psychological standpoint and encourages his readers to look at the design of the product and how users should be able to interact with it, rather than blaming themselves for not being able to work with it properly.
Rating:
Summary: Design for everyday Human Behavior
Review: This is one of the seminal works in the field of User Centered Design. Norman wrote this book well before the Windows operating system was as familiar as the Golden Arches--which only reinforces the idea that certain basic usability principles transcend all forms of objects--from glass doors to Windows Explorer. 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).
Rating: 
Summary: Disappointing
Review: Upon opening "The Design of Everday Things", the first thing I noticed was that ironically, the book itself is not very well designed. The margins on both sides of the page are much too small, making it difficult to read the book without wrenching the it open to reveal the text on the inside of the page. The black and white photos of examples are very low quality, and many appeared blurry. There are also several formatting errors. For instance, a paragraph that should have been all italicized *was* italicized at the bottom of the left-hand page, but when it continued at the top of the right-hand page, it no longer was. Finally, there is very little structure to the book. Norman lays out some design principles, but then doesn't provide any system or structure for elaborating on them. In short, I found it difficult to take seriously someone who does not practice what he preaches!
These design flaws aside, I was still mostly unimpressed with the book. Many of the later chapters just repeat what is said earlier, and whole sections of the book fall into the pattern of "Look at this bad example of design. Now look at this one. Now look..." The first few examples in each section can be entertaining and sometimes illuminating, but after them, reading becomes tedious.
I found that 80% of the value of the book was in the first chapter (pp 1-30), in which Norman lays out four important (and good) design principles. The rest of the book consists of no more than repetitive examples, with some misinformation mixed in. (For example, Norman claims that the human mind has a total storage capacity of 125 megabytes, and implies that each "item" stored in memory is represented by the equivalent of ten 0's or 1's. These claims are patently false. See page 67.)
My last complaint about this book is how dated it is. Yes, the design principles still apply to computer user interface design, but whole sections of the book are comically dated. One example: "I am waiting for the day when portable computers become small enough that I can keep one with me at all times. I will definitely put all my reminding burdens upon it... It has to have a full, standard typewriter keyboard and reasonably large display. It needs good graphics... and a lot of memory--a huge amount, actually."
In sum, I was disappointed with Norman's book. It is not well designed and is quite dated, and most significantly, there just isn't very much material beyond the first chapter or two. Look elsewhere.
| 
