First, businesses discovered quality as a key competitive edge; next came science. Now, Donald A. Norman, former Director of the Institute for Cognitive Science at the University of California, reveals how smart design is the new frontier. The Design of Everyday Things is a powerful primer on how - and why - some products satisfy customers while others only frustrate them.
©1988 Donald A. Norman (P)2011 Tantor
The original title for this book was "The Psychology of Everyday Things" and it has not been updated since 1988. It contains mostly pop psychology insights from the '80s rather than design ideas, so if you are looking for information on the actual design process you will be disappointed.
Many of the psychological insights have been refined and unpdated in the two decades since publication and what must have been insightful and modern at the time now seems obvious or too simplistic.
The performance is terrible. The narrator has a Shatner-esque delivery where he randomly speeds up and slows down his reading and then dramatically drops his volume at the end of sentances. I honestly thought there was a problem with my stereo before I figured out he was doing it on purpose.
The author mentions in his new preface that the ideas in the book are timeless and therefore he didn't think it needed updating. However, a significant amount of speculation is done by the author about what computers in the future will be capable of--all of which has already come to pass. There is simply no need for an entire chapter fantasizing about a future where you can have an electronic appointment book.
Apparently, the book is considered a classic in the design and engineering world, but until it is updated it only has value as a historic document.
I have two rules; avoid abridgements and watch out for older texts on contemporary topics. The Design of Everyday Things was produced several years ago and it shows. While it is just filled with worthy insight, much of the material is dated.
Narration is good and keeps your interest. The idea that we should blame bad design and not ourselves for mistake is stated repeatedly throughout the book. To my disappointment I found the examples to be dated. He discusses VCRs as if they were more commonly used than DVDs. At one point he said he envisioned a portable computer that could be taken anywhere plugged into a phone within 5 years. How long has the iPhone been out? It would have been nice if the book updated before making into an audiobook. Turns out that this audiobook was recently released (making it seem like it was a new book) but had been written several years ago.
Potentially. It would be a great reference book to remind myself of good design principles.
The history behind of the important design decisions that we use in our lives (e.g. keyboard), as well as the concepts that will continue to hold over time.
Solid, plain, clear.
Only relevant for certain people, but at the same time for those who understand these concepts already might not learn anything new.
Despite having a nominal publishing date of 2002, the examples in the book were never updated from the late 1980's. This makes the book incredibly old fashioned and quaint to listen to. Although the ideas contained are timeless, the examples (such as PBX phones and floppy disks) are so out of date they obscure the arguments of the book.
The examples. They are out of date and truly irrelevant in this age.
strident, monotonous, and nasal
I would update the examples to ones that are relevant today. There are adults out there now who have never seen the kind of phone systems he describes, the typewriters, or the floppy disk. Every single example from this book is from the late 1980's, and was not updated during the 2002 publication. MAJOR editing mistake.
Someone with more patience for whining / someone who hadn't been told it was a "UX Primer" and was thus completely disappointed.
Huge let down.
I would probably read the book the second time around. This is the first time where the narrator's pretentious and condescending tone really pulled me out of the material.
The story is great and the writing is insightful.
The door story is good.
The design and simplicity of a car versus a radio.
My complaint is on the audio and narrator, not the book. I would probably read the book the second time around. This is the first time where the narrator's pretentious and condescending tone really pulled me out of the material.
Prosaic, pedantic and judgmental with excessive uninteresting personal observations. maybe this is interesting to others, not me
disappointment and boredom
wasted my credit on this
I particularly like the approach the author has towards the design of systems, as something intended to be used by humans (v.s. perfect, precise manual-reading robots.) The use of examples is also extremely helpful.
Probably the explanations behind some of the near-disasters. The fact that poorly designed and somewhat misleading control panels in three mile island contributed to a near-meltdown is a great example of how good (or bad) design can make all the difference in the world.
Peter's voice is clear, with no major accent, and good tone variation.
No extreme reaction, but it was an interesting read.
Some of the topics in this book are covered in later books by different authors. So, in this sense, the book is a little redundant to some other popular books on the strengths and weaknesses of the human mind as a tool for reasoning and decision-making.
Also, towards the end of the book there is some discussion towards future improvements in design in everyday things. As this is an older book (late 80's) and some of those ideas have already made their way into mainstream products. The ideas seem a little silly/obvious 20+ years later, and I had to keep reminding myself of the age of this book when making my way through some of these "forward looking" topics.
I have had this book on my short list of books to read for almost 10 years. I saw that audible had it and figured this would be the fastest way for me to finally consume this book - it kept getting bumped down on the list of my exciting fiction.
I work as a software engineer and it seems that every conference or class I have attended has recommended this book, and for good reason. Design as a whole is a very tough job. Non-designers are having to wear designer hats all the time and failing to understand what that means. This book sets out to explain why things go wrong and what sort of questions should be investigated. This book does that but with WAY to much background - it could (and should) have been written as a few page pamphlet and would probably have had wider acceptance and functions has a reference piece.
This book does not spend a lit of time describing the design of everyday things. There are few (when compared to how much material is in the book) actual case studies, or examples of good or bad design. I found the material very interesting but it failed to live up to what I wanted or needed - a guide to one of the most difficult task in any engineers job, interface design.
I found it really interesting how a book from 1988 is not horribly out of time. There are a few points where you can tell (like when discussing the modern type writer) but the logic and points of interest apply to today as much (if not more so) then they did in the 80s and 90s.
There are no listener reviews for this title yet.
Report Inappropriate Content