alt Hacker NewsI was gifted this book my a CIO when in college. She had a dozen copies in her office to hand out to various people.
It took me a few tries to get up the will to actually read it. It was years ago, so I don’t remember a lot of details. My main take away was to make controls logical for the thing being controlled. “Norman doors” are the big one, but I often think about it while I’m in my car trying to do something on a touch screen, when all I want is a knob, button, or switch.
In the modern era of web design I think it would point to these websites (like most of Apple’s product pages), that make users scroll through indulgent animations, just to get to the content. It may be cool the first time, but is very annoying for repeat visits, and it feels like it breaks my scrolling expectations. Not to mention all the horizontal scrolling thrown in there, which becomes a headache for those without the hardware to do it easily, and confusing to change scroll direction all the time.
Replies
The thing about norman doors is that it's not really a design flaw, not in every case. Like handles on push doors. It's tempting to think of that as a design flaw but more likely it's designed to be mass produced and reversible, the cost of making two (or more) configurations being much higher than the occasional confused user. You could argue this only enhances the metaphor as a lot of design issues occur when things are optimised for the company and not the user.
My car has a staggeringly bad UI design choice - the cancel active navigation the control to do this only appears when you hold your finger close to the screen. Pretty much every time I want to do this I am flummoxed as to "Where did the button go" - before I eventually remember.
The navigation system is good - I prefer it to using my phone and CarPlay but that design is terrible.
I love this. Thank you for introducing me to "Norman Doors". I hadn't realized someone else had described this in such detail. I have been complaining about this years.
Ok this will be a tangent, but I also take this one step farther and also talk about "documentation". Just for the record, I don't think documentation is all good or all bad, but it definitely can be used incorrectly and in excess. And Norman Doors and a great way to get this point across.
When someone creates or installs a Norman Door by accident or out of ignorance and then realizes there is a problem, they often think "I know, I will document it!" and they add little placards to the door that says "Push/Pull" or some such. They see that this helps with a small subset of users and thinks "there, I fixed the problem, people just need to read the documentation and now it is their problem if they don't". But if you watch users of the door, a large portion will still use the door incorrectly because... people don't read documentation. If they don't read documentation, is it the users fault the door was designed incorrectly or was it the designers problem?
I use this as an example for my developers on thinking before documenting troublesome code or a confusing interface to first ask "can I design this so it is less confusing?" and if so, that would usually be preferable to adding documentation "to solve the problem". Well designed code (or doors) with no documentation always beats poor designs with documentation.