Skip to main content

Making People Feel Stupid: A Cardinal Sin in Design

People will go to great lengths and inconvenience to avoid appearing or feeling stupid. A great example of when design makes a user feel stupid comes from Alan Coopers 1999 book The Inmates are Running the Asylum on page 24. Cooper is talking about the keyless entry system on his car keys.
"The large button locks the car and simultaneously arms the alarm. Pressing the button a second time disarms the alarm and unlocks the car. There is also a second smaller button labeled 'Panic.' When you press it, the car emits a quiet warble for a few seconds. If you hold it down longer, the quiet warble is replaced by the full 100-decibel blasting of the car alarm, whooping, tweeting, yowling, and declaring to everyone within a half-mile that some dolt--me--has just done something execrably stupid. What's worse, after the alarm has been triggered, the little plastic device becomes functionally inert, and further pressing of either button does nothing. The only way to stop that honking announcement of my palpable stupidity is to walk to my frighteningly loud car, enduring withering stares from passersby, unlock the driver's door with the key, then insert the key into the ignition and twist it. It really makes me feel like an idiot. If my car merely got robbed it would make me feel violated and sad, but it wouldn't make be feel stupid."
This essentially happened to my wife over the weekend. The kids got in the car and were playing with the automatic locks while there were at a campsite up in the mountains. Nice and serene and quiet. Somehow, they triggered an alarm sound from the car. A car which doesn't even have an alarm system. My wife grabbed her keys and tried pressing all the buttons on the remote, but none of them turned off the sound. After three or four minutes, the alarm was still sounding. A camper came over from an adjacent site and knew to do a long-press on the panic button on the key fob. My wife had been planning to try to disconnect the battery, she was so flummoxed.

Bad design makes us feel bad and resent the people who foisted it upon us.

Comments

Popular posts from this blog

Hammers and Nails: Technology Push Design

"We need to refine our requirements first, before we look at tools." This is a common phrase that I hear. While I sympathize with the sentiment, I think it is frequently wasteful. I suspect that we'd get to the right requirements faster by looking at tools already available in a given problem space. Pushing the concept further, is it foolish to find a cool technology and then look for ways that that technology can apply to current problem spaces?  What if you don't even recognize you have a problem space? Without a constant search and openness, we'll miss many serendipitous opportunities. Here is BYU professor Larry Howell discussing this issue. I often enjoy doing something ... that is sometimes controversial. In this approach, rather than starting with a need, you start with a new technology and you search to identify a need that it can fulfill. This second more controversial approach is called "technology push design."   You can imagine t...

How much will you remember?

There is a commonly passed around "stat" that, according to a blog post I recently read, isn't true. You've probably seen it or heard it. It is said that people remember: 10% of what they read 20% of what they hear 30% of what they see 50% of what they see and hear 70% of what they write and say 90% of what they say as they do The blog author says: Quite where these numbers come from is a mystery to many, and indeed it is difficult to understand what 90% retention actually means… 90% of what for how long? As a model it looks and on first thought appears to be credible, however as many of us will know some people have almost 100% retention for a considerable period of time if they read something, others teach others from a structure or procedure which they themselves do not understand! Thanks, RapidBI, for pointing out this common misconception!