HomeGroupsTalkZeitgeist
Hide this

Results from Google Books

Click on a thumbnail to go to Google Books.

The Design of Everyday Things by Donald A.…
Loading...

The Design of Everyday Things (1988)

by Donald A. Norman

Other authors: See the other authors section.

MembersReviewsPopularityAverage ratingMentions
3,628471,452 (4.09)24
Recently added byterrythomas, private library, PennAdams, clmerle, liuxl89, Sam.Huang, bridgelab, Yirba, ph_, nashby
Legacy LibrariesDavid Foster Wallace

None.

Loading...

Sign up for LibraryThing to find out whether you'll like this book.

No current Talk conversations about this book.

» See also 24 mentions

English (45)  Italian (1)  Danish (1)  All (47)
Showing 1-5 of 45 (next | show all)
Good, smart points; too often people blame themselves for errors with devices when the designs are faulty - something even as "simple" as doors.

The lessons here are undortunately not well learned, 23 years later, perhaps even less so as products are rushed to market today. Another one for the toolbox. ( )
  Razinha | May 23, 2017 |
Useful for any architect or designer and interesting for anyone who has ever groped in the dark at home for a light switch and turned the wrong light on.
That so long has passed since the book was written and still the same mistakes are repeated on new products just emphasises the value and validity of the author's observations. ( )
  sefronius | Jan 31, 2017 |
A thought-provoking look at a little explored area of everyday life. ( )
  bensdad00 | Jan 10, 2017 |
Absolutely brilliant and easy to read. If you internalize the ideas in this book it has the potential to completely change the way you look at made things. Its fascinating to see the challenges that presented themselves almost 30 years ago and how some have changed and others haven't at all. It's also crazy how many modern devices and systems Norman predicted.

This is definitely not just for designers, but if you design things or purchase things that others need to use (say software or desks for a company), this should be required reading. ( )
  typo180 | Jan 2, 2017 |
The main question in my mind after listening to this audiobook is easily enough answered: How old IS this book, anyhow? In the introduction the author talks about how the book isn't dated. Well, it was originally published in 1988. One of the most talked-about pieces of technology discussed is the videocassette recorder. The VCR. The computers being discussed are about a step beyond the ones that could add three numbers together using a bank of systems that would fill a room. Some of the book is relevant no matter what, as the prologue or forward or introduction or whatever it was points out. But not all of it is.

Much of the point of this book is: "When people have trouble with something, it's not their fault. It's the fault of the design." And I don't buy it. Maybe it's because I have less faith in humanity than the author does, but – well, I've seen it (including, to be honest, in myself). I did not like the book [book:Wizard's First Rule], but something I love and always use is the explication of Wizard's First Rule: "People Are Idiots". Yes, it should be obvious whether a door needs to be pushed or pulled to get the thing open – but in most if not all of the cases I've seen it's not actively hidden. In my experience, people just don't read.

Example: I can't tell you how many emails I've sent, only to have to reiterate some or all of it almost immediately. I used to run an international online-based Secret Santa, and every year after the emails went out I braced myself for the slew of responses asking questions that were answered in the initial email. Because people don't read.

I've learned that when I ask two questions or provide two pieces of information in an email, the second one is going to go completely unnoticed. More than two? Forget it. Now, I've long ago learned that my tendency to wordiness won't fly in business emails – I've learned to pare it down. Still, people don't read.

Recent example: in reply to a question from one of my bosses, I wrote "I’ve attached [three pieces of documentation for a delivery]; it looks like there was no delivery ticket created." That was the first line of my email. One of them replied with "Do we have delivery ticket?" I sat and stared at it for a couple of minutes, and then just wrote back "There was no delivery ticket, as far as I can see". I just don't understand.

Example: I can't tell you how many people go up to the fax machine in the office and ask whether paperwork has to be face-up or face-down. (The owner of the company asks every time.) (Every. Time.) How do you work in offices as long as these people have without learning that there is a little graphic on the machine to answer just that important question. (I also can't tell you how many blank faxes I've received over the years, because people a) didn't read and b) didn't ask, and just faxed away. Upside down.) The design is just fine: the question is answered. I'm not sure how else it could be addressed; bright colors or flashing lights? Or big letters? Nah. It's fine. People are idiots.

So your car radio is difficult to use while driving? Here's a thought: Don't use it while driving. You might want to watch the road instead.

The author talks about an expensive hoity toity Italian washing machine – it was so badly designed that the owners were afraid to touch it. "Why did they buy it?" the author asks. Well, because it's an expensive hoity toity Italian machine – and they're stupid. They wanted conspicuous consumption, or got snowed by a salesman who saw their weakness. Plus they probably hire someone to do their laundry anyway, or at any rate seem to be able to afford to.

And the author complains about the problems inherent in lowering a projection screen in a lecture hall – but it sounds like the hall long predates slide projectors. The projector had to be installed in the place long after the fact, and in such a way (I would assume) so as not to do any mischief to the structure or artistry of the room. So – yeah, it's not perfect. It doesn't exist in perfect conditions. Work with it. Or hold your lectures somewhere else.

And the author complains about senseless instructions for those VCR's, and all I could think was, well, they're often translated badly from Japanese.

The author talks about a design feature – or not – in an Audi which allowed the sunroof to be closed without the ignition key in place, but only if an odd sequence of steps were taken. Why, he asks, was it such a peculiar combination of steps? Well, a) because it was accidental, and/or b) because a non-peculiar combination might result in an accidental opening of the sunroof when you really didn't want it open. (I say "you" because I'll never so much as sit in an Audi.)

Now, I do agree with the basic premise of the book. Of course an object should be designed so that it's not difficult to use. But … well, see, over the sink in my apartment there are three switches. When I had a tour of the place I was told that the one on the left controlled the light, the one in the middle controlled the garbage disposal, and the last one was for the dishwasher. When I moved in a little while later it took about five minutes' trial and error. Now I don't have to think about it. Figure it out yourself: you'll probably remember it longer. "Control/alt/delete" isn't an intuitive command for the computer – but the reason for that is pretty sensible: it's not something that can be done using one or two close-set keys … because it's not something you want to do accidentally. And once it's learned, it's easy enough to remember.

Okay, go back to the whole door thing. The author admits that he has problems with doors. And I get it – if there's no label on a door it can be hard to know whether you're supposed to push or pull or whatever. But – at least nowadays – I think every door I see in a public venue has a little sign. And … I'm sorry, I can't muster up a whole lot of sympathy for the person who pulls on a door that says "push", or vice versa – including me. Honestly, I have little patience with anyone who doesn't read the damn directions.

I also don't have a lot of patience for someone who goes out and buys a massively expensive Italian washing machine without making sure they understand how to use it. Yes, that can be blamed on the design; it can also be blamed on the salesman seeing dollar signs, and on the fact that any instruction manual is probably translated from the Italian – and on a level of carelessness and lack of preparedness by the buyer. I'm sorry – if you don't put in a certain level of research into a big purchase, you deserve what you end up with.

If I need, for example, to make a spreadsheet do something I don't know how to do, I don't write a letter to MicroSoft complaining about the poor design of Excel. I figure it out, or I look it up. I work with people who don't bother to try to solve any problem for themselves. If they don't know how to do something, they sit in their seats and yell like children for help – literally. It sounds like the author is in favor of this attitude – everything should be obvious, and if it's not you're entitled to squawk. It's learned helplessness.

My feeling on this is basically that if I can figure it out, or look it up, anyone can do it – and damn well should.

And read my damned email, jackass.

So, no – technology of any sort should not be intentionally or incidentally obscure. But also, and equally, people should be able to learn and follow the instructions that are present and hone their deductive instincts. It's an ability that will only ever make life easier. ( )
  Stewartry | Nov 2, 2016 |
Showing 1-5 of 45 (next | show all)
no reviews | add a review

» Add other authors (7 possible)

Author nameRoleType of authorWork?Status
Donald A. Normanprimary authorall editionscalculated
Noferi, GabrieleTranslatorsecondary authorsome editionsconfirmed
You must log in to edit Common Knowledge data.
For more help see the Common Knowledge help page.
Series (with order)
Canonical title
Original title
Alternative titles
Original publication date
People/Characters
Important places
Important events
Related movies
Awards and honors
Epigraph
Dedication
First words
“You would need an engineering degree from MIT to work this,” someone once told me, shaking his head in puzzlement over his brand new digital watch.
Quotations
Last words
(Click to show. Warning: May contain spoilers.)
Disambiguation notice
Originally printed as "The Psychology of Everyday Things". Reprinted as "The Design of Everyday Things."

Please, Do not separate the differently titled works.
Publisher's editors
Blurbers
Publisher series
Original language
Book description
Haiku summary

Amazon.com Amazon.com Review (ISBN 0465067107, Paperback)

Anyone who designs anything to be used by humans--from physical objects to computer programs to conceptual tools--must read this book, and it is an equally tremendous read for anyone who has to use anything created by another human. It could forever change how you experience and interact with your physical surroundings, open your eyes to the perversity of bad design and the desirability of good design, and raise your expectations about how things should be designed.

(retrieved from Amazon Thu, 12 Mar 2015 18:22:49 -0400)

(see all 4 descriptions)

Even the smartest among us can feel inept as we fail to figure out which switch turns on which light or stove burner, or whether to push, pull, or slide a door. The fault lies in product designs that ignore the needs of users and the principles of cognitive psychology. A bestseller in the United States, this classic work on the cognitive aspects of design contains examples of both good and bad design and simple rules that designers can use to improve the usability of objects as diverse as cars, computers, doors, and telephones.--From publisher description.… (more)

» see all 3 descriptions

Quick Links

Swap Ebooks Audio
391 wanted1 pay

Popular covers

Rating

Average: (4.09)
0.5
1 3
1.5 5
2 19
2.5 7
3 94
3.5 22
4 228
4.5 21
5 218

Is this you?

Become a LibraryThing Author.

 

You are using the new servers! | About | Privacy/Terms | Help/FAQs | Blog | Store | APIs | TinyCat | Legacy Libraries | Early Reviewers | Common Knowledge | 116,173,302 books! | Top bar: Always visible